User stories are the general-purpose agile substitute for what traditionally has been referred to as software requirements. User stories describe system requirements from a user perspective, which are?brief statements of intent?that describe an action that a user wants to perform through the system to achieve a benefit.?
1. Interview target users to understand user roles, goals, and values relate to your service
2. Summarize the information from interviews
3. Articulate the summary in a standard user-voice form : "As a?
4. Make sure the user story focuses on describing a "problem" rather than a distinct solution
5. A well-formed user story should be:
Independent of each other
Negotiable: can be discussed in team
Valuable: valuable for users
Estimable: enough information
Small: small and concise
Testable: can be easily tested
The techniques below have the same characteristics.
The techniques below have different characteristics.