One of the major challenges we have encountered during agile transformation journeys at our clients is to solve how to ensure that Product Owners write good user stories! Many POs, in our experience, dilute the essence of user stories by obsessing on the technicalities and overlooking user engagement and focus. POs should take the user-centric approach to story writing, engaging in discussions and dialogue with clients, development teams, and other stakeholders but it seldom happens.
Also, user stories are neither shorter versions of Business requirement documents( BRD) nor a different form of use cases. Traditional project management approaches needed detailed, humongous documentation written upfront – primarily necessitated by freezing of requirements in the analyses phase. However, BRDs don’t have a place in agile ways of working, where the only constant is “change”.
Listing 12 basic and useful pointers to be cognizant of while writing good user stories below. Try using these as your guiding principles for writing user stories, we think they would help you write better user stories, which will be immensely useful during agile estimation and planning in particular and in realizing overall agility in general.
We would be glad to hear your views & feedback on the above pointers.Try using these simple 12 pointers next time during your story writing sessions and let us know your experience at consult@benzne.com
Sudha MadhuriAgile Consultant, Benzne
