Over the last few weeks, we’ve taken a look at several aspects of user story writing. As the primary means of kicking off conversations between product and engineering in most Agile environments, user story writing is a critical skill to develop. Let’s review where we’ve been.
If you are still wondering what the value of user stories are over more traditional product requirements documents, start with:
This post highlights the communicative benefits of user stories and also discusses how to ensure that your team can benefit from them.
If you are already convinced of the value of user stories, but need a primer on how to write user stories, read:
These posts review the basic components of a good user story. The first includes many examples and the second looks in-depth at acceptance criteria.
Once you’ve got a handle on the basics, review the following posts for some additions to the basic story format that help guide strategic thinking and planning.
- Using Themes to Wrestle an Ever-Growing Backlog
- Measuring the Impact of Each User Story
- Predicting the Impact of Each User Story
And finally, the following post discusses the many factors to take into account when prioritizing your backlog:
What did we miss? What else would you like to know about writing and managing user stories? Please share your questions and thoughts in the comments.
[…] Everything You Ever Wanted To Know About Writing User Stories […]
[…] Torres details the many benefits of user stories, the current best practice to document user needs/solutions vs. old school (PRD, […]
[…] managers prioritize and define problems or opportunities by writing user stories or job […]