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
Some good news, Axelos have given us a preview of the new PRINCE2 Agile guide. This preview also includes a simple high level overview of each chapter
So you can read the first three chapters of the PRINCE2 Agile guide and remember the publication date is 14 June 2015
AXELOS will be launching ‘PRINCE2 Agile’ within a matter of weeks. But what’s in the new product? What will it look like? A large team has been working on this for over a year, and if you would like to be one of the first to get answers to those questions then why not attend this webinar and find out?
This webinar will be presented by Keith Richards, Lead Author and Chief Examiner for PRINCE2 Agile. This is an opportunity to learn about what is in the course and how you can benefit from PRINCE2 Agile.
This session will look at:
• Why combine PRINCE2 with agile?
• What are their respective strengths?
• Where are the two approaches complimentary?
• What are the challenges when combining the two?
• How do you address the common misconceptions of agile and PRINCE2?
• Why PRINCE2 is NOT a ‘traditional’ approach to project management?
• How do you create a culture where they can operate together?
• How do you incorporate Scrum and Kanban?
• Where does the Scrum Master and Product Owner fit in?
• What are the benefits? How will it help your organisation?
• What does the new training course and examination look like?
Currently, there are many concepts that are trying to address the need to manage agile in wider context, but is this reinventing the wheel? PRINCE2 is a proven project management approach and is an industry standard that supports the principles and processes that can take agile to greater heights.
Why not attend and see if PRINCE2 Agile addresses your needs when working in agile environments? You may be surprised by the outcome!
After registering, you will receive a confirmation email containing information about joining the webinar.
There’s a simple FAQ by AXELOS that answers some of the frequent questions, such as:
Agile delivery principles are increasingly attracting the attention of organizations looking for the most appropriate approach to help meet their project objectives.
Michelle RowlandBut, buyer beware! Agile methods alone may not supply sufficient control within projects to ensure they are meeting business needs. Therefore, organizations need to know how to combine agile with other project management methodologies.
There would be only a PRINCE2 Agile Practitioner level exam and certification. Candidates have to be PRINCE2 Practitioner certified before taking the exam.
This might limit the exposure of this new system, since it’s harder to get certified and it might discourage some people who might have otherwise get involved. It’s also harder for companies who want to adopt it: since they could ask their team members to get the Foundation level certificate to understand the general idea and have the common language; but they can’t.
It’s the current decision. Let’s hope AXELOS revises it.