PRINCE2 7 Practitioner Training Course

Duration 10 days 20 modules · 65 contact hours
Level Intermediate Certificate on completion
Who attends Project Managers, Project Coordinators and others
Fee from USD 2,200 KSh 190,000 for Kenyan organisations
Where 52 cities + online See dates by city
Next start 9 Nov 2026 Course code SD-PM-065

Before you join: Participants should have practical exposure to projects, such as coordinating work packages, contributing to plans, reporting progress or supporting change delivery.

Dates & prices

Two start dates a month in every city, and live online on weekdays or weekends. Fees are per participant; classroom fees include tuition, materials, lunch and refreshments, and the certificate.

Suggest a date or city

Showing the next six months. Later dates, other cities and private deliveries for your team are available on request.

Course overview

Projects fail when teams begin delivery without an agreed business case, clear product definitions, workable controls or decision rights. Senior users may receive outputs that do not meet operational needs, project managers may report progress without reliable forecasts, and boards may approve changes without understanding effects on time, cost, risk and benefits. PRINCE2 7 provides a structured method for directing, managing and controlling projects while allowing proportionate tailoring.

This course develops the ability to apply PRINCE2 7 to realistic projects from initiation through closure. Participants learn the seven principles, people focus, practices and processes; then use them to create a business case, project brief, project initiation documentation, product descriptions, plans, registers, reports and closure records. The course addresses project roles, tolerances, stages, exceptions, quality control, risk, issues, change, sustainability and benefits management. Participants also learn how to tailor the method for project scale, delivery approach, organisational governance and supplier arrangements.

Teaching combines focused instructor briefings with case-based planning, facilitated group work, decision simulations and individual application planning. Participants work with a sustained project scenario during the first week, then deepen and review the same project controls during the second week. They leave with a completed PRINCE2-aligned project management pack that can be adapted for an active workplace project, plus a certificate of completion.

The course suits project managers, project coordinators, workstream leaders, project support staff, business change professionals and managers who contribute to project boards. It is particularly useful where organisations need consistent governance without imposing unnecessary documentation on smaller or less complex initiatives.

What you will be able to do

  • Apply the seven PRINCE2 7 principles to project decisions and governance arrangements
  • Develop a project brief, business case and project initiation documentation
  • Define products using product-based planning and measurable quality criteria
  • Construct stage plans, team plans and tolerances using PRINCE2 controls
  • Assess risks, issues and change requests through PRINCE2 management products
  • Tailor PRINCE2 7 practices and processes to project scale and context
  • Prepare management reports, exception reports and end-stage assessments
  • Present a complete PRINCE2-aligned project management pack for board review

Benefits of attending

For you

  • Produce PRINCE2 management products with greater confidence and consistency
  • Run stage boundaries and exception decisions using defined governance controls
  • Explain project status, forecast and risk exposure clearly to senior stakeholders
  • Adapt PRINCE2 documentation without losing essential project control
  • Build a reusable project pack for immediate workplace application

For your organisation

  • Improves consistency of project business cases, plans and control records
  • Strengthens board decisions through defined tolerances and exception reporting
  • Reduces unclear scope through product descriptions and quality criteria
  • Creates earlier visibility of risks, issues, changes and forecast variances
  • Supports proportionate governance across predictive, iterative and supplier-led projects

Course modules

20 modules over 10 days

Participants can position PRINCE2 7 within a project environment and explain its method structure.

  • PRINCE2 7 principles, practices, processes and management products explained clearly
  • Projects, programmes, operations and portfolios distinguished through governance purpose
  • Organisational context assessed before selecting proportionate project management controls
  • Project mandate interpreted as the trigger for formal project initiation
  • Delivery approaches compared: linear, iterative, incremental and hybrid methods
  • Management by exception linked to delegated authority and tolerances

