PRINCE2® Agile Practitioner Certificate in Agile Project Management Training in Sweden

Course materials are provided however you will also need a copy of the official publication PRINCE2 AGILE which is not included in this practitioner course.

If you do not have a copy of the PRINCE 2 AGILE then follow the instructions below to purchase one.

Please log in to your Peoplecert account , visit the overview section and click on the “buy E book” option.

PRINCE2 Agile can be taken if you hold any of the following certifications:

• PRINCE2 Foundation (any version)
• PRINCE2 Practitioner (any version)
• PRINCE2 Agile Foundation
• A current Project Management Professional® (PMP)
• Certified Associate in Project Management® (CAPM)
• IMPA Levels A,B,C and D® (Certified Projects Director)

Please note, although any of the above certifications are permissible as pre-requisite, QA strongly recommends that delegates hold a recent PRINCE2 Practitioner certificate before attending the course.

Essential prerequisites

Acceptable forms of prerequisite confirmation are as follows:

For PMI or IPMA certification holders:

• A copy of your examination certificate

For PRINCE2 Foundation and Practitioner Certificate holders:

• A copy of the candidates examination certificate
• A confirmed entry in the AXELOS Successful Candidate Register (full SCR number as on your certificate)

Pre-course reading

You will be provided with QA's pre-course reading prior to attending the course to help them prepare for the course. The pre-course reading is expected to take approximately 10 hours to complete. Success on the course will be enhanced by close attention to the pre-reading material.

Reasonable adjustments policy

The exam provider allows additional time for candidates who have a disability or whose native language differs to that of the examination paper. Ful details and how to apply can be found here www.qa.com/axelosexams. At least two weeks' notice will be required for processing this request. Learners failing to advise QA and provide evidence when requested, may not be allowed the additional support offered via the policy. QA Exam Administration can be contacted by email exam.admin@qa.com or by phone +44(0)1793 696162.

• Understand the basic concepts of common agile ways of working.
• Understand the purpose and context for combing PRINCE2 and the agile way of working.
• Be able to apply and evaluate the focus areas to a project in an agile context.
• Be able to fix and flex the six aspects of a project in an agile context.
• Be able to apply or tailor the PRINCE2 principles, themes, processes and management products to a project in an agile context.
• To learn through the use of theory and practical exercises.
• To prepare delegates for the PRINCE2 Agile Practitioner exam.

The PRINCE2 Agile course uses a combination of theory, discussion and practical exercises to ensure delegates feel confident in the application of the concepts. Additional evening work will be required in the form of consolidation reading and mock examination questions. The evening work is an integral part of the course and delegates should expect to spend approximately 2.5 hours on these activities.

The course will cover the following learning outcomes:

Understand the basic concepts of common agile ways of working

• Explain the differences between projects and BAU (business as usual).
• Describe agile and its common approaches, how and why agile approaches have developed and where they are used.
• Describe the history of agile, its contrast to the waterfall way of working and how the agile manifesto fits in.
• Describe the different levels of agile maturity and well-known agile frameworks.
• Describe behaviours, concepts and techniques that characterise agile.
• Define the PRINCE2 Agile view of 'agile'.
• Describe Kanban, the Kanban method and its six general practices, including the use of Cumulative Flow Diagram (CFDs).
• Describe the core concepts of Lean start-up.
• Describe the use of workshops.
• Describe how to transition to agile.
• Define Scrum theory and explain the nature of the Scrum team, Scrum events, Scrum artefacts and Sprints.

Understand the purpose and context for combining PRINCE2 and the agile ways of working

• Describe the complementary strengths of PRINCE2 and the agile ways of working.
• Define who can benefit from using PRINCE2 Agile and in what contexts/situation.
• Define the make-up of PRINCE2 Agile (frameworks, behaviours, concepts, techniques, focus areas).
• Explain the eight 'guidance points'.
• Explain how PRINCE2 controls and governance can enable agile to be used in many environments.
• Describe what a typical PRINCE2 'project journey' looks like in an agile context.
• Be able to apply and evaluate the focus areas to a project in an agile context.

Explain the purpose and use of the Agilometer throughout a project

