User Stories are narratives that foster collaboration, guide development and drive meaningful outcomes.
But many use them as containers for requirements.
So here's User Stories 101:
(1/14)
But many use them as containers for requirements.
So here's User Stories 101:
(1/14)
(2/14)
1. Why?
A User Story is written from the perspective of a user who wants to derive value from the product.
It should focus on the user's desired outcomes and be embedded in the context where the user seeks value from the product.
1. Why?
A User Story is written from the perspective of a user who wants to derive value from the product.
It should focus on the user's desired outcomes and be embedded in the context where the user seeks value from the product.
(3/14)
2. How?
The basic format of a User Story:
WHO: As a [user type]
WHAT: I want [action to perform]
WHY: So that [the desired outcome]
A prerequisite to working with User Stories is understanding the users, ideally segmented by their needs and desired outcomes.
2. How?
The basic format of a User Story:
WHO: As a [user type]
WHAT: I want [action to perform]
WHY: So that [the desired outcome]
A prerequisite to working with User Stories is understanding the users, ideally segmented by their needs and desired outcomes.
(4/14)
3. Effective User Stories: 3C's
The 3 C's of User Stories are Card, Conversation, and Confirmation.
They are essential for writing a good User Story.
3. Effective User Stories: 3C's
The 3 C's of User Stories are Card, Conversation, and Confirmation.
They are essential for writing a good User Story.
(5/14)
- Card
A card explaining WHO, WHAT, and WHY. They once were physical cards, but today, we create User Stories in tools like Jira.
- Card
A card explaining WHO, WHAT, and WHY. They once were physical cards, but today, we create User Stories in tools like Jira.
(6/14)
- Conversation
Rather than creating a detailed specification, discuss the reasoning behind the User Story.
Everyone needs to understand how the User Story will benefit the users, how it will contribute to your objectives, and how it aligns with your strategy.
- Conversation
Rather than creating a detailed specification, discuss the reasoning behind the User Story.
Everyone needs to understand how the User Story will benefit the users, how it will contribute to your objectives, and how it aligns with your strategy.
(7/14)
- Confirmation
Confirmation refers to the Acceptance Criteria that should be fulfilled to ensure the requirements have been met and delivered correctly. It's a concise checklist, not detailed test cases.
- Confirmation
Confirmation refers to the Acceptance Criteria that should be fulfilled to ensure the requirements have been met and delivered correctly. It's a concise checklist, not detailed test cases.
(8/14)
4. The INVEST User Stories
INVEST is an acronym representing the essential qualities of well-written User Stories:
- Independent: Each User Story should be self-contained and not depend on other stories.
4. The INVEST User Stories
INVEST is an acronym representing the essential qualities of well-written User Stories:
- Independent: Each User Story should be self-contained and not depend on other stories.
(9/14)
- Negotiable: The details of the User Story can be discussed and negotiated with the team and the stakeholders.
- Valuable: The User Story delivers value to the user.
- Estimable: It should be possible to estimate the effort required to complete the User Story.
- Negotiable: The details of the User Story can be discussed and negotiated with the team and the stakeholders.
- Valuable: The User Story delivers value to the user.
- Estimable: It should be possible to estimate the effort required to complete the User Story.
(10/14)
- Small: User Stories should be small enough to be completed within a single iteration. If you do not work in iterations, you might assume 2-4 weeks as the rule of thumb.
- Testable: There are clear criteria to determine if the story has been successfully implemented.
- Small: User Stories should be small enough to be completed within a single iteration. If you do not work in iterations, you might assume 2-4 weeks as the rule of thumb.
- Testable: There are clear criteria to determine if the story has been successfully implemented.
(11/14)
Those qualities are desirable. But do not obsess over the acronym.
Those qualities are desirable. But do not obsess over the acronym.
(12/14)
5. How to Split User Stories?
Some User Stories are too big to be selected for the implementation.
You must break them into smaller, more manageable pieces to deliver value faster and, ideally, start learning from customers using your product for real.
5. How to Split User Stories?
Some User Stories are too big to be selected for the implementation.
You must break them into smaller, more manageable pieces to deliver value faster and, ideally, start learning from customers using your product for real.
(13/14)
- Epic: A larger element, typically combining 5-15 smaller User Stories (that's context-specific).
- User Stories: Small, manageable items.
- Tasks: Used to plan and monitor the exact work performed by Engineers. PMs have nothing to say here.
- Epic: A larger element, typically combining 5-15 smaller User Stories (that's context-specific).
- User Stories: Small, manageable items.
- Tasks: Used to plan and monitor the exact work performed by Engineers. PMs have nothing to say here.
(14/14)
Some add more layers, but in my experience, you don't need that.
Keep it simple.
Some add more layers, but in my experience, you don't need that.
Keep it simple.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