Participants can apply PRINCE2 principles and assign accountable project roles.

  • Continued business justification tested throughout the project lifecycle
  • Learn from experience through lessons logs and review points
  • Defined roles and responsibilities mapped using PRINCE2 role descriptions
  • Manage by stages through planned decision points and approvals
  • People capability, culture and behaviour considered in project management
  • Project Board interests represented by executive, user and supplier roles

Participants can prepare the information needed to decide whether a project should initiate.

  • Project mandate reviewed for strategic purpose, authority and constraints
  • Executive appointed with accountability for business case ownership
  • Previous lessons examined before defining the proposed project approach
  • Project brief drafted with objectives, scope, exclusions and interfaces
  • Outline business case estimates benefits, costs, timescales and major risks
  • Initiation stage plan prepared for controlled project definition work

Participants can develop and maintain a PRINCE2 business case for informed decisions.

  • Reasons, options and expected benefits structured within the business case
  • Investment appraisal compares do-nothing, do-minimum and preferred options
  • Benefit dis-benefit and cost profiles forecast across the project lifecycle
  • Risk-adjusted viability reviewed at stage boundaries and exception points
  • Benefits management approach assigns measures, owners and review dates
  • Business case tolerances define escalation thresholds for continued justification

Participants can design project governance, delegation and communication responsibilities.

  • Project Board authority defined through directing and decision-making responsibilities
  • Senior User requirements represented through benefits and acceptance interests
  • Senior Supplier commitments aligned with technical feasibility and delivery capacity
  • Project Manager authority set through delegated tolerances and controls
  • Team Manager responsibilities defined for work package delivery and reporting
  • Stakeholder engagement approach identifies influence, interests and communication needs

Participants can define project products and derive plans from required outputs.

  • Product breakdown structure identifies required products and component relationships
  • Product flow diagram sequences creation, review and approval dependencies
  • Product descriptions specify purpose, composition, quality criteria and tolerances
  • Quality methods selected for inspection, testing, review or demonstration
  • Acceptance criteria translated into measurable requirements for final project products
  • Work packages derived from agreed products, dependencies and delivery responsibilities

Participants can prepare PRINCE2 plans with estimates, dependencies and tolerances.

  • Project, stage, team and exception plans distinguished by control purpose
  • Planning horizon matched to management level and decision timing
  • Estimating techniques include analogous, parametric, bottom-up and three-point methods
  • Dependencies mapped using precedence relationships and milestone scheduling
  • Resource requirements profiled against planned products and delivery activities
  • Time and cost tolerances recorded for management by exception

Participants can plan quality controls and record evidence of product acceptance.

  • Quality planning assigns methods, responsibilities, timing and acceptance evidence
  • Quality register records planned and completed quality control activities
  • Quality review technique applies preparation, meeting and follow-up responsibilities
  • Product descriptions establish quality specifications before production begins
  • Acceptance methods distinguish formal approval from internal quality checks
  • Configuration item records preserve approved product versions and status

Participants can identify, assess and control project threats and opportunities.

  • Risk management approach defines scales, categories, responses and reporting
  • Cause-event-effect statements describe risks with precision and ownership
  • Probability and impact assessed using agreed risk exposure scales
  • Risk budget and time allowance considered within project contingency arrangements
  • Threat responses include avoid, reduce, transfer, share, accept and escalate
  • Opportunity responses include exploit, enhance, share, accept and escalate

Participants can control issues, requests for change and product configurations.

  • Issue register records requests for change, off-specifications and concerns
  • Issue report analyses impact on business case, plans and products
  • Configuration management approach controls product identification, versions and status
  • Change authority assigned according to delegated scope and tolerance limits
  • Impact analysis examines time, cost, risk, quality, benefits and sustainability
  • Approved changes incorporated into baselined plans and product descriptions

Participants can monitor progress and escalate forecast exceptions appropriately.

  • Progress management approach sets reporting frequency, measures and responsibilities
  • Checkpoint reports provide Team Manager progress information to project management
  • Highlight reports summarise stage status for Project Board attention
  • Actual progress compared against plan forecasts, tolerances and product status
  • Exception reports explain forecast deviations and recommend corrective options
  • Management stages reset control baselines after Project Board approval

