MoSCoW Analysis for Beginners | Sort What to Do into Must, Should, Could and Won't

Project & Development

MoSCoW Analysis for Beginners | Sort What to Do into Must, Should, Could and Won't

Beginner | 4 whiteboard pages · Task board: 5 columns (4 parent tasks, 12 subtasks)

Beginner: No technical terms. Just answer the whiteboard's questions, following the examples, and it takes shape.

MoSCoW analysis sorts what you want into Must, Should, Could and Won't to pick what to start first.

Read more Show less

Ask whether skipping it means failure, then name an owner and date for each Must. First write the fixed limits (deadline, people, money, who decides), list everything you want and park it in the four boxes. Then check the Musts fit your people, test each with three questions and votes, and note a reason for every item you drop. Sorting by importance and urgency suits tasks already in hand; MoSCoW suits choosing what goes in within a limited time.

Plan for 4 to 7 people and 90 to 120 minutes. The example follows a cooking school with about 30 students: five staff narrow 20 wishes for a September booking site.

The whiteboard has 4 A4 pages (deadline and questions, sort into four, challenge the Musts, start with the Musts) and 14 numbered frames. The task board has 5 columns, 4 parent tasks and 12 subtasks (16 in all).

0 Likes 0 Copies Author: WeProcess
MoSCoW prioritization scope management narrowing requirements project planning
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Read the whiteboard text as plain text

MoSCoW Analysis Starter Board

How to use (4 pages): ① Page 1: write the goal and deadline, set the decision questions (boards①–③) → ② Page 2: list every wish and park it in four boxes (boards④–⑨) → ③ Page 3: count the Musts, narrow them with three questions and votes (boards⑩–⑫) → ④ Page 4: set owners, dates and signals, Musts first (boards⑬⑭)

1/4 Set deadline and questions

① Goal, deadline and team (start here)

  • What we are narrowing down for e.g. Launch a new booking site in September to cut phone bookings. We have 20 wishes and cannot do them all in time
  • Deadline (cannot move) e.g. Launch on Sept 1. Sign-ups for the new September classes open that day
  • Team e.g. 5 people: the school head, 2 instructors and 2 front desk staff. The head makes the final call

② Meanings and examples (read together)

Must Must have
  • How to fill in: Things that mean failure on the deadline day if missing
  • e.g. Choose a class and time and book it
Should Should have
  • How to fill in: Important, but something else keeps it going for a while
  • e.g. Cancel a booking on screen (for now the front desk takes cancellations by phone)
Could Could have
  • How to fill in: Nice to have, but bookings work without it
  • e.g. A profile page for each instructor
Won't Not this time
  • How to fill in: Decided not to do now; leave for another time
  • e.g. An English information page

③ Fixed limits and decision questions

What is decided Why it cannot move Add to questions
Deadline e.g. Launch on Sept 1 e.g. September class sign-ups start that day e.g. Can we take bookings on Sept 1 without it?
People e.g. 5 people, 10 hours a week in total e.g. Built between classes and front desk shifts e.g. Can we finish in 12 weeks, about 120 hours?
Money e.g. Build cost capped at $2,000 e.g. Fixed by this year's school budget e.g. Does it fit within $2,000?
Decider e.g. School head e.g. Someone must decide when votes split e.g. Can the head say we are stuck without it?

2/4 Sort wishes into four

④ Keep ③ in view and list every wish

  • What we want on the booking site
    • Booking e.g. Book or cancel a class and time
    • Payment e.g. Card payment, cash on the day
    • Notices e.g. Confirmation email, day-before reminder
    • About the school e.g. Instructor profiles, food photos
    • For students e.g. Points, class history
    • Front desk work e.g. Booking list, changing open slots

⑤ Must (launch fails without it)

  • How to fill in: Notes from ④ that stop us taking bookings on Sept 1 if missing
  • e.g. Choose a class and time and book it
  • e.g. Open slots are visible on screen
  • e.g. The front desk can see the booking list

⑥ Should (other ways work)

  • How to fill in: Things that phone or paper can cover for a while
  • e.g. Change the booking date and time on screen
  • e.g. Cancel a booking on screen
  • e.g. The front desk changes open slots on screen

