Project Delivery Training Course

Participants can define project scope and control requirements without creating ambiguity or uncontrolled work.

• Scope statement separates included work, exclusions and project boundaries
• Requirements elicitation uses interviews, workshops, observation and document analysis
• MoSCoW prioritisation distinguishes essential requirements from desirable enhancements
• Acceptance criteria specify evidence required for deliverable approval
• Requirements traceability matrix connects needs, deliverables, tests and acceptance
• Scope creep indicators identified before unapproved work consumes resources

Participants can decompose approved scope into manageable deliverables, work packages and accountable owners.

• Work breakdown structure decomposes scope into deliverables and work packages
• Product breakdown identifies tangible outputs before activity planning begins
• Work package definitions specify owner, effort, criteria and dependencies
• RACI matrix clarifies responsibility, accountability, consultation and information flows
• Control accounts connect work packages with reporting and budget responsibility
• Rolling-wave planning manages detail levels across near-term and later work

Participants can create defensible estimates using assumptions, historical evidence and appropriate estimating techniques.

• Analogous estimating uses comparable projects and adjusted delivery assumptions
• Three-point estimates calculate expected duration from optimistic and pessimistic ranges
• Bottom-up estimates aggregate work package effort, duration and direct costs
• Estimating basis records sources, exclusions, contingencies and confidence levels
• Resource calendars expose availability constraints affecting schedule feasibility
• Contingency reserves distinguish identified risk allowances from management reserves

Participants can produce a logical, resource-aware schedule that identifies the work driving completion.

• Precedence diagramming maps finish-to-start, start-to-start and finish-to-finish relationships
• Activity sequencing tests dependencies, leads, lags and external commitments
• Critical path method identifies activities determining the planned completion date
• Float analysis distinguishes schedule flexibility from critical delivery exposure
• Milestone schedules communicate decision points, approvals and key deliverables
• Schedule compression compares crashing costs with fast-tracking risk consequences

Participants can assign people, facilities and specialist inputs while managing capacity constraints.

• Resource breakdown structure categorises labour, equipment, materials and specialist services
• Capacity planning compares demand profiles with named resource availability
• Resource levelling resolves over-allocation within fixed capacity constraints
• Resource smoothing protects milestone dates while reducing workload volatility
• Responsibility assignments align work package ownership with decision authority
• Team mobilisation plan covers onboarding, roles, access and working agreements

Participants can establish approved cost and schedule baselines for disciplined performance control.

• Time-phased budget aligns planned expenditure with scheduled work packages
• Cost baseline separates authorised budgets from contingency and management reserves
• Funding profile identifies cash requirements, approval gates and release conditions
• Baseline approval records authorised scope, schedule, budget and assumptions
• Control thresholds trigger investigation before tolerances are exceeded
• Forecasting methods distinguish committed costs, actuals and estimated completion costs

Participants can assess delivery uncertainty and implement proportionate actions for risks, issues and dependencies.

• Risk register captures cause, event, effect, owner and response
• Probability-impact matrix prioritises threats and opportunities for management attention
• Response strategies include avoid, mitigate, transfer, accept and exploit
• Issue log records current problems, decisions, actions and escalation dates
• Dependency mapping identifies predecessor commitments and external delivery interfaces
• Risk appetite and tolerance guide escalation and contingency decisions

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

• Quality management plan defines standards, reviews, tests and approval evidence
• Quality assurance examines process compliance before deliverables reach acceptance
• Quality control verifies outputs against specifications and acceptance criteria
• Inspection and test plans assign checkpoints, methods, records and approvers
• Defect management records severity, correction ownership and retest outcomes
• Acceptance records confirm customer approval, conditions and outstanding obligations

Participants can design practical governance that supports timely oversight, decisions and escalation.

• Governance structure defines sponsor, steering group, project manager and workstream roles
• Terms of reference set meeting purpose, authority, membership and cadence
• Stage-gate reviews assess readiness against agreed evidence and decision criteria
• Delegated authorities specify approval limits for scope, cost and schedule
• Project assurance provides independent checks on controls, evidence and delivery confidence
• Escalation routes distinguish operational resolution from sponsor-level intervention

Participants can engage stakeholders with targeted communication, consultation and decision-making arrangements.

• Stakeholder mapping assesses influence, interest, impact and engagement needs
• Power-interest grids determine communication intensity and engagement priorities
• Communication plan specifies audience, purpose, channel, frequency and owner
• Sponsor briefings focus on decisions, tolerances, risks and benefit progress
• Difficult stakeholder conversations use interests, evidence and agreed next actions
• Meeting disciplines record decisions, actions, owners and due dates

Participants can manage project supplier interfaces from requirement definition through delivery assurance.

• Make-or-buy analysis compares capability, cost, control and delivery risk
• Statement of work defines scope, deliverables, service levels and acceptance
• Supplier evaluation criteria weight technical capability, price, risk and capacity
• Contract milestones connect payment events with verified deliverable acceptance
• Supplier performance reviews assess progress, defects, risks and corrective actions
• Interface register coordinates responsibilities between project, supplier and operations teams

Participants can report project performance clearly using meaningful indicators, forecasts and exceptions.

• Status reports distinguish completed work, current commitments and forecast outcomes
• Milestone trend analysis reveals repeated movement in key delivery dates
• Earned value management compares planned value, earned value and actual cost
• Schedule performance index indicates efficiency of planned work completion
• Cost performance index signals variance between value achieved and expenditure
• Exception reports present variance causes, options, decisions and recovery actions

Participants can assess, approve and implement changes while protecting delivery commitments and benefits.

• Change requests document rationale, urgency, scope and requested decision
• Impact assessment examines schedule, cost, risk, quality and benefit effects
• Change control board reviews material changes against approved tolerances
• Configuration management maintains current versions, approvals and product records
• Recovery plans combine root-cause analysis, replanning and accountable corrective actions
• Decision logs preserve rationale for accepted, rejected and deferred changes

Participants can prepare projects for operational adoption, formal closure and benefits follow-through.

• Transition plan assigns operational readiness, training, support and ownership actions
• Operational readiness assessments test people, processes, systems and support arrangements
• Cutover planning coordinates timing, rollback criteria, communications and command structures
• Handover packs include asset records, procedures, warranties and support contacts
• Lessons learned reviews capture evidence, causes, recommendations and accountable follow-up
• Closure reports confirm acceptance, final costs, residual risks and benefit ownership

Participants can build, review and present a complete project delivery pack with justified delivery decisions.

• Project mandate aligns benefits, scope, success criteria and governance authority
• Integrated plan combines work breakdown, schedule, resources and cost baseline
• Risk, issue and dependency registers support prioritised management action
• Stakeholder communications address sponsor decisions, supplier interfaces and operational readiness
• Performance report presents milestones, earned value, forecasts and exceptions
• Change and recovery recommendations defend proposed actions using impact evidence