The real cost of vague stories.
Teams waste 30% of sprint time on rework caused by unclear requirements. After analyzing 1,000+ user stories, we found that well-written acceptance criteria reduce rework by 75%. Here's the exact framework that turns vague ideas into shippable increments.
Sprint time on rework30%↓
median time burned re-doing work that didn't match the spec.
Rework reduction−75%↓
for stories with structured acceptance criteria vs. plain prose.
Story-to-test ratio1 : 4
elite teams write 4 testable AC per story; median teams write 1.
A Given/When/Then that holds.
The structure is older than agile, and it still works. Each acceptance criterion is one sentence:
Given a precondition, when an action occurs, then a measurable outcome happens.
If you can't write the AC in this form, the story is too big — split it.
What separates good from great.
TBL · 01 · ACCEPTANCE CRITERIA QUALITY MARKERSN = 1,000+ STORIES
| Marker | Rework Drop | Operational Tell |
|---|---|---|
| Each AC is one observable outcome | −42% | Tester can mark pass/fail without judgment |
| Edge case covered explicitly | −27% | Bonus list of 3 edge cases per story |
| Non-functional requirements named | −18% | Latency, accessibility, security, observability |
| Out-of-scope listed explicitly | −14% | Stops scope creep at planning, not at QA |
Patterns that ship, patterns that don't.
✓DO
- Write AC as one observable outcome each
- Cover at least one edge case explicitly
- Name non-functional requirements (latency, a11y, observability)
- List explicitly what's NOT in scope
- Confirm AC with engineering BEFORE the sprint, not during
✗DON'T
- Treat the description field as the spec
- Bundle multiple outcomes into one AC
- Defer 'edge cases' to QA
- Skip the out-of-scope list
- Re-write AC mid-sprint
Before you accept the story.
▸ AC · CHECKLIST0/6 COMPLETE
- Each AC is a single observable outcome
- Edge cases enumerated (≥ 3)
- Non-functional requirements named
- Out-of-scope items listed
- Engineering signed off pre-sprint
- QA can pass/fail without interpretation