Master the backlog hierarchy — Epics, Features, Stories and Tasks — and how each level serves a different planning horizon and audience. Learn to trace a single Epic down to Tasks and back up so progress rolls up honestly, and avoid the over-deep hierarchies and mislabelled items that break the trace.
Watch the free preview
The flat backlog that no one could plan — free to watch, no account needed.
What you'll learn
- Explain the backlog hierarchy of Epics, Features, Stories and Tasks and the planning horizon each level serves
- Distinguish the four levels by size, audience and lifespan, and place any backlog item at the right one
- Trace a single Epic down through Features and Stories to Tasks and confirm status rolls up correctly
- Diagnose a broken roll-up where a Feature reads done but its Epic does not, and repair the trace
- Build a Backlog Hierarchy Trace Template with a status roll-up and a linked column
Syllabus
Why the Hierarchy Exists
The flat backlog that no one could planFree preview
Four planning horizons, four audiences
Each Level in Depth
Epics and Features — the outcome and the deliverable
Stories and Tasks — user value and the how
Applying the Hierarchy to Real IT Work
Tracing an Epic down and rolling status back up
Case study — the Feature that was done for months
Making the Hierarchy Stick
Build your Backlog Hierarchy Trace Template
Traps — over-deep hierarchies and mislabelled items