⑦ Could (nice to have)

  • How to fill in: Things bookings work without
  • e.g. A profile page for each instructor
  • e.g. A gallery of dish photos
  • e.g. A day-before reminder email

⑧ Won't (left for next time)

  • How to fill in: Things we decide not to do this time
  • e.g. Points feature
  • e.g. Class history
  • e.g. An English information page

⑨ Undecided (what would settle it?)

  • Undecided e.g. Card payment. We do not know if cash on the day alone would trouble students
  • What to check to decide e.g. The front desk asks 10 students whether lacking card payment would trouble them

3/4 Challenge and narrow Musts

⑩ Count ⑤ Musts: are there too many?

  • Number of Musts e.g. 4 of the 20 wishes are parked in ⑤. The 1 in ⑨ (card payment) joins as a Must candidate
  • Does it fit the ③ staffing? e.g. The 4 in ⑤ plus the 1 in ⑨ take about 140 hours, over the 120 in ③, so challenge the Must candidates in ⑪

⑪ Challenge Musts (3 votes per person)

Candidate (from ⑤⑨) Fails without it? Fits people? (hours) Who is hurt if cut?
Candidate 1 e.g. Book a class and time e.g. Yes, it fails. We cannot take bookings e.g. About 40 hours e.g. All students and the front desk
Candidate 2 e.g. Show open slots e.g. Yes, it fails. Phones would not stop ringing e.g. About 20 hours e.g. Students and the front desk
Candidate 3 e.g. Front desk sees booking list e.g. Yes, it fails. No class prep on the day e.g. About 15 hours e.g. 2 front desk staff and instructors
Candidate 4 e.g. Booking confirmation email e.g. No, the front desk can tell them by phone e.g. About 25 hours e.g. Front desk (more calls)
Candidate 5 e.g. Card payment e.g. No, cash on the day works e.g. About 40 hours e.g. Some students

⑫ Kept and dropped, with reasons

  • Kept as Must, and why e.g. Booking, open slots and booking list. All 5 voted for them, and together they take about 75 hours, within the ③ staffing
  • Moved down to Should, and why e.g. Booking confirmation email. In September the front desk tells people by phone; build it in October
  • Dropped, and why e.g. Card payment. Of 10 students asked, only 2 would mind, and cash on the day works

4/4 Start with the Musts

⑬ Line up the ⑫ Musts to the deadline

  1. June Decide the build order e.g. Start with the booking screen. The head reviews the screen drafts and decides
  2. July Build the Musts e.g. Build booking and open slots, and test with 2 instructors at the end of July
  3. August Try it at the front desk e.g. 2 front desk staff run a week of bookings on the booking list
  4. Sept 1 Launch e.g. Send the announcement to 30 students and take bookings alongside phone bookings

⑭ Owners, dates, signals (review day)

What to do Owner Due date Signal and fallback
Must 1 e.g. Book a class and time e.g. Instructor A e.g. July 31 e.g. If booking is not working by late July, change the approach
Must 2 e.g. Show open slots e.g. Instructor B e.g. July 31 e.g. If slots do not match the paper sheet, change it
Must 3 e.g. Front desk sees booking list e.g. Front desk A e.g. Aug 15 e.g. Continue if the front desk can run a week
Should e.g. Booking confirmation email e.g. Front desk B e.g. Oct 31 e.g. If calls pass 10 a day, build it sooner
Review day e.g. 15 minutes every Friday e.g. School head e.g. By Aug 29 e.g. Continue if on plan. If 2 weeks behind, drop one Must and go back to (board⑪)

Task board contents

Not started 16 items

Frame the decision

On page 1, write the goal, deadline and team, agree on the four meanings, then fix the limits and decision questions in the table. Once these are set, sorting on page 2 causes less hesitation. Press Ctrl+F (⌘F on Mac) and enter 3/4 to jump to page 3.

Write the basics

In the three notes on board ①, write why you are narrowing down, the launch date and the roles of the 5 people. Done when all three are filled.

Read the 4 meanings

Read the four columns on board ② together, replace each e.g. with your own wishes and say them one by one. Done when everyone can explain the four differences.

