Integrated Project Management and Controls Training Course

Participants can define controlled scope using deliverable-based decomposition and traceable requirements.

• WBS decomposition rules applied to products, deliverables, and work packages
• 100 percent rule tested against approved scope baseline
• Work package dictionaries specify ownership, boundaries, and acceptance evidence
• Requirements traceability matrix connects needs, deliverables, and verification
• Scope change requests assessed for baseline and benefits effects
• Control accounts positioned at practical management responsibility points

Participants can develop logic-driven schedules and establish a controlled schedule baseline.

• Precedence diagramming maps finish-to-start, leads, lags, and constraints
• Activity durations estimated using three-point and reference-class methods
• Critical path and near-critical paths interpreted for management action
• Resource calendars and availability constraints incorporated into network schedules
• Schedule baseline approved with milestones, coding, and update rules
• Rolling-wave planning handles uncertain downstream work without false precision

Participants can produce cost estimates, contingency allowances and time-phased cost baselines.

• Basis of estimate records quantities, rates, assumptions, exclusions, and uncertainty
• Bottom-up estimates rolled into cost accounts and control accounts
• Parametric estimates tested against historical productivity and unit costs
• Contingency derived from quantified risk exposure rather than padding
• Time-phased cost baseline reconciled with funding and procurement plans
• Estimate maturity assessed using defined scope and design evidence

Participants can connect subsidiary project plans into one integrated control architecture.

• Integrated master plan links scope, schedule, cost, risk, and benefits
• Control account plans align work packages with responsible managers
• Project management plan consolidates subsidiary plans and control thresholds
• Data dictionary establishes common codes, dates, units, and status rules
• Configuration management identifies controlled documents, products, and version authority
• Management reserves separated from cost baseline and contingency budgets

Participants can identify, assess and respond to project risks using qualitative and quantitative methods.

• Risk breakdown structure categorises technical, commercial, delivery, and external threats
• Probability-impact scoring prioritises threats and opportunities using defined scales
• Qualitative risk register records triggers, owners, responses, and due dates
• Monte Carlo outputs interpreted for schedule confidence and contingency decisions
• Response plans assign avoidance, mitigation, transfer, acceptance, and exploitation actions
• Risk exposure reviewed against change requests and emerging issues

Participants can integrate supplier commitments, contract changes and delivery evidence into project controls.

• Make-or-buy analysis considers capability, cost, risk, and schedule implications
• Procurement packages aligned with WBS, interfaces, milestones, and acceptance criteria
• Contract types allocated according to scope certainty and risk ownership
• Supplier schedules integrated through data dates, deliverables, and interface milestones
• Commercial change control preserves authorised scope, value, and audit trails
• Expediting reports distinguish supplier progress claims from verified completion

Participants can assign project accountability and manage resource constraints against delivery commitments.

• Responsibility assignment matrix connects WBS work packages to accountable roles
• Resource-loaded schedules expose demand peaks, bottlenecks, and sequencing conflicts
• Capacity plans balance specialist availability, learning curves, and productivity assumptions
• RACI matrices clarify approvals, consultations, notifications, and delivery ownership
• Resource levelling evaluates schedule impact before changing committed milestones
• Team working agreements establish escalation routes and decision turnaround times

Participants can select objective progress measures and run reliable project status cycles.

• Progress measurement techniques selected by deliverable type and work maturity
• Physical percent complete supported by objective completion and acceptance evidence
• Weighted milestones prevent subjective reporting on complex engineering deliverables
• Rules of credit define earned value at measurable completion points
• Data-date discipline separates actual status from forecast assumptions
• Status cycles coordinate field updates, supplier inputs, and management reporting

Participants can calculate and interpret earned value metrics for cost and schedule control.

• Planned value, earned value, and actual cost calculated consistently
• Cost and schedule variances traced to control accounts and causes
• CPI, SPI, TCPI, EAC, and ETC interpreted for forecasts
• Performance measurement baseline reconciles budgets, schedules, and authorised work
• Earned value data quality checks identify timing and coding errors
• ANSI/EIA-748 control principles applied proportionately to project controls

