PRINCE2 Agile® Practitioner Exam

PRINCE2 Agile® Practitioner Exam

PRINCE2 Agile® Practitioner links agile concepts with the most popular approach to project management. The certification has been built in response to user demand. Moreover, the PRINCE2 Agile Practitioner certification teaches you to blend structure, governance and control with agile methods, techniques and approaches.

Exam Prerequisites

You can take the PRINCE2 Agile Practitioner certificate if you hold any of the following certifications:

• PRINCE2® Foundation (or higher)
• PRINCE2 Agile® Foundation
• Project Management Qualification® (PMQ)*
• Certified Associate in Project Management® (CAPM)*
• IPMA Levels A,B,C and D® (Certified Projects Director).

Exam Course Outline

The PRINCE2 Agile® Practitioner Exam covers the following topics - 

MODULE 1

• Explain the differences between projects and BAU (Business as usual) (Figure 1.1, Section 1.2)
• Describe agile and its common approaches, how and why agile approaches have developed and where they are used (Figure 2.3, Section 2.1)
• Describe the history of agile, it’s contrast to the waterfall way of working and how the Agile Manifesto fitsin (Figure 2.1)
• Describe the different levels of agile maturity and well-known agile frameworks (Section 2.2.1, Table 2.1)
• Describe behaviours, concepts and techniques that characterize agile (Section 2.2.2, Table 2.2)
• Define the PRINCE2 Agile view of ‘agile’(Section 2.2)
• Describe Kanban, the Kanban method and its six general practices, including the use of Cumulative Flow
• Diagrams (CFDs) (Figure 20.2, Figure 20.4, Section 20.4.1)
• Describe the core concepts of Lean Start-up (Section 20.4.2)
• Describe the use of workshops (Section 26.4.1)
• Describe how to transition to agile (Appendix F)
• Define Scrum theory and explain the nature of the Scrum team, Scrum events, Scrum artefacts and Sprints (Appendix H)

MODULE 2

• Describe the complementary strengths of PRINCE2 and the agile way of working (Section 3.1, Figure 3.1)
• Define who can benefit from using PRINCE2 Agile and in what contexts/situations (Section 3.1, Section 3.2, Section 3.3)
• Define the make-up of PRINCE2 Agile (frameworks, behaviours, concepts, techniques, focus areas) (Section 3.5, Figure 3.2)
• Explain the eight ‘guidance points’ (Section 3.6)
• Explain how PRINCE2 controls and governance can enable agile to be used in many environments (Section 3.7)
• Describe what a typical PRINCE2 ‘project journey’ looks like in an agile context (Figure 4.1, Section 4.1)

MODULE 3

• Explain the purpose and use of the Agilometer throughout a project (Section 24.1, Section 24.2, Section 24.3)
• Describe the six sliders used on the Agilometer, explain their significance and how to improve them (Figure 24.1, Section 24.4)
• Describe in detail requirements terminology, decomposition and prioritization, including MoSCoW and Ordering (Figure 25.2, Section 25.5, Table 25.3)
• Explain how requirements prioritization is used (Figure 25.2, Section 25.5) 
• Explain the rich communication focus area, its importance and its key techniques (Section 26.1, Section 26.2, Section 26.3)
• Explain how to manage frequent releases and the benefits of ‘failing fast’ (Section 27.1, Section 27.2)

MODULE 4

• Describe how to use the ‘hexagon’ in relation to the six aspects of project performance (Figure 6.1, Section 6.1)
• Explain the use of tolerances in terms of what to ‘fix’ and what to ‘flex’ in relation to the six aspects of project performance (Figure 6.1, Section 6.1, Table 6.1)
• Describe in detail each of the five targets that underpin the use of the hexagon (Section 6.4, Section 6.5, Table 6.2)
• Explain why the ‘fix and flex’ approach is good for the customer (Section 6.5)

MODULE 5

• Describe in detail the five PRINCE2 Agile behaviours (Transparency, Collaboration, Rich Communication, Self-Organization, Exploration) (Section 7.4, Figure 7.1)
• 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 (Section 8.1, Section 8.2, Figure 16.2, Figure 16.3, Figure 16.4, Section 16)
• Describe the two common Organization roles of Scrum master and Product owner (Section 10.2.1)
• Explain how to adjust roles, including the use of specialist roles, and the options for team organization in a project (Section 10.3, Section 10.4, Section 10.5.2, Table 10.1, Figure 10.4, Figure 10.5)
• Define the make-up of a typical delivery team (Section 10.4.2, Section 10.4.3)
• Describe servant leadership, its use and importance (Section 10.5.1)
• Describe how to define Working Agreements (Section 10.5.3)
• Describe quality setting techniques including ‘definition of done’ and the use of acceptance criteria (Section 11.2)
• Describe quality testing, quality checking and management techniques (Section 11.2, Section 11.3, Section 20.3)
• Describe approaches to planning and typical planning techniques (Section 12.3)
• Describe approaches to risk and how agile concepts mitigate many typical risks (Section 13.1, Section 13.2)
• Describe how blending PRINCE2 with agile approaches controls, responds to, and minimizes the impact of change, including risk management and configuration management (Section 14.2, Section 14.3)
• Describe how empowered self-organizing teams handle change dynamically within set tolerances (Section 10.2, Section 14.3.3)
• Describe common feedback loops and their importance (Section 14.4.1)
• Describe progress monitoring techniques including use of ‘work in progress’ boards, burn charts, information radiators (Figure 15.1, Section 15.2, Section 15.3, Section 15.4)
• Describe in detail agile techniques that may apply to each PRINCE2 process including Cynefin (Figure 17.3, Section 17.3, Section 17.4)
• Describe how to flex the ‘Direct a Project’ stage and the benefits of collaborative working (Section 18.2, Section 18.3)
• Describe how to ‘manage by exception’ with emphasis on empowerment, quantity of deliverables, rich information flows and value of deliverables (Section 18.3)
• Explain why PRINCE2 ‘stages’ may not be required, including the use of timeboxes and Scrum of scrums (Section 19.2)
• Describe typical output mechanisms when ‘Controlling a Stage’ and ‘Managing a Stage Boundary’ (Section 19.2, Section 19.3, Section 21.3, Section 21.4)
• Describe the use of retrospectives and how to make them effective (Section 19.4.1)
• Describe approaches to managing product delivery including Scrum and Kanban (Section 20.2)
• Explain how to define Work Packages, Product Descriptions, quality criteria and tolerances (Section 20.3)
• Give guidance on behaviours, risk and the frequency of releases (Section 20.3)
• Explain how to manage stage boundaries and the similarities between a stage and a release (Section 21.2)
• Explain how to assess quantity, quality and benefits of stage deliverables (Section 21.3)
• Explain how to effectively close a project, including evaluation of the use of agile (Section 22.2, Section 22.3, Section 22.4)
• Describe how to tailor PRINCE2 products, including Work Packages, Highlight Reports and Checkpoint Reports (Chapter 23)
• Describe in detail agile techniques that may apply to each PRINCE2 theme including requirements, defining value and user stories (Figure 25.3, Section 9.4.1, Section 25.1, Section 25.6.1)
• Describe guidance on the use of contracts (Section 28.3)
• Describe PRINCE2 Agile delivery roles (Appendix A, Appendix B)
• Explain how to use the Health Check (Appendix C)
• Describe the fundamental values and principles of agile (Appendix E)
• Outline tips for the PRINCE2 Agile project manager (Appendix G)

Get ready to practice and pass the PRINCE2 Agile® Practitioner Exam with latest and updated practice test and study guide. Try free practice test Now!