Study guide

10.2 Starting up 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.2 Starting up a Project and Its Agile Workshops

Key Takeaways Explain This Topic AI

Starting up a project is a pre-project process whose purpose is to establish whether there is a viable and worthwhile project before any significant spend.

The project canvas workshop produces the initial project canvas, and it is where user groups are defined and prioritized.

In PRINCE2 Agile the project canvas carries the business case, so the outline business case takes canvas form from the outset.

The release map is first created here, at a coarse level, using epic user stories.

SU is deliberately lightweight — the objective is the minimum needed to justify authorizing initiation, not a full plan.

Last updated: August 2026

10.2 Starting up a Project and Its Agile Workshops

Quick summary: SU is a pre-project process answering one question: do we have a viable and worthwhile project? It is deliberately light. Its agile workshops include the project canvas workshop , in which user groups are defined and prioritized , and the starting up workshop .

Purpose and objectives

The purpose of starting up a project is to ensure the prerequisites for initiating a project are in place. The board should be able to answer: is this a viable and worthwhile project, and do we know enough to authorize spending money on initiating it?

SU exists to solve a specific organizational pathology: projects that begin because someone senior wants visible action, before anyone has asked what the product is, who wants it, or whether it can be built. Its objectives are to establish:

  • That there is a business justification for initiating the project
  • That the necessary authorities exist to initiate it
  • That sufficient information is available to define the project's scope
  • The likely options for delivering the product, and the chosen approach
  • The project management team — the people, appointed and available
  • The plan for the initiation stage — the work needed to lay the foundations
  • Activities

Appoint the executive and the project manager. Nothing else can proceed without accountability.

Capture previous lessons. The learn from experience principle applied at the earliest possible point: what did comparable projects teach us?

Design and appoint the project management team. Including the agile roles the project will use.

Prepare the outline business case. In PRINCE2 Agile this takes the form of the project canvas .

Select the project approach and assemble the project brief. Including whether and how agile will be used.

Plan the initiation stage.

Agile tailoring

Keep it light. SU is the process most damaged by over-documentation. The output is a decision to initiate or not, and it should be reachable in days rather than weeks.

Requirements are captured coarsely. High-level requirements are expressed as epic user stories rather than a detailed specification. Nobody knows enough yet for detail, and detail written now will be invalidated later.

Collaboration replaces circulation. Rather than the project manager drafting a brief and sending it round for comment, SU is run through workshops that get the stakeholders into a room to produce the artifacts together. This is faster and produces genuine shared understanding rather than nominal sign-off.

Assessing agile suitability. SU is where the project first considers whether an agile approach fits — the kind of assessment the Agilometer supports, surfacing agile adoption risks early enough to plan a response.

The project canvas workshop

The project canvas workshop produces the project canvas : the single-page artifact capturing the project's purpose, its users, the outcomes and benefits sought, the constraints and the high-level approach.

Its most examinable feature: user groups are defined and prioritized in the project canvas workshop. This is where personas do their work — turning "the users" into specific, understood groups with an agreed order of importance. Everything downstream depends on it: backlog ordering, release sequencing, and who is consulted about what.

In PRINCE2 Agile the project canvas is more than a summary. It carries the business case — the outline version here, elaborated into the detailed version during initiation. That is why the canvas is a governance artifact rather than a facilitation prop.

The starting up workshop

The starting up workshop builds the early shared understanding SU needs: what problem the project addresses, what the product might be, who is involved, what the options are, and what the initiation stage must do. It is the collaborative vehicle for assembling the project brief and agreeing the project approach.

What is produced

  • Artifact State at the end of SU
  • Project canvas Created — outline form, carrying the outline business case
  • Project brief Assembled
  • Release map First created , coarse, based on epic user stories
  • Project backlog Started, at epic level
  • Lessons log Opened, with lessons from comparable projects
  • Daily log Opened
  • Initiation stage plan Prepared
  • Project management team Designed and appointed

The release map point is worth noting: it is created here, early and coarse, so the board can see the intended shape of delivery before authorizing initiation. It is then refined and updated as plans are documented in later processes.

The exit

SU ends when the project board, in directing a project , authorizes initiation — or declines to. Declining is a legitimate and valuable outcome: SU has done its job if it has stopped an unjustified project before it consumed a budget.