Participants can prepare evidence-based completion forecasts and explain their confidence levels.

• Estimate at completion forecast using independent, cumulative, and bottom-up methods
• Schedule forecast dates derived from logic, productivity, and risk evidence
• Trend registers distinguish one-off variances from systemic performance deterioration
• Cash-flow forecasts connect commitments, invoices, payment terms, and funding
• To-complete analysis challenges remaining durations, quantities, and resource assumptions
• Forecast narratives state confidence ranges, drivers, and management actions

Participants can assess, authorise, implement and verify changes without compromising baseline integrity.

• Integrated change control evaluates scope, schedule, cost, risk, and benefits
• Change control board terms define authority, quorum, and decision records
• Impact assessments trace proposed changes through baselines and contracts
• Configuration item registers maintain product versions, approvals, and release status
• Baseline freezes protect reporting integrity while authorised changes proceed
• Change logs distinguish requests, decisions, implementation actions, and verification

Participants can create project reports that support decisions rather than merely describe activity.

• Control dashboards separate leading indicators from lagging performance measures
• Exception reports focus attention on thresholds, trends, decisions, and owners
• Milestone trend analysis reveals persistent slippage before critical delay
• Integrated reports reconcile schedule, cost, risk, scope, and benefits data
• Management narratives explain variance drivers, recovery actions, and decisions required
• Report calendars align data dates, review forums, and escalation deadlines

Participants can test whether project controls are reliable, traceable and suitable for management assurance.

• Project control audits test baseline integrity, traceability, and data reliability
• Health checks assess governance, planning quality, reporting, and corrective action
• Internal control evidence retained for approvals, forecasts, changes, and payments
• Independent estimates challenge optimism bias and unsupported contingency assumptions
• Lessons learned captured with causes, consequences, and preventive actions
• Closeout reviews confirm deliverable acceptance, benefits handover, and records

Participants can diagnose deteriorating performance and prepare a practical recovery plan.

• Root-cause analysis separates symptoms, constraints, and controllable performance drivers
• Schedule compression compares crashing, fast tracking, resequencing, and scope trade-offs
• Recovery plans define actions, owners, dates, resources, and success measures
• Cost recovery options test productivity, claims, rework, and procurement savings
• Decision trees evaluate response choices under uncertainty and escalation limits
• Recovery governance tracks commitments, residual risks, and benefit realisation

Participants can define practical data structures and quality controls for integrated project reporting.

• Integrated control data model maps WBS, OBS, CBS, and coding structures
• Spreadsheet control registers use validation rules, versioning, and audit trails
• Dashboard specifications define source systems, refresh cadence, and calculations
• Data quality checks reconcile approved baselines, actuals, and forecast records
• Common data environments control document status, access, and transmittals
• Automation candidates identified where manual reporting causes delay or error

Participants can plan project communications and escalation routes around stakeholder decision needs.

• Stakeholder analysis maps influence, interest, information needs, and decision authority
• Communication matrix assigns reports, frequency, channels, owners, and recipients
• Escalation thresholds distinguish routine variance from sponsor-level intervention
• Interface registers manage handoffs, dependencies, responsibilities, and acceptance evidence
• Meeting cadences link working reviews, control boards, and governance gates
• Conflict resolution records decisions, dissent, commitments, and follow-up actions

Participants can build, review and present a complete integrated project controls pack for a defined project scenario.

• Project control plan integrates baselines, governance, data, and reporting cycles
• WBS, schedule, cost plan, risk register, and RAM aligned
• Performance measurement methods selected for representative work packages and suppliers
• Forecast, dashboard, change, and recovery controls tested against scenarios
• Peer review challenges assumptions, thresholds, data quality, and control gaps
• Executive presentation communicates status, decisions required, and corrective actions