Study guide

4.2 Project Contexts and the Five Integrated Elements

PRINCE2 Agile Foundation Version 2

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: The Version 2 Exam & PRINCE2 Agile Essentials

1.1 About the PRINCE2 Agile Foundation (Version 2) Exam 1.2 What PRINCE2 Agile Is and How to Blend Project Management with Agile 1.3 PRINCE2 Agile Key Terms You Must Be Able to Define

2 Chapter 2: Agile and the Agile Mindset

2.1 What Agile Is, Why It Is Needed, and Agile in Projects and BAU 2.2 Being Agile vs Doing Agile, and the Benefits of Both 2.3 The Agile Mindset and the Agile Onion 2.4 The Agile Manifesto and Popular Agile Approaches

3 Chapter 3: Key Agile Concepts and Techniques

3.1 User Stories, Agile Estimation, and the Definitions of Ready and Done 3.2 MVP, Burn Charts, Workshops and Agile Events

4 Chapter 4: PRINCE2 Project Management Foundations

4.1 Projects, Project Management and the Seven Performance Targets 4.2 Project Contexts and the Five Integrated Elements 4.3 The Seven PRINCE2 Principles 4.4 Agile Scaling and Agile Transformation Success Factors

5 Chapter 5: People and Organizational Change Management

5.1 Organizational Change Management: Definition, Stakeholders and Culture 5.2 How Agile Supports Change Management and How PRINCE2 Addresses People 5.3 Project Teams, Leading Effective Teams and Communication

6 Chapter 6: PRINCE2 Agile Essentials — Principles and Practices

6.1 How the PRINCE2 Principles Support the Agile Context 6.2 The Purpose of the Seven PRINCE2 Agile Practices

7 Chapter 7: The Practices (Part 1) — Business Case, Organization, Plans

7.1 The Business Case Practice in an Agile Context 7.2 The Organization Practice in an Agile Context 7.3 The Plans Practice in an Agile Context 7.4 Plans Artifacts and Techniques: Release Maps, Timeboxes and Estimation

8 Chapter 8: The Practices (Part 2) — Quality, Risk, Issues, Progress

8.1 The Quality Practice in an Agile Context 8.2 Quality Artifacts and Techniques: Ready, Done and Continuous Testing 8.3 The Risk Practice in an Agile Context 8.4 The Issues Practice in an Agile Context 8.5 The Progress Practice in an Agile Context 8.6 Progress Artifacts and Techniques: Burn Charts and Dashboards

9 Chapter 9: The Eleven PRINCE2 Agile Roles

9.1 Directing and Managing Roles 9.2 Delivery Roles: Coaches, Product Owner, Developer and Tester

10 Chapter 10: The Processes and Their Agile Workshops

10.1 The Purpose of the Seven PRINCE2 Agile Processes 10.2 Starting up a Project and Its Agile Workshops 10.3 Directing a Project and Its Agile Workshops 10.4 Initiating a Project and Its Agile Workshops 10.5 Controlling a Stage and Its Agile Workshops 10.6 Managing Product Delivery and Its Agile Workshops 10.7 Managing a Stage Boundary and Its Agile Workshops 10.8 Closing a Project and Its Agile Workshops

11 Chapter 11: The Wider Context, AI, and Exam Preparation

11.1 PRINCE2 Agile Beyond the Project Environment 11.2 How AI Can Support PRINCE2 Agile 11.3 Version 1 to Version 2: What Changed and Common Traps 11.4 Final Review and Exam-Day Strategy

4.2 Project Contexts and the Five Integrated Elements

Key Takeaways Explain This Topic AI

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.

Last updated: August 2026

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.

Loading diagram... The five integrated elements