MoSCoW prioritisation methodIncludes Foundation & Practitioner combined option.
Key takeawaysAI in Project Management
MoSCoW helps teams make clear trade-offs so the most valuable work is delivered first.Learn how to use AI tools in everyday project work.
- MoSCoW categorises requirements into Must, Should, Could, and Won’t to create shared priorities.ARTIFICIAL INTELLIGENCE (AI)
- Focusing on Must items reduces risk by protecting the minimum needed for success.BCS AI
- Should and Could items provide flexibility when time, budget, or resources tighten.Foundation
- Won’t items prevent scope creep by explicitly deferring low value work.Learn the fundamentals of artificial intellegence.
- Running a workshop with post-it notes and tracking outcomes on a Kanban board keeps alignment high.AI Project Governance Framework (AIPGF)
Scrum Master Could Choose Scrum Alliance or Scrum.org Scrum Master training courses.WScrum Product Owner on’t. MoSCoW analysis helps teams understand which requirements or tasks they should focus on. MoSCoW was invented by Oracle employee Dai Clegg in 1994 and is the most common prioritisation technique used on agile projects.Choose Scrum Alliance or Scrum.org Product Owner training courses.
Why should I use it?4-day course including Foundation.
MoSCoW prioritisationPMI is a highly effective way for a project team to prioritise its work. Focussing on the most important tasks means they can get the main components of the project finished quickly, before the fancy bits are added later. It keeps the entire team on the same page, ensuring everyone knows what is being worked on.®
Using MoSCoW also means both customer and project team might decide that some requirements don’t even need to be there. It helps cut out unnecessary things and keeps things lean, agile and simple. MoSCoW analysis is one of the aspects of PMI-PBA agileSelf-paced course to prepare you for the exam (exam not included). that helps the team minimise wasted time, effort, resources and money.Business Analysis Learning Library (BALL)™
How to use itCHANGE MANAGEMENT
the MoSCoW prioritisation technique is simple to use. Firstly, you’ll need a list of the customer’s requirements. A great way to use MoSCoW is in a workshop with users. Brainstorm a list of requirements, writing each one on a post-it note and then apply MoSCoW.APMG Change Management
It is also commonly used during Foundation ScrumLearn the fundamentals of enterprise change management. planning meetings to prioritise Practitioner user storiesIncludes Foundation & Practitioner combined option. for the next sprint.PROGRAMME MANAGEMENT
So, with your list of requirements, ask whether each requirement is one of the following:MSP
Must®
A requirement which must be completed and is vital for the project’s success. Without this requirement, the project will likely fail.Foundation
ShouldLearn the fundamentals of programme management.
Whilst these requirements are important, they can be delayed if time, resources or money are tight. They are not as time-critical as musts.Practitioner
CouldIncludes Foundation & Practitioner combined option.
These requirements are not necessary, but they can be completed if there’s enough time.INFORMATION TECHNOLOGY (IT)
Won’tITIL
These requirements are the least critical and can be completed at a later stage.®
Let’s use an example. Your customer wants a new e-commerce website for their small clothing business. Their requirements for this project are:Foundation
- It needs a homepageLearn the fundamentals of ITIL service management.
- It needs product pagesStrategist DPI
- Each product needs a photo and description3-day ITIL Strategist: Direct, Plan & Improve (DPI) course.
- There needs to be a shopping cart
- There needs to be an about us page
- There needs to a be a terms & conditions, returns page
- There should be a banner with special deals
- There should be live chat
- It would be nice to have social media buttons
- It would be nice to have a pop up for subscribing to mailing lists
- Perhaps there can be a blog, but not sure
Using MoSCoW, you might want to prioritise these requirements like this:
Must
Homepage, product listings, product photos and descriptions, shopping cart, about us page, returns page, terms & conditions page.Specialist: DSV
Should3-day ITIL Specialist: Drive Stakeholder Value (DSV) course.
Banner and live chatSpecialist: CDS
Could3-day ITIL Specialist: Create, Deliver and Support (CDS) course.
Social mediaIT Learning Library (ITLL)™
Won’tBUSINESS LEARNING LIBRARY (BLL)™
Blog Once prioritised, your team will know which requirements to work on first. To help keep everyone on the same page, it’s highly recommended you use a Kanban board. This can be a physical board in the office, or you can investigate digital boards, such as KanbanFlow and Trello.Agile Learning Library (ALL)™
SummaryP3O COURSES
Overall, the MoSCoW technique is an excellent tool for any agile project team. It brings focus and simplicity to everyday work, cuts down on wasted time and effort, and keeps everyone working towards the same goals. It can even be used outside projects on business as usual activities.Select your preferred training course below:
If you’re interested in learning how the MoSCoW method is used on agile projects, check out our Agile PM coursesWORKSHOPS and Select your preferred workshop below:Agile PM online courses .AGILE QUALIFICATIONS