PRINCE2 Agile Practitioner for PMOs Training Course

Course overview

PMOs are often asked to provide reliable governance, portfolio visibility and assurance while delivery teams work in Scrum, Kanban or hybrid environments. Traditional stage plans and status reports can obscure iterative progress, while unconstrained Agile delivery can leave sponsors without clear controls, tolerances or decision points. This course addresses the practical challenge of applying PRINCE2 Agile controls without imposing unnecessary bureaucracy on teams that need to release value frequently.

Participants learn how to tailor the PRINCE2 Agile method for PMO-led governance, from defining a project’s Agilometer profile and selecting an appropriate delivery approach to setting management stages, tolerances and reporting cadences. They work with the PRINCE2 themes of business case, organization, quality, plans, risk, change and progress alongside Agile practices including product backlogs, timeboxes, Kanban flow, sprint reviews, release planning and empirical forecasting. Particular attention is given to translating team-level delivery evidence into portfolio-ready dashboards, exception reports and assurance decisions.

The five-day programme combines instructor-led method explanation with a running case study of a PMO supporting several Agile project teams. Participants tailor controls, build a governance map, define reporting measures, prepare an Agile-compatible stage plan and respond to delivery exceptions. They leave with a practical PRINCE2 Agile PMO implementation pack: a tailoring decision log, governance and escalation model, reporting template set, assurance checklist and 90-day application plan for their own environment.

The course is suited to experienced project, programme and PMO professionals who need to govern Agile delivery credibly rather than simply adopt Agile terminology. It is equally valuable for managers funding transformation work who need consistent controls across mixed delivery models.

Course objectives

By the end of this course, participants will be able to:

• Tailor PRINCE2 Agile principles, themes and processes to a PMO governance environment
• Assess project context using the Agilometer and document an appropriate delivery and control profile
• Design management stages, tolerances and exception routes for iterative product delivery
• Create an Agile-compatible business case linking releases, benefits, costs and investment decisions
• Translate product backlog, velocity and flow data into PMO status reports and portfolio dashboards
• Apply Scrum, Kanban and Lean Startup concepts within PRINCE2 Agile control boundaries
• Develop risk, issue, change and assurance controls that support rapid team-level decision making
• Produce a PRINCE2 Agile PMO implementation pack with templates, governance roles and adoption actions

Benefits of attending

Target competencies

Who should attend

• PMO Managers — who need consistent governance across Scrum, Kanban and hybrid projects
• Project Managers — who must retain PRINCE2 controls while leading iterative delivery
• Programme Managers — who coordinate dependencies, tranches and benefits across Agile initiatives
• Project Support Officers — who create reports, RAID records and assurance evidence for delivery teams
• Portfolio Managers — who need comparable progress and investment data from mixed-method projects
• Agile Delivery Leads — who need to work effectively with PMO controls and senior governance forums

Requirements and prerequisites

Participants should have practical experience of project or PMO work and be comfortable with core PRINCE2 concepts such as business case, stages, roles, risks, issues, tolerances and reporting. Familiarity with at least one Agile delivery approach, ideally Scrum events and product backlogs or Kanban boards, is expected. Attendees should be able to interpret a project plan, RAID log and status report. Prior PRINCE2 Agile certification is not required, and no coding, specialist analytics or enterprise PPM-system administration experience is needed. A laptop with spreadsheet and document-editing software is useful for workshop activities.

Training methodology

An experienced instructor leads short method briefings, then participants apply each concept to a continuing PMO case involving multiple Scrum and Kanban teams. Workshops use governance maps, Agilometer assessments, product backlog extracts, cumulative-flow data, stage plans, RAID records and exception scenarios. Small groups compare tailoring choices and defend them in simulated project-board discussions. Daily outputs are reviewed against PRINCE2 Agile principles, and the final session converts case-study work into a 90-day application plan, supported by reusable templates for participants’ own PMO.

Course outline

Day 1: PRINCE2 Agile foundations for PMO governance

• PRINCE2 Agile purpose, principles and method structure
• PMO governance challenges in Scrum, Kanban and hybrid delivery
• PRINCE2 principles interpreted for iterative projects
• The six PRINCE2 aspects and the five Agile targets
• Roles, accountabilities and delegation across project board, PMO and delivery team
• The Agilometer assessment and tailoring decision criteria
• Governance layers from team delivery to portfolio oversight

Workshop: Participants assess a case-study project with the Agilometer and produce a documented tailoring profile for its PMO.

Day 2: Planning, business cases and release control

• Agile business cases and incremental investment decisions
• Product-based planning alongside product backlogs
• Management stages, releases, increments and timeboxes
• MoSCoW prioritisation and scope tolerance
• Release planning using velocity, throughput and forecast ranges
• Benefits management across staged and iterative delivery
• Defining workable tolerances for time, cost, scope, risk, quality and benefits

Workshop: Participants create a stage and release plan that links backlog priorities, tolerances, benefits and funding decisions.

Day 3: Control, reporting and assurance for Agile projects

• Progress theme controls in PRINCE2 Agile
• Checkpoint reports, highlight reports and Agile information radiators
• Burn charts, cumulative-flow diagrams and velocity trends
• Exception assessment and exception-plan preparation
• Quality planning, acceptance criteria and definition of done
• Independent assurance without disrupting delivery teams
• PMO dashboard design for portfolio-level comparability

Workshop: Participants convert team-level Scrum and Kanban data into a project-board highlight report and an exception recommendation.

Day 4: Risk, change and stakeholder decisions

• Risk theme application in uncertain and emergent work
• RAID management integrated with Agile ceremonies
• Issue and change control through backlog refinement
• Configuration management for evolving products and releases
• Stakeholder engagement through reviews, demos and feedback loops
• Decision rights, escalation paths and project-board interventions
• Managing dependencies across Agile teams, suppliers and programmes

Workshop: Participants run a governance workshop to resolve a cross-team dependency, scope change and risk escalation using defined decision rights.

Day 5: PMO implementation and Practitioner-style application

• Designing a PRINCE2 Agile PMO operating model
• Template tailoring for plans, reports, RAID logs and assurance reviews
• Selecting governance metrics that support action rather than reporting volume
• Adopting controls across predictive, hybrid and Agile project portfolios
• Common anti-patterns in Agile PMO implementation
• Readiness assessment and stakeholder adoption planning
• Ninety-day implementation roadmap and success measures

Workshop: Participants assemble and present a PRINCE2 Agile PMO implementation pack with governance templates, ownership actions and a 90-day roadmap.

Tools & standards covered

PRINCE2 Agile guidance, The Scrum Guide, The Kanban Guide, Microsoft Project

A typical training day

Live online deliveries follow the same structure in the East Africa Time zone, with shorter screen blocks and longer breaks.

What the fee includes

How you can take this course

Certification

Participants who complete the full five days receive the Skillset Development Certificate of Completion, stating the course title, course code, dates and delivery format — suitable for professional-development records and employer reimbursement.

Frequently asked questions