In 30 seconds
- A feature is a distinct capability users can see and value.
- In SAFe, features fit within one Program Increment.
- Features are split into user stories for sprints.
Features, epics and stories
Teams use the hierarchy differently, but a common pattern is: an epic holds several features; each feature holds several user stories. A feature is something a user would recognize, such as "saved payment methods".
In SAFe
In the Scaled Agile Framework, a feature is sized to be delivered by one Agile Release Train within one Program Increment. Each feature includes a benefit hypothesis and acceptance criteria.
Writing a good feature
- Name it by user benefit, not technical work
- State the expected benefit and how you'll know
- Keep it small enough to deliver in weeks, not months
Myth vs reality
Myth · Features and user stories are the same.
Reality · Features are bigger and broken into stories.
Myth · More features means more value.
Reality · Unused features add cost and complexity.
Myth · Feature lists are fixed.
Reality · They're ordered and pruned like any backlog.
FAQ
Do Scrum teams need features?
Optional; many use them to group stories.
Who writes features?
Product managers or Product Owners, with the team.
How is a feature different from an MMF?
An MMF is a feature small enough and valuable enough to release on its own.