Please enable JavaScript.
Coggle requires JavaScript to display documents.
Guidelines for Good Stories - Coggle Diagram
Guidelines for Good Stories
Start with Goal Stories
Consider each user role and identify the user's goals for interacting with the software.
Then we can used them to generate aditionals
Slice the Cake
split the story along technical lines
A much better approach is to write the replacement stories so that each one provides some level of end-to-end functionality.
An application could conceivably be released
for use with only its main functionality
Write Closed Stories
Finishes with the achievement of a meaningful goal and that allows the user to feel she has accomplished something
closed stories area part of the original story that was
not closed.
Put Constraints on Cards
constraint cards do not get estimated and scheduled into iterations but are still useful
can be taped to the wall where they act as reminders
write automated tests to ensure that constraints are being met
Size the Story to the Horizon
stories for the next iterations will be written in sizes that can be planned in those iterations
Distant stories could be
much larger and less precise
Take advantage of the flexibility of stories to make them useful on multiple levels.
Keep the UI Out as Long as Possible
One common mistake is to mix requirements with solution specification
Some Things Aren’t Stories
user stories are very flexible
They work well for describing much of the functionality of many systems
But they are not appropriate for everything
Use different format when needed
Include User Roles in the Stories
make use of roles in
writing the stories
writing stories in this way keeps the user in the forefront of the developer’s mind.
Write for One User
are generally most readable when written for a single user.
for some stories the difference can be significant
Write in Active Voice
Makes them easier to read and understand.
Customer Writes
This would be the ideal
Responsibility for writing stories resides with the customer and cannot be passed to the developers.
it is vital that the customer understand each story.
Don’t Number Story Cards
Numbering story cards adds pointless overhead to the process and leads us into abstract discussions
Don’t Forget the Purpose
Story cards main function is to act as a reminder to discuss the feature.
Do not replace the conversation by adding more detail to the story card.