Contents
The five stages a requirement passes through
Each stage receives an artifact from the one before and hands its own to the next. Things break at the seams.
01 — Requirements
How a task becomes a task
- 01.1 Definition of Ready: a finished spec and its imitation The signs that a task should not be taken into a sprint yet. →
-
01.2 Scope boundaries: what is in and what merely sits nearby in progress
02 — Analysis
A requirement becomes a description
-
02.1 Traceability: linking requirement, implementation and check in progress
03 — Development
What the analyst does while the code is written
-
03.1 Mid-flight change: rewrite the spec or file a new one in progress
04 — Testing
Checking what was actually ordered
-
04.1 Bug or omission: triaging disputed defects in progress
05 — Deployment
The task reaches the user
-
05.1 The first day in production: what to watch in progress