All frameworks and cheat sheets

Donut chart

The MoSCoW 60-20-20 rule: team effort per timebox

Donut chart of the MoSCoW 60-20-20 rule: Must Have work capped at 60% of team effort, with about 20% each for Should Have and Could Have.
Measured in effort, not feature count. The Could Have slice is your buffer. Source: Agile Business Consortium, DSDM Agile Project Framework, 2014

A donut chart of how DSDM splits team effort across one MoSCoW timebox: no more than 60% on Must Haves, about 20% on Should Haves and about 20% on Could Haves, which act as the contingency. Use it to sanity-check a release plan before you commit. If Must Haves take far more than 60% of the estimate, there is no room left for surprises. Koji interviews can show which items customers say they could not do without.

Where this appears

What's in this donut chart

Share
Must Have60%
Should Have20%
Could Have (contingency)20%

Shares of team effort in one timebox, not of feature count. Must Have is a ceiling.

Use this image

Free to use in your docs, decks and posts under CC BY 4.0, as long as you credit Koji with a link to this page. To embed it, paste this into your page:

html
<a href="https://www.koji.so/visuals/moscow-60-20-20-rule-effort-split-donut"><img src="https://www.koji.so/visuals/moscow-60-20-20-rule-effort-split-donut/moscow-60-20-20-rule-effort-split-donut.png" alt="Donut chart of the MoSCoW 60-20-20 rule: Must Have work capped at 60% of team effort, with about 20% each for Should Have and Could Have." width="1200" height="750" /></a>
<p>Source: <a href="https://www.koji.so/visuals/moscow-60-20-20-rule-effort-split-donut">The MoSCoW 60-20-20 rule: team effort per timebox</a>, Koji</p>