Study guide
2.3 The Agile Mindset and the Agile Onion
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
2.3 The Agile Mindset and the Agile Onion
Key Takeaways Explain This Topic AI
The Agile Onion has five layers, from the outside in: processes, practices, principles, values and mindset.
The outer layers are the easiest to see and copy but the least consequential; the mindset at the centre is the hardest to change and the most decisive.
Key characteristics of the agile mindset include empowerment, transparency, adaptability, respect, collaboration and a commitment to continual learning and improvement.
Empowerment is the mindset characteristic that specifically promotes autonomy and self-management within teams.
Changing an organization by installing processes at the outer layer without touching the mindset at the core is why agile adoptions stall.
Last updated: August 2026
2.3 The Agile Mindset and the Agile Onion
Quick summary: The Agile Onion has five layers. From the outside in : processes → practices → principles → values → mindset . Outer layers are visible and easy to copy; inner layers are invisible and hard to change. Real agility is built from the inside out, which is why installing processes alone fails.
The five layers
The Agile Onion is the model PRINCE2 Agile uses to explain why so many agile adoptions produce ceremony without change. Learn the layers in order , because ordering questions are common.
Layer Position What it contains Visibility Ease of change
Processes Outermost Named frameworks and their events: Scrum sprints, stand-ups, reviews, Kanban boards Highly visible Easy — adopt in weeks
Practices Second Concrete techniques: user stories, estimation, burn charts, Definition of Done, pairing, continuous integration Visible Fairly easy — learned with training
Principles Middle The reasoning that justifies the practices, such as the twelve principles behind the Agile Manifesto Semi-visible Harder — requires understanding, not instruction
Values Fourth What the organization actually prioritizes when there is a conflict: courage, openness, focus, respect, commitment Largely invisible Hard — shown in decisions, not statements
Mindset Core How individuals fundamentally think about work, uncertainty, failure and other people Invisible Hardest — changes slowly, through experience
The insight the model encodes is an inverse relationship: the easier a layer is to adopt, the less difference it makes on its own. Buying a tool and running sprints changes the processes layer in a fortnight and changes outcomes not at all. Shifting the mindset takes years and changes everything.
If a question asks which layer promotes continual learning, improvement and flexibility , the answer is the mindset — it is the layer at which the disposition to learn actually resides. Processes and practices are how that disposition gets expressed; they do not create it.
Characteristics of the agile mindset
The syllabus expects you to define the key characteristics of the agile mindset. The ones to know:
Empowerment. Decisions are taken by the people closest to the work. This is the characteristic that specifically promotes autonomy and self-management within teams — if a question phrases it that way, empowerment is the answer, not transparency or adaptability.
Transparency. Information is open by default — progress, problems, quality and risk are visible without having to be requested.
Adaptability. Change is treated as expected information rather than as a failure of planning.
Respect. People, their expertise and their time are treated as valuable; disagreement is possible without hostility.
Collaboration. Work is done together across roles and organizational boundaries, rather than handed between silos.
Continual learning and improvement. Every increment and every retrospective is treated as a source of evidence about how to work better.
Customer focus. Value to the user is the measure of success, ahead of internal process compliance.
Comfort with uncertainty. Committing to a direction and learning by delivering, rather than demanding certainty before starting.
These are dispositions, not activities. You cannot mandate them in a process document; you build them by leadership modelling, by coaching, and by making it demonstrably safe to raise problems.
Reading the Onion in both directions
From the outside in — the diagnostic use. When an adoption is disappointing, ask how deep it went. Are we running sprints but still punishing teams for missed forecasts? Then we changed the processes layer and left the values layer untouched.
From the inside out — the design use. When you are trying to build agility deliberately, start at the core. Establish psychological safety, model the behaviour you want at leadership level, and let the practices be chosen by teams that already understand why they exist. Practices adopted by people who understand the principles behind them survive; practices imposed on people who do not, decay.
Why this matters for a governed project
In a PRINCE2 Agile context the Onion has a specific practical use: it tells the project manager where to intervene.
If a delivery team's iterations are not producing usable increments, the temptation is to add process — more reporting, tighter work packages, closer supervision. That is an outer-layer intervention, and it usually makes things worse by removing the autonomy the team needs.
The Onion suggests asking one layer deeper each time. Is the team empowered to make the decisions its work requires? Is it safe for them to say the increment will not be ready? Does the organization actually value working product over a green status report? Those are values and mindset questions, and they are where the real constraint usually sits.