PRINCE2 Agile® Foundation

1. Understand key concepts relating to projects and PRINCE2

1.1 Recall the PRINCE2 principles

1. Continued business justification
2. Learn from experience
3. Defined roles and responsibilities
4. Manage by stages
5. Manage by exception
6. Focus on products
7. Tailor to suit the project

1.2 Explain the purpose of the PRINCE2 themes:

1. Business case
2. Organization
3. Quality
4. Plans
5. Risk
6. Change
7. Progress

1.3 Explain the purpose of the PRINCE2 processes

1. Starting up a project
2. Initiating a project
3. Directing a project
4. Controlling a stage
5. Managing product delivery
6. Managing a stage boundary
7. Closing a project

1.4 Explain the purpose of the following PRINCE2 management products

1. Business case
2. Checkpoint report
3. Highlight reports
4. Project brief
5. Project initiation documentation
6. Project product description
7. Work package

1.5 Explain the responsibilities of the following PRINCE2 roles

1. Project board
2. Executive
3. Senior user
4. Senior supplier
5. Project manager
6. Team manager

2. Understand key concepts relating to projects and PRINCE2 Agile

2.1 Explain how PRINCE2 Agile is used in a project context and explain the difference between projects and business as usual (BAU).

2.2 Recall which agile ways of working are suitable for use with PRINCE2 Agile

1. Kanban
2. Lean startup
3. Scrum

2.3 Describe the need to ‘blend and weave’ PRINCE2 with agile at all levels of a project (project direction, project management and product delivery) including the eight guidance points

2.4 Describe the roles, responsibilities and competencies of the PRINCE2 Agile delivery team

1. Customer subject matter expert
2. Customer representative
3. Supplier subject matter expert
4. Supplier representative

3. Understand how PRINCE2 principles, themes, processes and management products are tailored and/or applied in an agile context

3.1 Explain how the PRINCE2 principles will be applied in an agile context

1. Continued business justification
2. Learn from experience
3. Defined roles and responsibilities
4. Manage by stages
5. Manage by exception
6. Focus on products
7. Tailor to suit the project environment

3.2 Explain the PRINCE2 Agile behaviors

1. Transparency
2. Collaboration
3. Rich communication
4. Self-organization
5. Exploration

3.3 Explain the PRINCE2 Agile guidance for each theme

1. Business case
2. Organization
3. Quality
4. Plans
5. Risk
6. Change
7. Progress

3.4 Explain the PRINCE2 Agile guidance for each process

1. Starting up a project
2. Initiating a project
3. Directing a project
4. Controlling a stage
5. Managing product delivery
6. Managing a stage boundary
7. Closing a project

3.5 Explain the PRINCE2 Agile guidance for tailoring the following PRINCE2 management products

1. Business case
2. Checkpoint report
3. Highlight reports
4. Project brief
5. Project initiation documentation
6. Project product description
7. Work package

3.6 Explain what to fix and what to flex, including setting tolerances and the five targets

1. Fix and flex tolerances
2. Be on time and hitting deadlines
3. Protect the level of quality
4. Embrace change
5. Keep teams stable
6. Accept that the customer doesn’t need everything

4. Understand the agile ways of working, key terms and techniques

4.1 Recall the definition of the following agile terms

1. Backlog (sprint, release & product)
2. Benefit (value)
3. Epic
4. Information radiator
5. Spike
6. Stand up meeting
7. Timebox (sprint, release)
8. Velocity
9. Waterfall methodology

4.2 Explain key Agile concepts and techniques

1. Scrum
2. Lean Startup (incl. MVP)
3. Retrospectives
4. User stories (incl. Definition of ‘ready’ and ‘done’)
5. Workshops
6. Burn charts
7. Agile Estimation (points and T-Shirt sizing)
8. Working Agreements

5. Understand the focus areas in an agile context

5.1 Explain the PRINCE2 Agile focus areas

1. Agilometer
2. Requirements
3. Rich communication
4. Frequent releases