How To Write User Stories In Scrum? – Easy User Stories Writing Skills
Posted on September 1, 2010
Filed Under Scrum Basics | Leave a Comment
In Scrum methodology, proper User Stories are the key to maintain or form a great product backlog. How do we write good user stories? What are the main aspects of a great user story? How can one consciously write great user stories? Please read on to get a quick overview of user stories in Scrum…
User Stories format should be maintained for uniformity.
User Stories need to be written in the following format for better understanding of the requirement and the value addition that it provides to the customer.
As A [role], I want [Requirement/Feature], So That [Justification/Reason]
or
As a [role], I want [Requirement]
e.g.
1. As a System Admin, I want to track Log-In history, so that I can see who have logged in to the system and when.
2. As a Customer Support Executive, I want to search Case Notes by Case ID
User Stories should be concise and easy to understand
User Stories need to be concise, as people are not patient enough to read lengthy user stories. Easier it is to read, better it is for the team to understand the gist of the wanted requirement. That’s why people first write User Stories on a physical Index Cards (3’’x5’’) to be minimalistic.
User Stories should be customer centric
User Stories should represent customer requirements or pain points. It is never an assumption of the developer or product owner. User Stories should be a result of thorough customer requirements review.
User Stories should be testable
User Stories should have follow-up definition of done. That is, the requirement or the feature that is mentioned in the user stories should be testable. A generic user stories is always difficult to test.
e.g. As an user, I want very User Friendly GUI
The above User Story is hard to understand as there is no end for a GUI to be user friendly. This can be broken down so that more meaningful user stories emerge.
User Stories should be of right size (effort-wise)
User Stories should not be too small or too large in terms of efforts needed it to be developed. Ideally, experts suggest that an User Story should be implementable in say 40 hours or about a weeks time.
*Visited 4756 times, 5 So far today*
Comments
-
About
All about Scrum Framework, Tutorials, Guides, Discussion Forum. KnowScrum.com is maintained by Scrum Certified Industry Experts. Please feel free to participate on Scrum initiatives on KnowScrum.com
-
Search
Leave a Reply