1 Understand the basic concepts of common agile ways of working
1.1 Explain the differences between projects and BAU (Business as usual)
1.2 Describe agile and its common approaches, how and why agile approaches have developed and where they are used
1.3 Describe the history of agile, it’s contrast to the waterfall way of working and how the Agile Manifesto fits in
1.4 Describe the different levels of agile maturity and well-known agile frameworks
1.5 Describe behaviours, concepts and techniques that characterize agile
1.6 Define the PRINCE2 Agile view of ‘agile’
1.7 Describe Kanban, the Kanban method and its six general practices, including the use of Cumulative Flow Diagrams (CFDs)
1.8 Describe the core concepts of Lean Start-up
1.9 Describe the use of workshops
1.10 Describe how to transition to agile
1.11 Define Scrum theory and explain the nature of the Scrum team, Scrum events, Scrum artefacts and Sprints

2 Understand the purpose and context for combining PRINCE2 and the agile way of working
2.1 Describe the complementary strengths of PRINCE2 and the agile way of working
2.2 Define who can benefit from using PRINCE2 Agile and in what contexts/situations
2.3 Define the make-up of PRINCE2 Agile (frameworks, behaviours, concepts, techniques, focus areas)
2.4 Explain the eight ‘guidance points’
2.5 Explain how PRINCE2 controls and governance can enable agile to be used in many environments
2.6 Describe what a typical PRINCE2 ‘project journey’ looks like in an agile context

3 Be able to apply and evaluate the focus areas to a project in an agile context
3.1 Explain the purpose and use of the Agilometer throughout a project
3.2 Describe the six sliders used on the Agilometer, explain their significance and how to improve them
3.3 Describe in detail requirements terminology, decomposition and prioritization, including MoSCoW and Ordering
3.4 Explain how requirements prioritization is used
3.5 Explain the rich communication focus area, its importance and its key techniques
3.6 Explain how to manage frequent releases and the benefits of ‘failing fast’

4 Be able to fix and flex the six aspects of a project in an agile context
4.1 Describe how to use the ‘hexagon’ in relation to the six aspects of project performance
4.2 Explain the use of tolerances in terms of what to ‘fix’ and what to ‘flex’ in relation to the six aspects of project performance
4.3 Describe in detail each of the five targets that underpin the use of the hexagon
4.4 Explain why the ‘fix and flex’ approach is good for the customer

5 Be able to apply or tailor the PRINCE2 principles, themes, processes and management products to a project in an agile context
5.1 Describe in detail the five PRINCE2 Agile behaviours (Transparency, Collaboration, Rich Communication, Self-Organization, Exploration)
5.2 Explain that agile needs to be incorporated in all seven PRINCE2 processes and all seven themes but that the amount appropriate to each will vary depending on the project context
5.3 Describe the two common Organization roles of Scrum master and Product owner
5.4 Explain how to adjust roles, including the use of specialist roles, and the options for team organization in a project
5.5 Define the make-up of a typical delivery team
5.6 Describe servant leadership, its use and importance
5.7 Describe how to define Working Agreements
5.8 Describe quality setting techniques including ‘definition of done’ and the use of acceptance criteria
5.9 Describe quality testing, quality checking and management techniques
5.10 Describe approaches to planning and typical planning techniques
5.11 Describe approaches to risk and how agile concepts mitigate many typical risks
5.12 Describe how blending PRINCE2 with agile approaches controls, responds to, and minimizes the impact of change, including risk management and configuration management
5.13 Describe how empowered self-organizing teams handle change dynamically within set tolerances
5.14 Describe common feedback loops and their importance
5.15 Describe progress monitoring techniques including use of ‘work in progress’ boards, burn charts, information radiators
5.16 Describe in detail agile techniques that may apply to each PRINCE2 process including Cynefin
5.17 Describe how to flex the ‘Direct a Project’ stage and the benefits of collaborative working
5.18 Describe how to ‘manage by exception’ with emphasis on empowerment, quantity of deliverables, rich information flows and value of deliverables
5.19 Explain why PRINCE2 ‘stages’ may not be required, including the use of timeboxes and Scrum of scrums
5.20 Describe typical output mechanisms when ‘Controlling a Stage’ and ‘Managing a Stage Boundary’
5.21 Describe the use of retrospectives and how to make them effective
5.22 Describe approaches to managing product delivery including Scrum and Kanban
5.23 Explain how to define Work Packages, Product Descriptions, quality criteria and tolerances
5.24 Give guidance on behaviours, risk and the frequency of releases
5.25 Explain how to manage stage boundaries and the similarities between a stage and a release
5.26 Explain how to assess quantity, quality and benefits of stage deliverables
5.27 Explain how to effectively close a project, including evaluation of the use of agile
5.28 Describe how to tailor PRINCE2 products, including Work Packages, Highlight Reports and Checkpoint Reports
5.29 Describe in detail agile techniques that may apply to each PRINCE2 theme including requirements, defining value and user stories
5.30 Describe guidance on the use of contracts
5.31 Describe PRINCE2 Agile delivery roles
5.32 Explain how to use the Health Check
5.33 Describe the fundamental values and principles of agile
5.34 Outline tips for the PRINCE2 Agile project manager