User Stories18% of the exam
User story anatomy, INVEST and splitting
The three parts of a user story and why each matters, how to keep stories about intent rather than implementation, how to diagnose a weak story with the INVEST checklist, and how to split a story that is too big.
Understand the components of a user story to perform thorough analysis.
~7 min read · 21 practice questions ·
What the exam expects
- Identify the who, what and why of a story, and say which one is missing or weak.
- Explain why the benefit clause matters for prioritization and for delivering the intended outcome.
- Rewrite stories that name an implementation, a vague persona or a circular benefit.
- Diagnose a weak story against each INVEST characteristic and choose the fix.
- Split an oversized story into pieces that still deliver value, and plan who attends a story-writing workshop.
Key terms:
- User story: a simple description of a feature told from the user's point of view.
- Persona: the defined user from whose perspective the story is written (the who).
- Benefit: the why, the reason the user needs the functionality.
- INVEST: Independent, Negotiable, Valuable, Estimable, Small, Testable; a checklist for story quality.
- Story-writing workshop: a session near the start of a project where the project team brainstorms stories.
Key facts
Story format
- Detail
- As a < who >, I want < what > so that < why >
Parts of a story
- Detail
- Who (persona), what (goal), why (reason); all equally important
A story is a synopsis
- Detail
- It does not outline the entire requirement
INVEST origin
- Detail
- Bill Wake, 2003
Negotiable
- Detail
- An invitation to a conversation, not a contract
Estimable
- Detail
- An exact estimate is not required
Undefined who
- Detail
- Create a list of defined personas before writing stories
Workshop timing
- Detail
- Near the start of the project
Backlog priority
- Detail
- Set by the product owner
- Why does a missing benefit clause hurt the backlog?
- What does Negotiable mean in INVEST?
- When should a story-writing workshop be held, and who attends?
- Why should a story avoid naming components or services?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Business Analyst pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 22 lessons of the Business Analyst guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (21 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams