Before we start talking about the User Stories, how many of you know that User Stories are not part of Scrum? I know, I know, you must be thinking that I am joking. But I am not. User Stories are not part of Scrum. The concept of User Stories comes from Extreme Programming.
User Stories consists of three components, called 3 Cs. Card, Conversation, and Confirmation.
1. Card:
User Stories are typically written on an index card. This card just contains enough text to identify the requirement and initiate the discussion.
2. Conversation:
The need/requirement is communicated from customer to the team members by conversations. This conversation takes place over time, particularly when the story is estimated (usually during backlog refinement ), and again at the Sprint planning when the story is committed to the team. for implementation
3. Confirmation:
The third C in the user story’s key aspects is confirmation. This component is the acceptance of the story finished by the team.
As we humans evolve, User Stories have evolved too. People who have mastered writing user stories have relied on few important aspects.
1. Role: Who is going to use the functionality.
2. What: What is being developed
3. Value: How much value business get out of this functionality
4. Acceptance Criteria: How a User Story will be accepted/decided as done
5. Estimate: How much effort team needs to put in order to deliver the story.
The test for determining whether or not a story is well understood and ready for the team to begin working relies on INVEST acronym, which is self-explanatory.
I – Independent
N – Negotiable
V – Valuable
E – Estimable
S – Small
T – Testable