Talk about # Entry requirements #

1: The demand is no longer the traditional SRS document, but one article, can query, edit, modify, state tracking. such as the user story in the backlog that scrum proposes.

2: The hierarchy of requirements, the level of division is often not enough. First-level requirements often collect raw material requirements, difficult to control its scope and scale, so it is not easy to directly develop, second-level requirements through the first level of filtering and finishing, suitable for the development of the program. Epic and story are commonly divided in agile, and are divided into customer needs, product requirements, and component requirements in the CMMI.

   Different organizations will also arrange intermediate levels between the first and second levels in order to be more fit to the organization. But from a lean point of view, the intermediate product is a potential waste, unless it is necessary to suggest that level two needs to be expressed is sufficient.

3 : Fragmentation of requirements is a very obvious trend and should be realistic, and entry is the only efficient solution to the fragmentation of demand.

4 : The state management of the entry requirements can be the initial identification, acceptance, confirmation, implementation, validation, and integration of the requirements, especially the changes can be combined, so far the most efficient demand management. It also supports the entire life cycle of the product, beyond the project-level lifecycle.

< Span style= "Color:rgb (51, 51, 51); Font-family:arial, ' Microsoft Yahei '; font-size:14px; line-height:23px; " > 5: The entry requirements to obtain a full-time verification of the opportunity, compared to the waterfall-type demand packaging stage review, equivalent to two levels of segmentation, 1 is horizontal, the bulk of the demand cut into the entry, 2 is vertical, from the identification, preliminary acceptance, confirmation requirements, implementation, verification, testing and so on step-by-step verification, the role More efficient and more precise

< Span style= "Color:rgb (51, 51, 51); Font-family:arial, ' Microsoft Yahei '; font-size:14px; line-height:23px; " > 6: For the first level of the expression of requirements, the most common is epic, cloud, kite-level use cases, business use cases, the original requirements and so on, the most important point is not to guide the follow-up implementation, but to capture the real expectations of the stakeholders, requirements, so in the expression as far as possible in the stakeholder language

< Span style= "Color:rgb (51, 51, 51); Font-family:arial, ' Microsoft Yahei '; font-size:14px; line-height:23px; " > 7 : For the second level of the expression of requirements, the common user story, system use cases, use cases, demand use cases, the most important thing is to confess and confirm the characteristics of the software to achieve, to guide the implementation of the follow-up. If a programmer writes a second level of demand directly, it can be relatively simplified. But the scene expression becomes the current popular practice, no longer pursues the traditional refinement induction or the formal expression.

< Span style= "Color:rgb (51, 51, 51); Font-family:arial, ' Microsoft Yahei '; font-size:14px; line-height:23px; " >
/span>

Martian Chen Yong # entry Requirements # I am now on the point of view of the article and structure: fragmented demand is not the discovery of a completely non-related fragmentation of requirements, but the fragmentation of the discovery of demand. Fragments are not nouns, nor adjectives ("need"), but adverbs ("discoveries"). The intrinsic relevance and structure of demand is not agile development or the internet can break.
Wings Fly _2012: What are the tools?  Interested! reply @ wings fly _2012: Many of the entry tools can be, such as redmine,mantis,jira,polarion,rally,trello,vsts, etc.

Talk about # Entry requirements #