• Describe the six sliders used on the Agilometer, explain their significance and how to improve them
• Describe in detail requirements terminology, decomposition and prioritisation, including MoSCoW and Ordering
• Explain how requirements prioritisation is used
• Explain the rich communication focus area, its importance and its key techniques
• Explain how to manage frequent releases and the benefits of 'failing fast'

Be able to fix and flex the six aspects of a project in an agile context

• Describe how to use the 'hexagon' in relation to the six aspects of project performance
• Explain the use of tolerances in terms of what to 'fix' and what to 'flex' in relation to the six aspects of project performance
• Describe in detail each of the five targets that underpin the use of the hexagon
• Explain why the 'fix and flex' approach is good for the customer

Be able to tailor the PRINCE2 principles, themes, processes and management products to a project in an agile context

• Describe in detail the 5 PRINCE2 Agile behaviours (Transparency, Collaboration, Rich Communication, Self-Organisation, Exploration).
• 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.
• Describe the two common Organisation roles of scrum master and product owner.
• Explain how to adjust roles, including the use of specialist roles, and the options for team organisation in a project.
• Describe the make-up of a typical delivery team.
• Describe servant leadership, its use and importance.
• Describe how to define Working Agreements.
• Describe quality setting techniques including 'definition of done' and the use of acceptance criteria.
• Describe quality testing, quality checking and management techniques.
• Describe approaches to planning and typical planning techniques.
• Describe approaches to risk and how agile concepts mitigate many typical risks.
• Describe how blending PRINCE2 with agile approaches controls, responds to, and minimises the impact of change, including risk management and configuration management.
• Describe how empowered self-organising teams handle change dynamically within set tolerances.
• Describe common feedback loops and their importance.
• Describe progress monitoring techniques including use of Work in Progress boards, burn charts, information radiators.
• Describe in detail agile techniques that may apply to each PRINCE2 process including Cynefin.
• Describe how to flex the 'Direct a Project' stage and the benefits of collaborative working.
• Describe how to 'manage by exception' with emphasis on empowerment, quantity of deliverables, rich information flows and value of deliverables.
• Explain why PRINCE2 'stages' may not be required, including use of timeboxes and Scrum of scrums.
• Describe typical output mechanisms when 'Controlling a Stage' and 'Managing a Stage Boundary.
• Describe the use of retrospectives and how to make them effective.
• Describe approaches to 'Managing Product Delivery' including Scrum and Kanban.
• Explain how to define Work Packages, Product Descriptions, quality criteria and tolerances.
• Give guidance on behaviours, risks and the frequency of releases.
• Explain how to manage Stage Boundaries and the similarities between a stage and a release.
• Explain how to assess quantity, quality and benefits of stage deliverables.
• Explain how to effectively close a project, including evaluation of the use of agile.
• Describe how to tailor PRINCE2 products, including Work Packages, Highlight Reports and Checkpoint Reports.
• Describe in detail agile techniques that may apply to each PRINCE2 theme including requirements, defining value and user stories.
• Describe guidance on the use of contracts.
• Describe PRINCE2 Agile delivery roles.
• Explain how to use the Health Check.
• Describe the fundamental values and principles of agile.
• Outline tips for the PRINCE2 Agile project manager.

PRINCE2 Agile Examination: key information

PeopleCert exams take place remotely via PeopleCert Online Proctoring, and the afternoon of the last day of your course will continue with your learning until approximately 4.00pm. When booking your exam please ensure that it is for a time after the course has concluded and at a time convenient for you. You will be required to download and install ExamShield and conduct a compatibility test prior to sitting the exam.

• 2.5 hour exam
• Open book (PRINCE2 Agile book only)
• Objective testing exam
• Taken on the afternoon of the third day
• 50 questions totalling 50 marks (1 mark per question)
• Pass mark is 60% (30 correct answers).

Throughout the PRINCE2 Agile course, delegates will be exposed to numerous examples of examination questions. We will undertake a number of exercises and 'question-and-answer' sessions that will help to consolidate the learning, thereby ensuring that delegates are more than adequately prepared for the final examination.

PRINCE2 Agile® is a [registered] trade mark of AXELOS Limited, used under permission of AXELOS Limited. All rights reserved.

The Swirl logo™ is a trade mark of AXELOS Limited, used under permission of AXELOS Limited. All rights reserved.