4.2 Project Contexts and the Five Integrated Elements
Key Takeaways
- PRINCE2 has five integrated elements: principles, people, practices, processes, and the project context.
- 'People' became an integrated element in PRINCE2 7, and PRINCE2 Agile Version 2 builds on it with content on teams, leadership, culture and change.
- Practices are what PRINCE2 6 called themes, and there are still seven of them.
- PRINCE2 can be used across many project contexts — commercial and internal, simple and complex, single-team and multi-team, regulated and unregulated.
- The project context element is what makes tailoring a first-class part of the method rather than an afterthought.
4.2 Project Contexts and the Five Integrated Elements
Quick summary: PRINCE2 Project Management is made up of five integrated elements: principles, people, practices, processes, and the project context. Two of these — people as an element in its own right, and practices replacing the older term themes — are Version 7 changes that PRINCE2 Agile Version 2 inherits. Older PRINCE2 Agile material describes only principles, themes and processes, which is a reliable way to spot outdated study notes.
The five integrated elements
They are called integrated because none works alone. Principles without processes are slogans; processes without principles are bureaucracy.
1. Principles
Seven universal, self-validating statements that must all be applied for a project to be a PRINCE2 project. They are the non-negotiables: if you drop one, you are no longer doing PRINCE2. They are covered in full in section 4.3.
2. People
The human dimension of project delivery: leading and building teams, managing the change the project imposes on the organization, communication, culture, and stakeholder engagement.
This element was introduced in PRINCE2 7, in response to long-standing criticism that PRINCE2 was strong on structure and control but comparatively silent on the people who make projects succeed. PRINCE2 Agile Version 2 leans on it heavily — the whole of learning outcome 1.4 in the Foundation syllabus, covering organizational change management, teams, leadership and communication, exists because of it. Chapter 5 of this guide is devoted to it.
3. Practices
Seven aspects of the project that must be addressed continually throughout its life, not set up once and forgotten: business case, organization, plans, quality, risk, issues, progress.
Practices is the Version 7 term for what earlier editions called themes. The list also changed: the old Change theme became the Issues practice. Practices are covered in chapters 6 to 8.
4. Processes
Seven time-ordered sets of activities that carry the project from before it starts to after it finishes: starting up a project, directing a project, initiating a project, controlling a stage, managing product delivery, managing a stage boundary, closing a project. Processes are covered in chapter 10.
5. The project context
The environment in which the project runs — organizational, commercial, regulatory, technical and cultural — and the recognition that this environment determines how the other four elements should be applied.
The project context is what turns tailoring from an informal habit into part of the method. It is the element that makes PRINCE2 Agile possible at all: PRINCE2 Agile is, in essence, detailed guidance on applying the other four elements when the project context includes agile delivery.
How they relate
| Element | Answers the question | Changes between projects? |
|---|---|---|
| Principles | What must always be true? | Never — all seven always apply |
| People | Who does the work, and how are they led and engaged? | Yes — teams and cultures differ |
| Practices | What must be attended to continually? | The seven are constant; how each is applied is tailored |
| Processes | What happens, in what order, and by whom? | The seven are constant; their weight is tailored |
| Project context | Where and under what conditions is this happening? | Always — this is the source of tailoring decisions |
A useful way to hold it: principles are the tests, practices are the aspects, processes are the flow, people do the work, and context decides the dials.
Project contexts in which PRINCE2 can be used
PRINCE2 is deliberately generic. It carries no industry assumptions, no technology assumptions, and no assumption about delivery approach. The contexts it is designed to span include:
- Commercial versus internal. A project delivered by a supplier to a customer under contract, or one delivered inside a single organization. The commercial case brings a customer/supplier relationship that shapes the organization practice and the choice of contract.
- Simple versus complex. A small single-team change, or a multi-team, multi-supplier programme component.
- Single-organization versus multi-organization. Joint ventures, partnerships and consortia change how authority is delegated and how assurance operates.
- Regulated versus unregulated. Regulation constrains the quality practice, the evidence you must retain, and how far documentation can be right-sized.
- Predictive, agile or hybrid delivery. The whole reason PRINCE2 Agile exists.
- Project versus programme or portfolio. A project may stand alone or sit inside a programme that sets its objectives and consumes its outputs.
- Public, private and third sector, each with different benefit definitions — a public-sector project may measure social outcomes where a commercial one measures return.
The point of the list is not to memorise it exhaustively but to internalise the claim behind it: PRINCE2 is scalable and tailorable to any project, which is why tailor to suit the project is a principle and not merely good advice. What is tailored is the weight of the practices, the formality of the processes, and the shape of the artifacts — never the principles.
Which are the five integrated elements of PRINCE2 Project Management?
Which integrated element was introduced in PRINCE2 Version 7 and underpins the Version 2 syllabus content on organizational change management, teams and communication?
Which element of PRINCE2 is the source of tailoring decisions?