MoSCoW prioritization template
Split a release's scope into Must, Should, Could and Won't-have-this-time so everyone agrees what ships.
Use this templateFree, opens in your browser. No sign-up.
What's on the board
- Must have — release fails without it
- Sign up with email · Create and share a board · Data saved reliably
- Should have — important, not vital
- Google sign-in · Export to PDF
- Could have — nice if time allows
- Custom themes · Keyboard shortcut cheatsheet
- Won't have (this time)
- Native mobile app · Offline sync
How to use this template
- Click Use this template. It opens in the Kelvo app as a new board, saved in your browser.
- Double-click any box to change its text. Replace the examples with your own content.
- Add notes fast. Press S for a sticky note in the middle of your view. A sticky is a box like any other: link it, recolour it, resize it.
- Paste a table. Paste comma- or tab-separated text and it becomes a table. Tab moves to the next cell and adds rows as you go.
- Let Smart Assist draft the next step. Turn on Suggest, finish a label and pause: the next steps appear as dashed ghosts. Tab keeps them, Esc dismisses them.
Good for
- moscow
- prioritization
- scope
- product owner
- release
- Planning a quarter or a release
- Prioritising a long backlog with a shared method
- Connecting outcomes to the work that should move them
Related templates
RICE prioritization
Score features by Reach, Impact, Confidence and Effort to rank a backlog with numbers instead of opinions.
User story map
The user's journey as a backbone of activities, tasks under each, and stories sliced into releases (MVP first).
Feature launch checklist
Everything that has to happen before, on and after launch day, with an owner for each item.
Product vision board
Vision, target group, needs, product and business goals on one page — align the team on why the product exists.
Product backlog
A ranked backlog with type, estimate and readiness, plus backlog health and the next refinement session.
Canary & blue/green deployment
Release safely: shift a little traffic to the new version, check SLOs, then promote or roll back — plus a strategy comparison.