Set fixed limits

In the four rows of the table on board ③ (deadline, people, money, decider), write what is decided, why it cannot move and what to add to the questions. Done when the decider says we sort by this question.

Sort into 4 boxes

On page 2, list every wish and park each one in the four boxes by asking whether skipping it means failure. Listing everything now saves you from coming back later to say that one was a Must too.

List every wish

On the tips of the 6 branches of board ④, add your wishes as sticky notes. Done when everyone says there are no more.

Park in four boxes

Ask of each note on board ④ whether skipping it means failure, and move it to one of the boxes on boards ⑤–⑧. Put undecided notes on board ⑨. Done when no notes are left on ④.

Plan how to check

For each note on board ⑨, write what you need to learn to decide, and who will check it and how. This is the material for the challenge on page 3.

Challenge the Musts

On page 3, check that the Musts are not too many, challenge the Must candidates with three questions and votes, and decide what to keep and what to drop, with reasons. This parent task is the core work and takes the most time.

Count the Musts

Count the notes on board ⑤ and write on board ⑩ the number of Musts and whether the ③ staffing can finish them. If not, write that you will challenge them in ⑪. Done when both notes on ⑩ are filled.

Vote on 3 questions

Copy up to 5 Must candidates into the candidate column of the table on board ⑪, fill the three question columns, then place circle stamps, up to 3 per person. Done when everyone has voted.

Record the reasons

Decide what stays a Must in order of votes, then on board ⑫ write what stays a Must, what moves down to Should and what is dropped, each with its reason.

Start with Musts

On page 4, line up the Musts you kept along the road to the deadline and decide owners, dates and signals. Track what you decide in the Building column of the task board.

Plan the timeline

In the four steps of board ⑬, place the Musts kept in ⑫ in the order you will build them and write what ends each month. Done when the four steps are filled.

Set owners, dates

In the Must and Should rows of the table on board ⑭, write what to do, who owns it and the due date. Done when every row has an owner's name and a date.

Decide by signals

On review day, look at the signal and fallback column of board ⑭ and decide to continue, change or stop. Write the decision with the date in the same row's signal and fallback column; when you stop, go back to the board named there.

Sorting 0 items

Challenging 0 items

Building 0 items

Reviewed 0 items

← Back to templates

Preview mode MoSCoW Analysis for Beginners | Sort What to Do into Must, Should, Could and Won't

Whiteboard preview

