Executive Project Management Training Course

Participants can design governance arrangements that support timely decisions and credible oversight.

• Governance layers defined for sponsor, steering committee, project manager and workstream leads
• RACI matrix built around approvals, deliverables, controls and escalation responsibilities
• Stage-gate reviews structured around evidence, tolerances, decisions and accountable signatories
• Three lines model applied to management control, assurance and independent review
• Decision log maintained with options, recommendations, owners, deadlines and rationale
• Assurance plans aligned with audit requirements, funding conditions and delivery risk

Participants can develop a decision-ready business case with explicit value, costs and assumptions.

• Five Case Model used to structure strategic, economic and commercial justification
• Problem statements converted into measurable objectives, options and investment criteria
• Options appraisal compared through cost, benefit, risk, deliverability and strategic fit
• Benefits maps link project outputs to operational outcomes and measurable value
• Financial assumptions documented for capital costs, operating costs and contingencies
• Benefit owners assigned with measures, baselines, targets and review dates

Participants can define controlled scope and translate deliverables into manageable work packages.

• Scope statements define inclusions, exclusions, acceptance criteria and delivery boundaries
• Product breakdown structures identify tangible outputs before planning project activities
• Work breakdown structures decompose deliverables into accountable, measurable work packages
• WBS dictionaries record descriptions, owners, assumptions, interfaces and acceptance evidence
• Requirements traceability matrices connect stakeholder needs, specifications, tests and deliverables
• Scope baseline approved through documented requirements, WBS and acceptance criteria

Participants can build and analyse an integrated schedule using dependencies, milestones and critical paths.

• Precedence diagramming maps finish-to-start, start-to-start and lag relationships
• Activity sequencing exposes external dependencies, approvals, handovers and supplier interfaces
• Critical path method calculates float, constraints and schedule sensitivity
• Milestone schedules distinguish decision points, contractual dates and delivery commitments
• Schedule baselines freeze approved logic, durations, milestones and calendar assumptions
• Look-ahead planning identifies near-term constraints, owners and removal actions

Participants can produce resource and duration estimates supported by transparent planning assumptions.

• Bottom-up estimating aggregates work package effort, duration, materials and services
• Three-point estimates apply optimistic, most likely and pessimistic duration assumptions
• Resource breakdown structures classify people, equipment, facilities and specialist services
• Resource loading tests planned demand against availability, skills and utilisation limits
• Resource levelling resolves overallocations while protecting critical milestones and dependencies
• Planning assumptions register records productivity rates, calendars and resource constraints

Participants can identify, analyse and control threats and opportunities affecting project objectives.

• Risk breakdown structures organise threats across technical, commercial and delivery categories
• Risk statements written using cause, event and impact formulation
• Probability-impact matrices prioritise risks using agreed scoring definitions and thresholds
• Monte Carlo analysis tests schedule confidence and contingency requirements
• Risk responses selected through avoid, mitigate, transfer, accept and exploit strategies
• Risk owners maintain triggers, response actions, due dates and residual ratings

Participants can create stakeholder engagement and communication plans suited to influence and impact.

• Stakeholder mapping assesses interest, influence, impact, expectations and likely resistance
• Power-interest grids determine engagement approaches for sponsors, users and regulators
• Communications plans specify audience, message, channel, frequency, owner and feedback route
• Stakeholder interviews surface unspoken concerns, acceptance conditions and political constraints
• Issue framing separates facts, interests, options, recommendations and required decisions
• Escalation communications present consequences, thresholds, choices and recommended actions

Participants can manage procurement interfaces, supplier obligations and contractual delivery risks.

• Make-buy analysis compares internal capability, market capacity, cost and control
• Statement of work defines deliverables, service levels, milestones and acceptance conditions
• Contract types compared across fixed-price, time-and-materials and cost-reimbursable arrangements
• Bid evaluation criteria weight technical quality, commercial value, risk and capacity
• Supplier performance reviews track deliverables, defects, invoices, risks and corrective actions
• Contract change requests assessed for scope, price, schedule and liability implications

Participants can establish quality controls that demonstrate requirements have been met.

• Quality management plans define standards, controls, records and acceptance responsibilities
• ISO 9001 principles applied to process control, evidence and corrective action
• Requirements prioritised through MoSCoW categories and agreed release criteria
• Acceptance test plans specify scenarios, evidence, approvers and defect resolution
• Quality assurance reviews examine process adherence before deliverable acceptance
• Root cause analysis uses five whys and fishbone diagrams

Participants can establish cost baselines and interpret earned value performance measures.

