ART · Backlog item · Fits in one PI
Feature
A benefit hypothesis one ART can deliver within a PI.
01What it's for
A Feature is a slice of an Epic with a measurable benefit, sized so that one ART can deliver it within a PI. It carries a benefit hypothesis and acceptance criteria.
Product Management owns the what and the why. The ART owns the how.
02What it turns into on the old system
The Feature becomes a requirement or work package. The business specifies it, hands it to IT and receives an estimate in hours. Features are cut by component or department.
03How you notice
- Features are named after systems or components.
- A Feature is “done” when it is deployed, not when its benefit is measured.
- Features are larger than a PI, or need four teams in sequence.
- The benefit hypothesis field is empty.
04How to make it work
Write the benefit hypothesis and how it will be measured, next to the acceptance criteria.
Slice vertically through the architecture so the Feature delivers value on its own.
Keep it small enough for one PI. If it isn't, split it.