Manuals / Product Thinking / Chapter 6

B · Learning · beginner · ~25 min · Chapter 6 of 9

Prioritization: MoSCoW

Must / Should / Could / Won’t (this time). Excellent for release scoping and stakeholder alignment.

Path progress
67%

Step 1 of 1

Force the Won’t

If there is no Won’t, Must will eat the release.

Force the Won’tDrag stickies · tap for tips
Study mapDrag stickies · tap for tipsKeep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Assert the UIdrag · tap →Retry wiselydrag · tap →Seed datadrag · tap →Close the loopdrag · tap →Keep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Pathwise hackdrag · tap →Force the Won’tdrag · tap →Try thisdrag · tap →Follow the dashed drag · tap →

Do this now

Classify 10 backlog items. Cap Must at 40% of the list.

Pro tip: Must = release fails without it. Be ruthless.

Was this step clear?
Chapter learning outcomes
  • MoSCoW categories
  • Won’t as a feature
  • Must inflation

Clear these before you leave