Chapter 25 of the new PRINCE2 Agile Guide is focused on Requirements and this includes the MoSCoW which is used for prioritisation (Prioritise Requirements – MoSCoW)
This chapter describes how to define and prioritize requirements in terms that are compatible with agile ways of working.
Here is a 20 minute video explains one of the best prioritization techniques which is MoSCoW and is use to prioritise requirements. Understanding and using this technique is really helpful for IT projects, as long as other kinds of projects.
Besides the use of MoSCoW prioritization for management of scope, as it’s done in some Agile methods, it can also be used for prioritization of acceptance criteria, as recommended in PRINCE2.
So, hope you would enjoy this video and find it helpful:
This use of MoSCoW was first developed by Dai Clegg of Oracle UK Consulting and he subsequently donated the intellectual property rights to the Dynamic Systems Development Method (DSDM) Consortium.
MoSCoW is often used with timeboxing, where a deadline is fixed so that the focus can be on the most important requirements. MoSCoW is also seen as a core aspect of rapid application development (RAD) software development processes and agile software development techniques.
MoSCoW is a technique used in management, business analysis, and software development to reach a common understanding with stakeholders on the importance they place on the delivery of each requirement. This is also known as MoSCoW prioritization or MoSCoW analysis.
See the PRINCE2 Agile Group on LinkedIn for more information
Page: Prioritise Requirements – MoSCoW