Download as PDF, PPTX
![● [ ] Todo (agreed upon by the team and in the Must-Have quadrant)
● - Team is aligned and this requirement is in the correct quadrant
● ? To be discussed (not agreed upon but captured during discussions or any
social interaction)
● 🐽 Team disagreement / May need further discussions or stakeholder
input
● ☑ Done — This requirement has shipped
Keep the document live and
up to date](https://image.slidesharecdn.com/benoitsslides2020-02-19-200315034754/75/The-MoSCoW-Prioritization-Framework-26-2048.jpg)
Uploaded byBenoit des Ligneris
The MoSCoW Prioritization Framework
The document describes a presentation on the MoSCoW prioritization method. The presentation discusses how MoSCoW prioritization can help align teams by establishing clear priorities. It explains the four categories in MoSCoW prioritization - Must have, Should have, Could have, Won't have. The presentation provides tips on running a MoSCoW prioritization session, such as inviting the right stakeholders and using a document to capture agreements and next steps.
More Related Content
Similar to The MoSCoW Prioritization Framework
The MoSCoW Prioritization Framework
- 1.
- 4. TONIGHT’S EVENT SPONSOREDBY Thanks, Shopify!
- 5. Jonathan Laroque Director ofProduct, Slice Labs Jobs to be Done: A Primer Benoît des Ligneris, Ph. D. Sr. Product Manager, Shopify MoSCoW Prioritization Method Jeremy Biffis Technical Manager, TripAdvisor Objectives and Key Results at TripAdvisor TONIGHT’S PRODUCTTANK SPEAKERS
- 6. MoSCoW Prioritization Method Benoît desLigneris, Ph. D. Sr. Product Manager, Shopify #ProductTankOttawa
- 7. MoSCOW Prioritization Method How tocreate better and faster team and stakeholder alignment Benoît des Ligneris, Ph. D. Senior PM @Shopify
- 8.
- 9. ● Lack oftrust ● Passive-aggressive ● Inefficient & unclear ● No healthy conflict ● Low risk-taking ● Low commitment ● No personal responsibility or accountability ● Unclear agreements Unaligned team(s):
- 10. ● Trust ● Open ●Efficient ● Healthy conflict ● High risk-taking ● High commitment ● Personal responsibility and accountability ● Clear agreements Aligned team(s):
- 11. 1. Communicate tostakeholders 2. Communicate to the organization 3. How to say no with empathy Three additional key benefits
- 12. Which method tochoose?
- 13. Multiple possibilities Narrow Scope BroadScope Complex Simple Scorecard (RICE…) Why, Who What, How MoSCoW
- 14.
- 15.
- 16. ● Required forthe release to have the expected outcomes ● Skeleton ● Proven value ● Vital element ● Prerequisite MUST is also an acronym for Minimal Usable SubseT. Must-Have
- 17. ● Impact ● Notindispensable ● Good candidate for the next dev cycle Should-Have
- 18. ● Desirable ● Lackof data / certainty ? ● Missing dependencies (have to wait) Could-Have
- 19. ● Not inthis release/cycle ● Document the “No” as … “Not Yet” ● Focus on the current cycle Won’t-Have
- 20. How to runa MoSCoW meeting?
- 21. 1. Review theexisting document (brief, press-release, etc.) 2. Invite the team: a. core-team members b. passionate stakeholders c. subject experts 3. Book 1h 4. Decide on an approach Preparation
- 22.
- 23.
- 24.
- 25. 1. 10 minutesbefore the end: the quadrant walk-through 2. If not complete: a. Book another meeting b. Re-start with all the agreed upon decisions and check if everyone is still OK c. Continue the process Tips & Tricks
- 26. ● [ ]Todo (agreed upon by the team and in the Must-Have quadrant) ● - Team is aligned and this requirement is in the correct quadrant ● ? To be discussed (not agreed upon but captured during discussions or any social interaction) ● 🐽 Team disagreement / May need further discussions or stakeholder input ● ☑ Done — This requirement has shipped Keep the document live and up to date
- 27.
- 28. 1. Simple touse prioritization method 2. Perfect for pre-scoped products/features 3. Visual representation of the decisions on one page 4. Keep it live & start a new prioritization session once your Must-Have are 80% done Reference: How to run a MoSCoW prioritization session Conclusion