① Goal, deadline and team (start here) ③ Fixed limits and decision questions ⑤ Must (launch fails without it) ⑥ Should (other ways work) ⑦ Could (nice to have) ⑧ Won't (left for next time) ⑨ Undecided (what would settle it?) ⑩ Count ⑤ Musts: are there too many? ⑪ Challenge Musts (3 votes per person) ⑫ Kept and dropped, with reasons ⑬ Line up the ⑫ Musts to the deadline ⑭ Owners, dates, signals (review day) MoSCoW Analysis S... How to use (4 pag... Must (fails witho... Should, goals and... Could, limits and... Team and things t... 1/4 Set deadline and ... Ctrl+F / ⌘F : 2/4... → 2/4 2/4 Sort wishes into ... ↙ 3/4 What we are narrowing down fore.g. Launch a new booking site in September to cut phone bookings. We have 20 wishes and cannot do them all in time Deadline (cannot move)e.g. Launch on Sept 1. Sign-ups for the new September classes open that day Teame.g. 5 people: the school head, 2 instructors and 2 front desk staff. The head makes the final call ② Meanings and ex... MustMust have How to fill in: Things that mean failure on the deadline day if missing e.g. Choose a class and time and book it ShouldShould have How to fill in: Important, but something else keeps it going for a while e.g. Cancel a booking on screen (for now the front desk takes cancellations by phone) CouldCould have How to fill in: Nice to have, but bookings work without it e.g. A profile page for each instructor Won'tNot this time How to fill in: Decided not to do now; leave for another time e.g. An English information page What is decided Why it cannot move Add to questions Deadline e.g. Launch on Sept 1 e.g. September class sign-ups start that day e.g. Can we take bookings on Sept 1 without it? People e.g. 5 people, 10 hours a week in total e.g. Built between classes and front desk shifts e.g. Can we finish in 12 weeks, about 120 hours? Money e.g. Build cost capped at $2,000 e.g. Fixed by this year's school budget e.g. Does it fit within $2,000? Decider e.g. School head e.g. Someone must decide when votes split e.g. Can the head say we are stuck without it? ④ Keep ③ in view ... What we want on the booking site Booking e.g. Book or cancel a class and time Notices e.g. Confirmation email, day-before reminder For students e.g. Points, class history Payment e.g. Card payment, cash on the day About the school e.g. Instructor profiles, food photos Front desk work e.g. Booking list, changing open slots How to fill in: Notes from ④ that stop us taking bookings on Sept 1 if missing e.g. Choose a class and time and book it e.g. Open slots are visible on screen e.g. The front desk can see the booking list How to fill in: Things that phone or paper can cover for a while e.g. Change the booking date and time on screen e.g. Cancel a booking on screen e.g. The front desk changes open slots on screen How to fill in: Things bookings work without e.g. A profile page for each instructor e.g. A gallery of dish photos e.g. A day-before reminder email How to fill in: Things we decide not to do this time e.g. Points feature e.g. Class history e.g. An English information page Undecidede.g. Card payment. We do not know if cash on the day alone would trouble students What to check to decidee.g. The front desk asks 10 students whether lacking card payment would trouble them 3/4 Challenge and nar... → 4/4 4/4 Start with the Musts Number of Mustse.g. 4 of the 20 wishes are parked in ⑤. The 1 in ⑨ (card payment) joins as a Must candidate Does it fit the ③ staffing?e.g. The 4 in ⑤ plus the 1 in ⑨ take about 140 hours, over the 120 in ③, so challenge the Must candidates in ⑪ Candidate (from ⑤⑨) Fails without it? Fits people? (hours) Who is hurt if cut? Candidate 1 e.g. Book a class and time e.g. Yes, it fails. We cannot take bookings e.g. About 40 hours e.g. All students and the front desk Candidate 2 e.g. Show open slots e.g. Yes, it fails. Phones would not stop ringing e.g. About 20 hours e.g. Students and the front desk Candidate 3 e.g. Front desk sees booking list e.g. Yes, it fails. No class prep on the day e.g. About 15 hours e.g. 2 front desk staff and instructors Candidate 4 e.g. Booking confirmation email e.g. No, the front desk can tell them by phone e.g. About 25 hours e.g. Front desk (more calls) Candidate 5 e.g. Card payment e.g. No, cash on the day works e.g. About 40 hours e.g. Some students Kept as Must, and whye.g. Booking, open slots and booking list. All 5 voted for them, and together they take about 75 hours, within the ③ staffing Moved down to Should, and whye.g. Booking confirmation email. In September the front desk tells people by phone; build it in October Dropped, and whye.g. Card payment. Of 10 students asked, only 2 would mind, and cash on the day works JuneDecide the build ordere.g. Start with the booking screen. The head reviews the screen drafts and decides JulyBuild the Mustse.g. Build booking and open slots, and test with 2 instructors at the end of July AugustTry it at the front deske.g. 2 front desk staff run a week of bookings on the booking list Sept 1Launche.g. Send the announcement to 30 students and take bookings alongside phone bookings What to do Owner Due date Signal and fallback Must 1 e.g. Book a class and time e.g. Instructor A e.g. July 31 e.g. If booking is not working by late July, change the approach Must 2 e.g. Show open slots e.g. Instructor B e.g. July 31 e.g. If slots do not match the paper sheet, change it Must 3 e.g. Front desk sees booking list e.g. Front desk A e.g. Aug 15 e.g. Continue if the front desk can run a week Should e.g. Booking confirmation email e.g. Front desk B e.g. Oct 31 e.g. If calls pass 10 a day, build it sooner Review day e.g. 15 minutes every Friday e.g. School head e.g. By Aug 29 e.g. Continue if on plan. If 2 weeks behind, drop one Must and go back to (board⑪) → 2/4 Sort wishes into ... ↙ 3/4 Challenge and nar... → 4/4 Start with the Musts
100%

Drag to move, scroll to zoom