Home › Free PMP lessons › Agile Practices

PMP lesson · Agile Practices · Backlog and stories · lesson 2 of 3 · about 7 minutes

User stories: INVEST, acceptance criteria and splitting

Agile and hybridFree preview
Goal: After this lesson you can write a user story with acceptance criteria, check it with INVEST, and split big stories vertically.

1The situation

“Not what was meant”

At three sprint reviews in a row, the MES product owner rejected stories that matched their short written criteria: “This is not what was meant.” The criteria were written by the PO alone, often in one line.

Meanwhile, a 55-point story, “automated order-to-shipment workflow”, was split by the team into database, logic and screens, and none of the parts could be shown to users.

Good stories are small, valuable and clearly understood by everyone.

2The user story

A user story describes a need from the user's view: As a [role], I want [capability], so that [benefit]. It is a placeholder for a conversation, completed with acceptance criteria.

Card
The short description
As a shift supervisor, I want to export the shift report, so that I can send it to the plant manager.
Conversation
Shared understanding
PO, developers and testers discuss it together (“three amigos”).
Confirmation
Acceptance criteria
Given / when / then examples that prove it works.
Misunderstandings are fixed by conversation and examples, not by longer text written by one person.

3INVEST: the qualities of a good story

I · Independent

Can be built in any order where possible.

N · Negotiable

A conversation, not a contract.

V · Valuable

Delivers value to a user or customer.

E · Estimable

The team can size it.

S · Small

Fits in a sprint.

T · Testable

Clear acceptance criteria.
Check each story against these six qualities.

4How it looks on the exam

Exam-style question 1. The product owner rejects several completed stories at reviews because 'this is not what was meant', though they meet the brief written criteria, which the PO writes alone. What should the project manager suggest?
A. Ask the PO to write longer criteria
B. Build two versions of each story
C. Collaborative refinement where the PO, developers and testers agree acceptance criteria and examples together before development
D. Accept the rejections
Show the answer and the decode
Answer: C.
In simple English
Misunderstood stories.
What is the question really asking?
How to prevent it.
Key words / trigger
“written by the PO alone”
PMP logic
Shared understanding comes from conversation and examples (three amigos).
Why the wrong answer looks attractive
Longer text written alone can still be misunderstood.

5Remember this

Your memory card

  • Story: As a … I want … so that … + acceptance criteria
  • INVEST: independent, negotiable, valuable, estimable, small, testable
  • Agree criteria together with examples (card, conversation, confirmation)
  • Split vertically, never by technical layer
The full lesson in the PMCLEAR app also has:
  • the rest of the lesson (Splitting big stories)
  • a worked example
  • the common traps (wrong vs right)
  • 2 exam-style questions with the decode
  • a 3-question quick check
Open the full lesson → Create a free account
← The product backlog and refinementNext: Definition of ready and definition of done →