What are User Stories?
User Story is one of the features that need to be built for the product, described from the viewpoint of the end-user.
The things to be captured in a User Story are as follows:
Rules for writing a good user story are as follows:
The things to be captured in a User Story are as follows:
- Who - for whom is this being developed
- What - what is the goal that we want to achieve
- Why - what is the value that the end-user derives from this
Each User Stroy needs to have proper Acceptance Criteria, which should be demo-able so that it can be reviewed by the Product Owner / Stakeholders.
- The criteria specified should be testable and should clearly mention the pass / fail results
- Should be clear and concise
- SHould be defined with a shared understanding between the Product Owner and the Development Team.
Rules for writing a good user story are as follows:
- Independent - one user story should not be dependent on another
- Negotiable - the user story should be able to adapt to changing scenario for the end-user
- Valuable - should give some concrete value to the end-user
- Estimateable - should be able to judge the complexity involved and estimate the effort needed
- Small - should be small enough for the development team to finish it in a few days
- Testable - the user story should be testable
Comments
Post a Comment