Participants can support project board decisions throughout the PRINCE2 lifecycle.

  • Authorise initiation after reviewing project brief and initiation stage plan
  • Authorise project after assessing project initiation documentation and delivery confidence
  • Authorise a stage or exception plan using updated forecasts
  • Give ad hoc direction when tolerances, risks or external conditions change
  • Authorise project closure after confirming acceptance and follow-on actions
  • Project Board decision records capture rationale, conditions and delegated actions

Participants can assemble project initiation documentation that establishes a controlled baseline.

  • Project initiation documentation integrates strategies, plans, controls and governance
  • Delivery approach documented with supplier, procurement and integration assumptions
  • Management approaches cover benefits, change, quality, risk and communication
  • Project plan establishes scope, schedule, costs, risks and key controls
  • Baseline management products approved before major delivery work begins
  • Initiation review tests viability, readiness and governance before authorisation

Participants can manage day-to-day stage control within delegated tolerances.

  • Work packages authorised with products, constraints, tolerances and reporting requirements
  • Checkpoint information reviewed against expected progress and emerging risks
  • Issues and risks captured, assessed and escalated through agreed controls
  • Corrective actions selected before forecast deviations exceed stage tolerances
  • Configuration status accounts confirm approved product versions and completion
  • Highlight reports prepared with achievements, forecasts, risks and decisions required

Participants can agree, monitor and accept work packages from delivery teams.

  • Work package acceptance confirms authority, resources, products and constraints
  • Team plans detail activities, estimates, dependencies and delivery responsibilities
  • Specialist products created against approved descriptions and quality methods
  • Checkpoint reports communicate completed work, forecasts, issues and risks
  • Completed work packages returned with quality records and configuration updates
  • Product acceptance verifies required criteria before project management sign-off

Participants can prepare end-stage information for informed continuation decisions.

  • End stage reports compare performance against approved stage plans
  • Next stage plans reflect updated estimates, risks and resource availability
  • Business case updated with actual costs, revised forecasts and benefits
  • Lessons report captures insights for immediate action and future projects
  • Exception plan replaces a forecast plan exceeding agreed tolerances
  • Stage boundary submission requests Project Board continuation authorisation

Participants can close a project in a controlled manner and transfer ownership.

  • Planned closure confirms products meet acceptance criteria and user requirements
  • Premature closure assesses incomplete products, liabilities and recommended actions
  • Benefits management approach transfers post-project review responsibilities to operations
  • End project report records performance, outcomes, deviations and outstanding issues
  • Lessons report consolidates actionable findings for organisational learning
  • Follow-on action recommendations assign owners, dates and expected outcomes

Participants can tailor PRINCE2 7 controls for sustainability, data and project context.

  • Sustainability considerations incorporated into business case options and product requirements
  • Environmental and social impacts assessed through project risk and benefits controls
  • Digital data management addresses information quality, access, retention and security
  • Tailoring decisions document retained, adapted, combined and omitted method elements
  • Project scale, complexity, risk and delivery approach guide tailoring choices
  • Agile delivery controls aligned with PRINCE2 governance and management stages

Participants can review management products for quality, consistency and decision readiness.

  • Business case assumptions checked against plans, risks and benefit measures
  • Product descriptions tested for measurable quality criteria and ownership
  • Plans reviewed for dependencies, estimates, milestones and tolerance alignment
  • Registers checked for current risks, issues, quality activities and configuration status
  • Reports assessed for decision clarity, forecast accuracy and escalation requirements
  • Cross-document traceability confirms coherent project governance and control

Participants can build, review and present a complete PRINCE2-aligned project management pack for board approval.

  • Project brief and business case assembled from case evidence
  • Product breakdown structure and product descriptions define deliverable scope
  • Project plan, stage plan and tolerances establish delivery control
  • Risk, issue, quality and configuration records support informed governance
  • Board submission presents initiation documentation, decisions and recommended authorisations
  • Peer review tests pack consistency against PRINCE2 principles and practices

