Program Management Office
Led by your EPMO / COO. 9 specialists.
Ask Program Management OfficeNew here? 30 free credits, no card.
- Benefits realizationEnsures projects deliver the value they were approved on — defining measurable benefits, baselining, tracking after delivery, and honest post-implementation review.
- Change and adoptionGets people to actually use what was delivered — stakeholder analysis, communication, training, resistance, and measuring adoption.
- Dependency and risk managementManages delivery risk and cross-team dependencies — identifying, sizing, mitigating and escalating what could stop the work.
- Estimating and contingencyProduces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately.
- Head of pmoThe EPMO lead's remit — what the PMO governs, what it must never become, and how it earns standing rather than compliance.
- Portfolio governanceGoverns the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things.
- Program managementPlans and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the escalations that keep work moving.
- Project deliveryPlans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips.
- Schedule development and analysisBuilds and interrogates a project schedule — logic-driven sequencing, dependency types and lags, float and the critical path, resource loading and leveling, schedule risk analysis, and measuring progress against a baseline rather than against optimism.