Project Delivery Management Training Course

Duration 10 days 16 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 16 Nov 2026 Course code SD-PM-091

Before you join: Participants should have experience contributing to a project, workstream, implementation, operational change or client assignment.

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 in delivery when approved ideas are not converted into controlled work: scope remains ambiguous, decisions arrive late, resources are committed without realistic schedules, and risks become issues before anyone owns them. Project delivery managers must coordinate people, suppliers, budgets, governance bodies and operational teams while preserving a clear line from the business case to measurable results. This course addresses the practical controls required to deliver predictable outcomes under changing conditions.

Participants learn how to establish delivery governance, define scope, structure work, build resource-loaded schedules, control cost, manage risks and report meaningful performance information. They use work breakdown structures, network schedules, critical path analysis, earned value measures, RAID logs, RACI matrices, quality plans, change controls and benefits tracking. The course also covers supplier management, stakeholder engagement, team leadership, handover and project closure. Attention is given to decisions and documents that project managers must produce, review and defend during delivery.

Teaching combines short instructor briefings with cases, facilitated group work, delivery simulations and structured application planning. Participants develop a delivery pack for a project relevant to their role, adding plans and controls as each module introduces them. They leave with reusable templates and a completed project delivery pack that can be adapted for a live project. The course is suited to professionals already involved in projects who need to take stronger responsibility for planning, coordination, reporting and delivery assurance.

What you will be able to do

  • Create a project charter with objectives, governance, tolerances and success criteria
  • Develop a work breakdown structure, schedule network and critical path analysis
  • Produce a cost baseline and calculate earned value performance measures
  • Build a RAID log with ownership, response actions and escalation thresholds
  • Apply RACI analysis and stakeholder mapping to delivery communications
  • Control scope changes through impact assessment, approval and baseline updates
  • Manage supplier deliverables using acceptance criteria, milestones and contract controls
  • Present a complete project delivery pack for governance review

Benefits of attending

For you

  • Produce credible project plans for governance and sponsor approval
  • Identify schedule slippage before critical milestones are missed
  • Explain cost, scope and risk trade-offs using structured evidence
  • Run clearer status reviews with accountable owners and actions
  • Build a portfolio of reusable delivery documents for future assignments

For your organisation

  • Earlier visibility of schedule, cost and dependency threats
  • More consistent governance papers and decision records
  • Better control of scope growth and unapproved commitments
  • Clearer ownership across project teams, suppliers and operational units
  • Stronger handover readiness and benefits accountability after project closure

Course modules

16 modules over 10 days

Participants can frame a project for controlled delivery using clear objectives, authority and success measures.

  • Project lifecycle selection using predictive, adaptive and hybrid delivery approaches
  • Business case assumptions translated into measurable delivery objectives
  • Success criteria separated from outputs, outcomes and operational benefits
  • Project charter authority, constraints, tolerances and escalation routes
  • Assumption, dependency, constraint and issue definitions applied consistently
  • Delivery context assessed through organisational strategy and portfolio priorities
  • Early feasibility questions that prevent unapproved work entering delivery

Participants can establish governance arrangements that support timely decisions and accountable oversight.

  • Governance structure defining sponsor, steering group and project manager accountabilities
  • Delegated authority matched to budget, scope and schedule tolerances
  • Stage gates designed around evidence, decisions and funding releases
  • RACI matrix clarifying approval, consultation and delivery responsibilities
  • Decision log records rationale, owner, date and follow-up actions
  • Escalation paths triggered by agreed thresholds rather than personal preference
  • Assurance reviews distinguish compliance checks from management decision forums

Participants can plan stakeholder engagement and communication around influence, information needs and project decisions.

  • Stakeholder mapping using power, interest, influence and impact criteria
  • Engagement strategies differentiated for sponsors, users, regulators and suppliers
  • Communication plan links audiences to messages, channels and frequency
  • Resistance analysis identifies concerns, incentives and required management actions
  • Sponsor briefings focus on decisions, exceptions and strategic implications
  • Meeting cadence supports coordination without creating unnecessary reporting burden
  • Feedback routes capture user requirements and emerging operational impacts

Participants can define deliverable scope and control requirements from baseline through acceptance.

  • Requirements elicitation distinguishes business, user, functional and nonfunctional needs
  • Scope statement defines inclusions, exclusions, assumptions and acceptance boundaries
  • Work breakdown structure decomposes deliverables into manageable work packages
  • Requirements traceability matrix connects needs, deliverables, tests and approvals
  • Acceptance criteria specify observable conditions for completed deliverables
  • Scope baseline combines approved scope statement, WBS and WBS dictionary
  • Gold plating risks addressed through agreed requirements and change control