• Cost breakdown structures align budgets with work packages and control accounts
• Time-phased budgets create planned value profiles across project reporting periods
• Earned value measures planned value, earned value and actual cost
• Schedule performance index and cost performance index diagnose delivery variance
• Estimate at completion forecasts total cost using current performance trends
• Management reserves distinguished from contingency reserves and authorised budget changes

Participants can lead cross-functional project teams through accountability, conflict and delivery pressure.

• Team charters establish purpose, roles, behaviours, meeting routines and decision rules
• Situational leadership adapts direction and support to competence and commitment
• Psychological safety supports reporting of risks, errors, concerns and dissent
• Thomas-Kilmann modes guide responses to project conflict and competing interests
• Delegation plans match authority, capability, accountability and coaching requirements
• Performance conversations address missed commitments, causes, recovery actions and support

Participants can select and govern adaptive delivery methods alongside predictive project controls.

• Agile values compared with predictive planning assumptions and governance needs
• Scrum roles define product ownership, delivery accountability and facilitation responsibilities
• Product backlogs prioritise user value, risk reduction and dependency resolution
• Sprint planning converts prioritised backlog items into short-cycle delivery commitments
• Kanban boards visualise workflow, work-in-progress limits and bottleneck patterns
• Hybrid delivery models integrate fixed milestones with iterative product development

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

• Change requests capture rationale, urgency, benefits, impacts and requested decisions
• Impact assessments quantify scope, schedule, cost, risk and resource consequences
• Change control boards evaluate requests against priorities, tolerances and available funding
• Configuration management identifies controlled items, versions, baselines and approval status
• Requirements traceability confirms approved changes reach design, testing and acceptance
• Change logs preserve decisions, rejected requests, implementation dates and residual actions

Participants can produce concise performance reports that support management intervention.

• Project dashboards combine milestone status, cost variance, risks, issues and decisions
• Traffic-light reporting uses defined thresholds rather than subjective status labels
• Forecast completion dates updated through remaining duration, dependencies and constraints
• Issue registers separate current problems from uncertain future risk events
• Exception reports present tolerance breaches, options, recommendations and required authorities
• Management information tailored for sponsors, steering committees and operational leaders

Participants can diagnose project distress and develop credible recovery or closure recommendations.

• Recovery assessments test scope viability, schedule realism, funding and leadership capacity
• Root cause analysis distinguishes symptoms from systemic delivery control failures
• Schedule compression evaluates crashing, fast tracking, risk and resource consequences
• Rebaselining criteria distinguish justified recovery plans from concealed underperformance
• Turnaround plans sequence stabilisation actions, decisions, owners and review checkpoints
• Project termination recommendations address sunk costs, obligations, records and transition

Participants can plan operational handover, closure evidence and post-project benefits management.

• Operational readiness assessments test people, processes, systems, support and capacity
• Transition plans assign handover activities, owners, dates, dependencies and acceptance evidence
• Benefits realisation plans track outcomes beyond formal project completion
• Post-implementation reviews compare achieved results with business case assumptions
• Lessons learned methods capture observations, causes, recommendations and reusable actions
• Closure checklists confirm contracts, assets, records, approvals and stakeholder communications

Participants can manage project dependencies and resource conflicts within portfolio priorities.

• Dependency maps identify shared resources, interfaces, milestones and critical assumptions
• Portfolio prioritisation applies strategic fit, value, risk, urgency and capacity criteria
• Resource demand profiles expose conflicts across projects, operations and planned initiatives
• Benefits dependency networks identify prerequisites for value realisation and sequencing
• Portfolio reporting distinguishes project health from aggregate strategic delivery confidence
• Senior forums resolve cross-project trade-offs using transparent decision criteria

Participants can incorporate ethical, compliance and public-interest considerations into project decisions.

• Ethical decision frameworks test consequences, duties, rights, fairness and transparency
• Conflict-of-interest declarations protect procurement, approvals and supplier selection decisions
• Data protection requirements incorporated into scope, design, controls and acceptance criteria
• Environmental and social impacts assessed through materiality, mitigation and monitoring measures
• Compliance registers track obligations, evidence, owners, deadlines and assurance activities
• Whistleblowing routes and escalation protections support early reporting of misconduct

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

• Project charter consolidates objectives, scope, governance, assumptions and success measures
• Integrated baseline links WBS, schedule, resources, budget, risks and dependencies
• Stakeholder and communications plans address engagement, resistance, decisions and escalation
• Control framework combines reporting, earned value, change management and assurance
• Executive review tests affordability, deliverability, benefits, compliance and risk exposure
• Board presentation communicates recommendation, trade-offs, decisions and immediate next actions