Study guide
10.4 Initiating a Project and Its Agile Workshops
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
10.4 Initiating a Project and Its Agile Workshops
Key Takeaways Explain This Topic AI
Initiating a project establishes solid foundations for the project, so everyone understands the work before committing to delivery.
It has seven activities covering tailoring, the management approaches, project controls, the project plan, the detailed business case and assembling the PID.
The project initiation workshop aligns the team on vision, objectives and goals and develops the detailed project canvas.
The project kickoff workshop forms the delivery team — introductions, values and norms, decision-making and the team dashboard.
Tailoring decisions, including how agile will be used, are agreed and recorded here rather than left to emerge.
Last updated: August 2026
10.4 Initiating a Project and Its Agile Workshops
Quick summary: IP exists to establish solid foundations for the project . It runs during the initiation stage, after the board has authorized initiation. Its two agile workshops are the project initiation workshop and the project kickoff workshop .
Purpose
The purpose of initiating a project is to establish solid foundations for the project, enabling the organization to understand the work needed to deliver the products before committing to significant spend.
Solid foundations is the phrase that identifies IP in a purpose question.
The seven activities
- Activity What it settles
- Agree the tailoring requirements How PRINCE2 will be scaled for this project, including how agile will be used
Agree the management approaches Risk, quality, issue and communication management approaches, plus the benefits management approach and sustainability approach
Set up the project controls Stage structure, tolerances, reporting cadence, dashboards, the change authority and any change budget
- Create the project plan The overall plan, including the release map
- Prepare the detailed business case Elaborating the outline case from SU
- Assemble the project initiation documentation Bringing the above into an agreed whole
- Request authorization to deliver the project Presenting the PID, project canvas and release map to the board
These need not run sequentially. They overlap and are revisited — deciding the tailoring changes the controls, and creating the plan changes the business case.
The project canvas becomes the detailed business case
In PRINCE2 Agile the project canvas carries the business case . The outline canvas created in SU is developed here into the detailed version, incorporating what planning has revealed: the release map, the benefit forecast per release, the confirmed user group priorities and the tailoring decisions.
Presenting the detailed canvas and release map to the board, and formally requesting authorization to deliver, is a separate step from the workshops themselves.
The project initiation workshop
The project initiation workshop aligns the people who will deliver the project on the same picture. It:
- Establishes shared understanding of the vision, objectives and goals
- Develops the detailed project canvas , drawing on lessons gathered in SU
- Works through the management approaches and controls collaboratively rather than by circulating drafts
- Surfaces disagreement early, while it is cheap to resolve
The project manager prepares by reviewing the daily log and lessons log and assembling the project documentation so the workshop starts from evidence rather than from a blank page.
The project kickoff workshop
Where the initiation workshop aligns the project, the project kickoff workshop forms the team . It establishes:
Team introduction — the element that fosters familiarity and establishes connections , and the foundation of the psychological safety the team will need
- Team values and norms — the working agreements governing how the team operates
- Decision-making arrangements — often a team decision matrix, frequently arrived at through delegation poker
- The team dashboard — how the team will make its work visible
Getting these agreed before delivery starts is what separates a group of individuals assigned to a project from a team.
Agile tailoring of IP
Right-size the documentation. The PID is assembled, but its components can be short and can point to living artifacts. A management approach that fits on a page and is followed beats one that runs to twenty pages and is not read.
Record the tailoring decisions explicitly. Which agile approach the teams will use, how tolerances are set, what the Definition of Done contains, how progress will be reported, what the change authority may approve. Recording these is what makes tailoring deliberate rather than drift.
Agree the Definition of Done with governance. Because quality is a target held firm, the board needs to know what the guarantee actually is. This is a governance artifact as much as a team one.
Plan in layers. IP produces the project plan and the release map, not a detailed schedule of every iteration. Detail is added progressively.
Set up the controls that make agile governable. Dashboards rather than reports, a change budget so that ordinary change does not become an exception, and a delegated change authority so decisions do not queue.
What is produced
- Artifact State at the end of IP
- Project initiation documentation Assembled
- Project canvas Detailed — carrying the business case
- Release map Created within the project plan
- Project plan Created
- Management approaches Agreed — risk, quality, issue, communication, benefits, sustainability
- Project controls Set up, including tolerances and dashboards
- Definition of Done Agreed and visible
- Team working agreements and dashboard Established in the kickoff workshop