Participants can build a logically sequenced schedule and identify activities requiring close control.

  • Activity definition converts work packages into estimable schedule activities
  • Precedence diagramming maps finish-to-start, start-to-start and finish-to-finish relationships
  • Duration estimates use expert judgement, analogous data and three-point estimating
  • Critical path method identifies zero-float activities and schedule exposure
  • Milestone schedule communicates major decisions, approvals and delivery commitments
  • Schedule compression compares crashing costs with fast-tracking delivery risks
  • Rolling-wave planning maintains detail where work is imminent and understood

Participants can align people, equipment and external purchases with planned delivery work.

  • Resource breakdown structure groups labour, equipment, materials and services
  • Capacity planning tests resource demand against available skills and time
  • Responsibility assignments connect work packages with named accountable roles
  • Resource levelling resolves overallocations while protecting critical delivery commitments
  • Make-or-buy analysis compares internal capability, cost, risk and timing
  • Procurement plan defines packages, sourcing route, milestones and contract ownership
  • Supplier dependencies integrated into the master schedule and RAID log

Participants can produce a cost baseline and interpret cost performance during delivery.

  • Bottom-up estimating aggregates work package labour, materials and supplier costs
  • Contingency reserves distinguish identified risk provision from management reserve
  • Cost baseline aligns approved budgets with scheduled work and control accounts
  • Cash flow forecast profiles planned expenditure against funding availability
  • Earned value management calculates planned value, earned value and actual cost
  • Cost performance index and schedule performance index guide corrective action
  • Estimate at completion forecasts final cost from current performance data

Participants can identify, analyse and control threats, opportunities and live delivery issues.

  • Risk workshop identifies causes, events, consequences and early warning indicators
  • Probability-impact matrix prioritises risks using defined scoring criteria
  • Risk appetite and tolerance guide response selection and escalation decisions
  • Response planning assigns avoid, reduce, transfer, accept and exploit actions
  • RAID log integrates risks, assumptions, issues and dependencies for review
  • Issue management records ownership, due dates, decisions and closure evidence
  • Quantitative risk analysis uses three-point estimates for uncertain durations

Participants can plan quality assurance, quality control and acceptance evidence for project deliverables.

  • Quality management plan defines standards, measures, reviews and acceptance responsibilities
  • Quality assurance checks process adherence before defects reach acceptance stages
  • Quality control uses inspections, testing and defect trend analysis
  • Acceptance plan identifies approvers, evidence, criteria and decision timing
  • Root cause analysis applies five whys and fishbone diagrams
  • Nonconformance records track defects, corrective actions and verification results
  • Lessons from defects update standards, checklists and future work packages

Participants can run coordinated delivery controls that connect progress, dependencies, actions and decisions.

  • Integrated master plan links scope, schedule, cost, risk and resource baselines
  • Weekly control cycle reviews progress, constraints, actions and forecast changes
  • Progress measurement uses completed milestones, physical completion and earned value
  • Dependency management identifies predecessor commitments and interface ownership
  • Action tracker distinguishes actions from decisions, risks and unresolved issues
  • Control account reviews compare actual performance with approved baseline commitments
  • Recovery plans sequence corrective actions, owners, deadlines and residual risks

Participants can assess, approve and implement changes without losing baseline control.

  • Change request captures rationale, urgency, impacts and requested decision
  • Impact assessment examines scope, schedule, cost, quality, risk and benefits
  • Change authority applies delegated thresholds and formal approval routes
  • Configuration management identifies controlled products, versions and status records
  • Baseline updates follow approval rather than informal delivery team agreement
  • Change log provides an auditable record of decisions and implementation status
  • Emergency changes use documented retrospective review and corrective controls

Participants can create decision-focused reports that reveal performance, forecasts and required interventions.

  • Project dashboard presents milestones, budget, risks, issues and decisions required
  • RAG status criteria use evidence-based thresholds rather than subjective judgement
  • Variance analysis explains causes, consequences, trends and proposed corrective action
  • Forecasting updates completion dates, costs and resource needs from current evidence
  • Milestone trend analysis reveals recurring slippage before deadlines are missed
  • Exception reports focus governance attention on matters outside agreed tolerances
  • Narrative reporting separates facts, assumptions, decisions and management recommendations

Participants can lead project teams through clear expectations, constructive challenge and disciplined follow-through.

  • Team charter establishes purpose, behaviours, decision rules and meeting disciplines
  • Situational leadership adapts direction and support to capability and commitment
  • Psychological safety supports early reporting of risks, errors and concerns
  • Conflict resolution distinguishes task conflict from interpersonal conflict
  • Accountability conversations address missed commitments using evidence and agreed actions
  • Cross-functional coordination clarifies interfaces between delivery and operational teams
  • Recognition practices reinforce behaviours that support reliable project delivery

