Prince II
Prince II is a project management framework for delivering change projects, emphasizing principles such as justified project continuation, clear roles, stage-based work, escalation tolerances, context adaptation, and continuous learning.
THE IDEA
Prince II
Prince II is a framework for delivering change projects. The excerpt highlights these principles:
- Ensure the project justification is refreshed and don't be afraid to stop;
- Have clear roles and responsibilities both within the project and around it;
- Work in stages;
- Escalate things following clearly defined tolerances;
- Adapt what you are doing to suit the context;
- Learn as you go.
Other project and programme management frameworks exist (e.g. the PMI PMBOK), with variations in what is regarded as important, depending on their history and focus.
The excerpt also discusses the limits of making firm plans upfront. Detailed planning depends on how well the requirements are understood and how likely they are to change. Where customer needs or regulations remain uncertain, teams need opportunities to reassess the plan as they learn.
When to use it
Managing a construction project with clear milestones, fixed budgets, and regulatory approvals.
Implementing a new IT system in a large organization where requirements are stable and scope is well-defined.
Planning a public sector initiative that requires strict adherence to tolerances and regular reporting to stakeholders.
FROM THEORY TO EVERYDAY LIFE
In practice
Applying Prince II to Software Development
A software development team uses Prince II to manage a new product launch. The project is divided into stages: initiation, design, build, test, and deployment. At the end of each stage, the project board reviews the business case and decides whether to continue. Roles are clearly defined—the project manager handles day-to-day activities, the senior user represents customer needs, and the executive sponsors the project. Tolerances for time and cost are set, and any deviation outside these tolerances is escalated for decision-making. Lessons learned are documented and applied to future stages.
Using Prince II for a Marketing Campaign
A marketing team applies Prince II to a campaign for a new product. The project justification is based on projected sales uplift. The campaign is planned in stages: research, creative development, media buying, execution, and analysis. Each stage has clear deliverables and budget tolerances. When customer feedback during the research stage suggests a different message, the project board is informed and decides to adapt the creative approach, ensuring the project remains aligned with market needs.
A MOMENT TO REFLECT
Put it to work.
How does the Prince II principle of continually refreshing project justification help avoid the sunk cost fallacy?
In what types of projects is the stage-based approach of Prince II most effective, and where might it be less suitable?
How can the escalation tolerances in Prince II empower project managers while maintaining senior management control?
Often confused with
CONTINUE THE CONVERSATION
Source texts
- Beyond the Five Whys Root Cause Analysis and Systems Thinking (James C. Paterson)