Study guide
2.1 What Agile Is, Why It Is Needed, and Agile in Projects and BAU
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.1 What Agile Is, Why It Is Needed, and Agile in Projects and BAU
Key Takeaways Explain This Topic AI
Agile is a family of behaviours, frameworks, concepts and techniques for delivering iteratively and incrementally, not a single named method.
The need for agile comes from uncertainty: when requirements will be discovered rather than specified, a sequential approach commits to the wrong answer early.
Iterative means repeating cycles that refine the product; incremental means delivering usable slices of it. Agile approaches are normally both.
Agile applies to business as usual as well as projects — BAU is ongoing, repeatable work with no defined end, whereas a project is temporary and unique.
A common misconception is that adopting an agile framework alone will deliver benefits; the framework is only the outer layer of the change.
Last updated: August 2026
2.1 What Agile Is, Why It Is Needed, and Agile in Projects and BAU
Quick summary: Agile is a family of behaviours, frameworks, concepts and techniques that deliver work iteratively and incrementally with continuous feedback. It exists because a great deal of modern work is uncertain: the requirements are discovered by building, not by specifying. Agile applies to both projects (temporary, unique) and business as usual (ongoing, repeatable).
Defining agile
There is no single thing called "agile". The word covers a family of approaches that share a set of commitments:
Work is delivered in small, frequent increments rather than one large hand-over.
Requirements are expected to emerge and change , and change is welcomed rather than resisted.
Feedback loops are short — the team learns from real users and real working product, quickly.
Teams are cross-functional and self-managing within agreed boundaries.
Progress is measured by working product , not by documents completed.
Scrum, Kanban, Lean and Lean Startup are all members of the family, and they differ substantially. Scrum organizes around fixed-length iterations and defined events; Kanban organizes around flow and limiting work in progress; Lean is a broader philosophy focused on eliminating waste; Lean Startup is oriented to validated learning about a product idea. Recognising that these are different tools for different situations — rather than competing brands of the same thing — is part of the Foundation syllabus.
Why agile is needed
The need for agile is fundamentally a response to uncertainty .
A sequential approach makes its largest commitments at the point of least knowledge. You specify everything at the start — when you know the least about the users, the technology and the market — and then spend months executing that specification. If the specification was wrong, the error is not discovered until acceptance testing, by which time correcting it is enormously expensive.
Agile inverts this. It commits to a direction rather than a specification , and it buys information cheaply by delivering something small and looking at what happens. Concretely, the need arises when:
Requirements are not fully knowable up front. Users cannot describe what they want until they see something.
The environment changes faster than the project runs. Markets, regulation and competitors move during delivery.
Feedback is available and valuable. There are real users who can react to a real increment.
The cost of being wrong late is high. Early detection of a wrong assumption is worth paying for.
Where none of these hold — a well-understood, stable, heavily regulated build with no useful early feedback — a more sequential approach is a legitimate choice. PRINCE2 Agile is explicit that agile is not universally superior.
Iterative and incremental
These two words are frequently used interchangeably. They are not the same thing, and the distinction is examinable.
Meaning Analogy
Iterative Repeating cycles that refine and improve the same thing Sketching a portrait, then progressively refining the whole sketch
Incremental Delivering the product in usable slices , each adding capability Painting the portrait one finished section at a time
Most agile approaches are both : each iteration produces an increment that is potentially usable, and later iterations refine what earlier ones produced. The combination is what makes early benefit realization possible — you can release increment one while iterating on increment two.
A common misconception
The syllabus specifically expects you to recognise the misconception that adopting an agile framework alone will deliver the benefits .
Organizations routinely install Scrum events, rename their project managers, buy a tool, and then find nothing improves. The framework is the outermost, most visible layer of agile, and it is also the least consequential without the layers beneath it. Without a genuine change in mindset, values and behaviour, the ceremonies become theatre: stand-ups turn into status reports to a manager, retrospectives produce actions nobody implements, and the backlog becomes a requirements document with a new name.
By contrast, the following are true of agile and are therefore not the misconception: agile is about empowering teams; agile focuses on producing higher-quality products; agile enables teams to minimize waste and reduce delays.
Projects and business as usual
PRINCE2 Agile applies to project work and to business as usual (BAU) , and expects you to distinguish them.
- Project Business as usual
- Duration Temporary — a defined start and end Ongoing, no defined end
- Output Unique product, service or result Repeatable, routine output
- Purpose Introduces change Sustains steady-state operations
- Team Cross-functional , assembled for the project Standing operational team
- Governance Project board, business case, stages Line management, operational budgets
The four characteristics of a project worth memorising are that it is temporary , unique , introduces change , and is delivered by a cross-functional team. If a question asks which characteristic implies that a project has a start and an end, the answer is temporary .
Agile fits BAU very naturally — a Kanban board managing a stream of support requests is agile without being a project. What BAU lacks is a business case, a defined end, and a project board, so the PRINCE2 governance apparatus is not applied to it. PRINCE2 Agile's guidance on tailoring practices to BAU matters most at the boundary: when a project closes, its product transitions into an operational environment where BAU teams take it on.