Participants can control supplier performance against contractual commitments, milestones and acceptance requirements.

  • Statement of work defines deliverables, boundaries, service levels and acceptance criteria
  • Contract milestone plan aligns supplier outputs with integrated project dependencies
  • Supplier performance reviews assess delivery, quality, risk and corrective actions
  • Service level measures distinguish operational performance from project delivery progress
  • Commercial change control evaluates contractual, cost and schedule consequences
  • Acceptance certificates document evidence, approvals, exceptions and outstanding obligations
  • Supplier exit planning protects continuity, knowledge transfer and asset return

Participants can close projects responsibly and transfer ownership of outcomes and benefits to operations.

  • Operational readiness assessment tests people, processes, systems and support arrangements
  • Handover plan transfers assets, documentation, training and ownership responsibilities
  • Benefits realisation plan identifies measures, owners, timing and data sources
  • Project closure checklist confirms acceptance, contracts, finances and records completion
  • Lessons learned review captures evidence, root causes and recommended actions
  • Post-implementation review compares realised outcomes with approved business case expectations
  • Closure report records final performance, residual risks and transition decisions

Participants can build, review and present a complete project delivery pack for governance approval.

  • Project charter establishes objectives, authority, success measures and delivery constraints
  • Integrated plan combines scope, schedule, budget, resources and dependency controls
  • RAID log prioritises current threats, issues, assumptions and external dependencies
  • Governance report presents performance, forecasts, exceptions and decisions required
  • Change request demonstrates impact analysis and controlled baseline amendment
  • Handover and benefits plan assigns operational ownership beyond project closure
  • Peer review tests document consistency, evidence quality and decision readiness

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

What you take back to work

  1. Project charter template
  2. Integrated delivery plan
  3. RAID log and escalation matrix
  4. Cost baseline and earned value tracker
  5. Change control register
  6. Governance reporting dashboard

Who should attend

  • Project Managers — need stronger controls for planning, reporting and delivery decisions
  • Project Coordinators — prepare to manage workstreams and integrated delivery plans
  • Programme Officers — coordinate dependencies, governance actions and project reporting
  • Operations Managers — deliver change initiatives without disrupting business operations
  • PMO Analysts — support consistent planning, assurance and portfolio reporting
  • Technical Workstream Leads — manage specialist deliverables within wider project commitments

Skills and tools covered

Delivery planningSchedule controlCost performance analysisRisk managementStakeholder engagementGovernance reporting

Tools and standards

PMBOK Guide, PRINCE2, ISO 21502, Earned Value Management

How the course runs

Training methodology

The course uses short briefings to introduce methods, followed by cases drawn from infrastructure, technology, public service and business change projects. Participants work in groups to interpret project evidence, build plans, assess trade-offs and respond to delivery events through simulations. Instructor feedback focuses on the quality of assumptions, controls and decisions. Individual application planning links each method to a current or recent project. The final capstone brings the planning, control and reporting elements into one governance-ready delivery pack.

Requirements and prerequisites

Participants should have experience contributing to a project, workstream, implementation, operational change or client assignment. They should recognise common project terms such as scope, milestone, budget, risk and stakeholder, and be comfortable working with spreadsheets and project documentation. Prior project manager experience is useful but not essential. The course does not require a formal project management qualification, prior use of specialist scheduling software, advanced finance knowledge or familiarity with a particular delivery methodology. Participants should bring a current or recent project example where possible.

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 have contributed to a project, workstream, implementation or operational change initiative. Formal project management certification and prior use of scheduling software are not required.

Bring details of a current or recent project if you can, including its objectives, stakeholders, milestones and known challenges. You can apply the course templates to that project during the course.

It is designed for project managers, coordinators, workstream leads, PMO staff and operations managers responsible for delivery activity. It also suits technical specialists moving into project leadership responsibilities.

This course assumes familiarity with basic project terminology and concentrates on the controls used during real delivery. It goes further into governance, integrated planning, earned value, supplier management, change control and recovery action.

The delivery pack provides working formats for charters, schedules, RAID logs, reporting, change control and handover. Participants can adapt these documents to an active project or upcoming initiative.

The first part establishes planning foundations including scope, schedules, resources, costs and risks. The later part focuses on control, reporting, leadership, suppliers, handover and a capstone presentation; each training day runs from 08:30 to 16:30 with about 6.5 contact hours.

Questions about this course?

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