Exercises and examples are adapted to each cohort's sectors and roles.

What you take back to work

  1. PRINCE2 project brief template
  2. Business case and benefits management approach
  3. Product breakdown structure and product description set
  4. Project initiation documentation outline
  5. Risk, issue, quality and configuration register pack
  6. Stage control and project board reporting checklist

Who should attend

  • Project Managers — need a disciplined method for planning, control and board reporting
  • Project Coordinators — support managers with accurate plans, registers and management products
  • Project Support Officers — maintain project controls, records and reporting cycles
  • Workstream Leaders — manage delegated delivery within agreed tolerances and product criteria
  • Business Change Managers — connect project outputs to adoption, benefits and operational readiness
  • Project Board Members — make informed decisions on viability, exceptions and stage boundaries

Skills and tools covered

PRINCE2 project governanceProduct-based planningBusiness case developmentStage controlRisk and issue managementMethod tailoring

Tools and standards

PRINCE2 7, Product-based Planning, Quality Review Technique, MoSCoW prioritisation

How the course runs

Training methodology

The course uses short instructor briefings to introduce PRINCE2 7 concepts, followed by case work that develops a project from mandate to closure. Participants analyse governance choices, define products, prepare plans, assess risks and respond to simulated exceptions. Group exercises test project board, project manager and team manager responsibilities. Facilitated reviews compare management products against PRINCE2 requirements, while application planning helps participants adapt templates and controls to their own project setting.

Requirements and prerequisites

Participants should have practical exposure to projects, such as coordinating work packages, contributing to plans, reporting progress or supporting change delivery. Familiarity with basic project terms including scope, schedule, budget, risk and stakeholder is assumed. Prior PRINCE2 Foundation knowledge is strongly recommended because the course builds quickly on PRINCE2 concepts and terminology. Participants do not need prior experience as a project manager, formal project management certification, specialist software skills or advanced financial analysis knowledge. A current or recent project is useful for workplace application planning.

A typical training day

08:30 – 10:30First session
10:30 – 10:45Refreshment break
10:45 – 12:30Second session
12:30 – 13:30Lunch and networking
13:30 – 15:00Third session
15:00 – 15:15Refreshment break
15:15 – 16:30Workshop and daily review

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

What the fee includes

  • Instruction by a practitioner facilitator
  • Full course workbook and materials
  • Exercise files, templates and case studies
  • Refreshments and lunch on classroom deliveries
  • Certificate of completion
  • Post-course application plan

Frequently asked questions

You should understand basic project terminology and have some exposure to project work. PRINCE2 Foundation knowledge is strongly recommended because the course moves quickly into applying the method rather than introducing every term from first principles.

Bring details of a current or recent project if you can share them without breaching confidentiality. A laptop is useful for adapting templates and recording application actions, though course materials are provided.

It is designed for project managers, coordinators, project support staff, workstream leaders and business change professionals. Managers who sit on project boards also benefit from understanding PRINCE2 decision points and controls.

Foundation-level study concentrates on recognising PRINCE2 terms, principles and method components. This Practitioner course focuses on selecting, tailoring and applying those components to project decisions; it also shows how PRINCE2 governance can work with iterative and agile delivery.

You will build a PRINCE2-aligned project pack containing plans, registers, reports and governance records. These materials can be adapted to an active project and used to structure conversations with sponsors, users, suppliers and delivery teams.

Each training day runs from 08:30 to 16:30 and provides about 6.5 contact hours. The first week establishes the method and creates core project materials; the second week applies controls, tailoring and lifecycle processes before the final capstone review and presentation.

Questions about this course?

Ask about dates, fees, group bookings or running it for your team. Our training team replies by email.

Ask on WhatsApp info@skillsetdevelopment.com

Related courses in Project Management