Cross-project dependencies, tranches and gates modelled properly, so a slip in one project moves the programme date instead of surfacing three weeks later in a status meeting.
Roll-up is derived from the underlying project records — no consolidated deck is ever assembled by hand.
Explicit, typed dependencies between deliverables in different projects - finish-to-start, resource-based, contractual - with automatic impact analysis when a predecessor slips.
In an AMI rollout, meter firmware, head-end software, field installation and regulatory approval are separate projects with hard interlocks.
Configurable lifecycle gates with defined entry and exit criteria, mandatory deliverables, approval routing, and enforcement that a project cannot progress until the gate is formally passed.
This is the mechanism that makes an SLA-aligned process suite real rather than documented.
Consolidating cost, effort and earned value from projects to programme level, producing programme CPI, SPI, estimate-at-completion and variance-at-completion.
Programme-level EVM is the earliest reliable warning of trouble - it detects drift months before a milestone is formally missed, which is exactly when intervention is still cheap.
A genuine multi-level object model where programmes are real entities with their own budget, schedule, risks, benefits and governance - not just a tag or folder applied to a group of projects.
Programme management is where most work-management tools quietly fail.
Automatic consolidation of project milestones into a programme-level milestone plan, with status, forecast dates, variance against baseline and trend.
Programme milestones are the currency of steering-committee reporting.
A consolidated RAID log at programme level, aggregating from projects and holding programme-specific items, with owners, due dates, escalation paths and closure evidence.
RAID is the working record of programme governance and the first thing an auditor or a new programme director asks for.
Formal change requests against an approved baseline, with impact assessment on scope, cost, schedule and benefits, approval routing, and a versioned history of every baseline.
Baseline discipline is the difference between a governed programme and a moving target.
Native support for scaled agile constructs - agile release trains, program increments, PI planning boards, epics and features linked to team backlogs, and flow metrics.
Relevant if part of the portfolio - typically the software organisation - runs SAFe or a similar framework while the rest runs waterfall.
Generating steering-committee-ready status packs directly from live data on a schedule, rather than assembling them manually from project submissions.
Status reporting is typically the largest single consumer of PMO effort.
Managing the benefits case at programme level where benefits usually actually land, with attribution across contributing projects and tracking through to realisation.
Benefits rarely belong to one project.
Every capability above states the lowest plan that includes it. Nothing here is an add-on and nothing is metered.
The full matrix shows all 71 capabilities and the lowest plan that includes each one.
