Write stories from the end-user's perspective. The end-user may be a external customer or internal customer. User stories also form the building blocks of agile frameworks like epics and initiatives.
As a: [user role that will be interacting with the system]
I want to: what is the value bring to the end user.
So I can: [what is the result]
e.g. As a mother I want to be able to check the status of my childs bill.
- Helps in delivering high quality content.
- Eases collaboration within team.
- Helps understand users better.
- Improves transparency.
- Reduces risks/uncertainty.
- Supports iterative development.
- Focuses on vocal / f2f communication.
Idependent - Stories should be independemt of one another so that each of them can be developed and delivered separately. Negotiable - Stories should be discussable and should be open for negotiation. Valuable - Stories must ensure value is being added to the customer. Estimatable - The stories must be estimable and can be divided into tasks. Small - Stories should be able to be completed in 40 hours. Testable - They have to have an acceptance criteria that can be tested to check if the fulfill the customer's need.
Card: A card provides a written description of a user story. This is used for planning and estimation. Coverstation: this represents the dicussions between stakeholders. It helps build shared understanding. Confirmation: These represent the conditions that need to be fulfilled to ensure the story meets requirements.
- JIRA - Kanban board. Story Management.
- Should be used to order backlog to achieve maximum value.
- Should not be used to judge people.
- Should not be tied to incentives
- Should not have too many jobs.
- Should not be hours, complexity, or absolute.
- Triangulate. If there is another story that is a 3, another that is an 8, and this is somewhere in the middle, may be it is a 5.
https://www.youtube.com/watch?v=_N5gj9gzOjg
Software
- Planning Poker - Story point estimation.