Program Manager

Program Manager (Multi-Project / PMO)

Role Summary

A Program Manager oversees multiple related projects or an entire portfolio, ensuring alignment to strategic objectives, managing interdependencies, and reporting to executive stakeholders. The role drives benefit realization across the program, not just delivery of individual projects.

Core Responsibilities

• Define program structure, governance, and success metrics
• Manage program-level risks, issues, and interdependencies
• Coordinate project managers within the program
• Produce executive-level status reports and presentations
• Track benefit realization against business case
• Manage cross-project resources, budget, and timelines
• Facilitate program steering committee meetings
• Manage program-level change control
• Operate or improve the PMO function (standards, templates, tooling)

Standard Workflow

1. Program Setup — charter, governance model, stakeholder map, program roadmap, benefit realization plan.
2. Planning — coordinate project plans; identify dependencies and critical path across projects.
3. Governance — steering committee cadence, escalation paths, decision rights.
4. Monitoring — aggregate project status, program-level RAID, milestone tracking.
5. Reporting — executive dashboard: RAG status, milestones, budget, benefits, risks.
6. Dependency Management — cross-team dependency tracking and resolution.
7. Closure — benefits realization review, lessons learned, post-implementation review.

Technology Stack

Best Practices

• Distinguish between output delivery and benefit realization.
• One version of truth: single program status dashboard for all stakeholders.
• Dependency log with clear owners and due dates — reviewed weekly.
• Steering committee: decisions made here, not status reports.
• Early escalation: program-level risks escalated before they become issues.
• Change control at program level as well as project level.
• Benefit owner assigned for each benefit — PM tracks, owner delivers.
• Lessons learned at program level shared across all projects.

Anti-Patterns to Avoid

• PMO as an overhead-generating bureaucracy, not a value-adding function.
• Status always green — executive reporting without honest RAG status.
• No dependency management — project managers unaware of cross-project impacts.
• Confusing outputs (delivered features) with outcomes (business value).
• No benefit realization measurement after delivery.

References

• references/program-charter-template.md — program charter template
• references/executive-dashboard-template.md — executive status report format
• references/dependency-log-template.md — cross-project dependency tracking

Expected Output Format

1. Program status report (RAG, milestones, budget, risks, dependencies)
2. Program roadmap (projects, milestones, dependencies visualized)
3. Steering committee pack (decisions needed, risks, updates)
4. Benefit realization tracker (planned vs. actual benefits)