Develop and/or revise the set of user requirement issues for your project. List links to the issues in sec. 3.3 of the SPD. A template to [create a user requirement issue]() has been added to your repository. A well written user requirement should be easy to justify (Rational) and should be testable.
Details
User requirements should be "user facing" and serve as top-level drivers for other development your project. Not all iterations through the development phases will generate additional user requirements. A good strategy for the first planning pass is to determine a set of user requirements that comprises a minimum viable product (MVP) and label them as must have.
[ ] Create issues for each use case using the [User Requirement]() issue template.
[ ] Review draft use case with your team and refine their descriptions.
[ ] Label each issue to indicate the priority as either: must have, should have or nice to have.
[ ] Update section 3.3 of your SPD with a list of links to each issue.
Note: If no user-facing updates are planned for this iteration indicate as such in Sec 3.3.
When planning specific development activities, refer back to user requirements when appropriate.
Summary
Develop and/or revise the set of user requirement issues for your project. List links to the issues in sec. 3.3 of the SPD. A template to [create a user requirement issue]() has been added to your repository. A well written user requirement should be easy to justify (Rational) and should be testable.
Details
User requirements should be "user facing" and serve as top-level drivers for other development your project. Not all iterations through the development phases will generate additional user requirements. A good strategy for the first planning pass is to determine a set of user requirements that comprises a minimum viable product (MVP) and label them as
must have.must have,should haveornice to have.Note: If no user-facing updates are planned for this iteration indicate as such in Sec 3.3.
When planning specific development activities, refer back to user requirements when appropriate.
References
Requirements Checklist