Backlog Refinement and MoSCoW
Level 4 Β· Stories, sizing and tracking
How backlog refinement keeps the top of the list small, clear and sized. How the MoSCoW method sorts work into must, should, could and won't have.
Course contentsLesson 14 of 19
Level 1 Β· What agile is
Level 2 Β· Scrum
Level 3 Β· Kanban
Level 4 Β· Stories, sizing and tracking
Level 5 Β· Other methods and scale
After this lesson you can
- Run backlog refinement
- Sort items with MoSCoW
- Keep the must haves honest
10 mincovers 2 glossary entries
Worth reading first: Acceptance Criteria and INVEST
How a backlog is kept ready and sorted
Backlog refinement is the steady work of getting items ready to build. The team splits big items, adds detail and acceptance criteria, and sizes them. The Scrum Guide calls it ongoing, not a set meeting. Many teams still hold one session a week, often about an hour long.
The aim is to keep about one or two sprints of work ready at the top. More than that is wasted effort, because items lower down will change before anyone builds them. Less than that, and planning turns into a long session of writing stories from scratch.
The Product Owner brings the items and explains why they matter. The Developers ask questions, spot gaps and size the work. Only the people who will build it can say how big it is.
The MoSCoW method helps sort items, often for one release. Must have: the release fails without it. Should have: important, but it can wait. Could have: nice if there is time. Won't have this time: agreed to leave out for now.
The won't have group is the useful one. Writing down what is left out ends the same argument coming back every week. It also tells people their idea was heard, just not chosen this time.
MoSCoW only works if the must haves are honest. If 90% of the work is marked must, there is nothing to cut when time runs short. Many teams keep the must haves well under the time they have, so the should and could items act as a cushion.
The common mistake is skipping this work when the team is busy. The next planning meeting then stalls on stories nobody understands. An hour of it a week often saves three hours at planning.
Worked example
Emma sorts a release with MoSCoW
Emma has 30 items for a 3-month release of a banking app. At first her managers call 24 of them must haves.
She asks which ones the release would fail without. That leaves 12 musts, 8 shoulds, 6 coulds and 4 won't haves. When one sprint is lost to a server move, 3 coulds are dropped and every must still ships.
The words for this lesson2
Check yourself
What does the W in MoSCoW stand for?
Finished this lesson?
Marking it complete also marks its 2 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.