Feature Feature Feature

A system service that fulfils a

stakeholder need. It has a benefits Requested Ready
hypothesis and acceptance criteria,
and is sized or sliced as necessary to
Source is clear.
The Feature has a clear owner.
fit within a Program Increment.

Meaningfully named.
The Feature can be clearly described.
Requested
Not a Story.
Any ‘fixed’ requirements are known.
Ready
Not an Epic.
The level of key stakeholder

In the Backlog. involvement is understood.
Committed
Small enough to fit within a PI.

Relevant.
Previewed
The cost of delay is clear.

The Feature is testable.
Accepted

The Feature is feasible.
Released
Potential benefits are understood.
Done
Relates to: Requirements
1/7 2/7
V1.3 V1.3 V1.3

Feature Feature Feature

Committed Previewed Accepted

Stories outlined.

Dependencies understood.

Lead team known.

Working relationships established.

New estimate available.

Completion forecast.

Acceptance criteria agreed.

Benefits hypothesis confirmed.

Technical impact understood.

Key decisions verified.
No loose ends.

Unwanted stories removed.
Accepted by the Feature Owner.

Story priorities clear.
Actuals known.

Product Manager enthused.
Success forecast.

The gap to completion is known.
Acceptance Criteria met.

Release forecast.
All necessary stories accepted.

Acceptance criteria finalized.
Benefits hypothesis validated.

Risk under control.
Releasable.

Benefits hypothesis supported.
Fully tested.

Viability confirmed.
Code complete.

3/7 4/7 5/7

V1.3 V1.3 V1.3

Feature Feature

Released Successful

Available to users.
In use.

Help available.
Feedback positive.

Actuals known.
Actuals known.

Benefits hypothesis assessable.
Benefits hypothesis accepted.

All stories deployed.

6/7 7/7
V1.3 V1.3