If you’re wondering about how to do an outstanding job on figuring out users and what matters to them, look no further!I recommend this site’s: Tutorial on Personas, Problem Scenarios, and Value Propositions.Stories can be ever bit as structured as old school ‘requirements’.
For more detail, ‘test cases’ are associated to stories.
Organizing inputs to development this way turns out to be a more descriptive, more actionable, more discussable way to define what you want to build.
If you want to jump ahead, check out the Examples below and/or the User Stories Template.
This piece will equip you with foundation concepts for creating great agile user stories and using them to drive better collaboration in your team.
User stories have a specific format, designed to help the author be descriptive and the reader (a developer) to take action: “As a ” If you’re the product person, your job is the fill in the (orange) blanks.
The persona is a vivid, humanized, yet operational description of your user.
The ‘[do something]’ is a some action you assume the user wants to do, and the ‘[derive a benefit]’ clause is a statement of why you’ve assumed the user persona wants to do what you describe.
The reason why it’s so important is that this is where you’re saying why the feature you’re proposing to build makes sense.
The world’s an uncertain place and you don’t necessarily have to be right about why but you .