In my last post, I wrote about how technical tasks are not user stories. But what does it make a user story good?
- I – Independent: Bear in mind that priorities may change along the project, so user stories could be moved around. Therefore, they need to be the most independent.
- N – Negotiable: User stories are not strict requirements, they would change along the way. However, they should be only negotiable until a sprint has started.
- V – Valuable: As I mentioned in my previous post, user stories are done in order to add value to the end-user.
- E – Estimable: What’s the point of doing something that cannot be estimated? If they are not estimable, they will never be done or planned in a sprint.
- S – Scalable: Related to the previous one, user stories must be small-sized. If they are too big – epic stories -, try to break them down into smaller pieces.
- T – Testable: To move one user story to DONE, it should be successfully tested. Therefore, provide the required information in the user story to test it.
Apart from this, I would add one more point:
- Collaboration: User stories should be written by the Product Owner. Nonetheless, SCRUM focuses on teamwork and self-organization. Then, it’s a good idea to write – or modify – user stories collaborately so everyone provides an opinion or viewpoint.
Would you add any other characteristics?Antonio González