Program Management: Definition, Roles & Examples [2026]

A. Togay Koralturk A. Togay Koralturk, Best-Selling PMP Author Last updated on November 09, 2026 12 min read

Four project managers sit around a conference table at a retail chain, and each one reports that their project is on track. Then the chief operating officer asks when customers will actually be able to order online and collect in a store, and nobody in the room can answer. Program management gives that question an owner. This guide explains what program management is, what a program manager does, and how it appears on the PMP® and CAPM® exams.

What is program management?

Program management is the coordinated management of a group of related projects and activities so that an organization obtains benefits it could not get by running them individually. It focuses on the interdependencies among projects, the shared resources they compete for, and the lasting benefits they are meant to produce together.

The PMBOK® Guide makes an important point about size: a program is not simply a very large project. Programs exist to bring about organizational change. A single enormous bridge can be one project, because it has one defined output. A group of smaller efforts can be a program, because together they change how an organization operates.

Consider Riverstone Bank, which wants to move its customers from branches to digital services. It launches separate projects for a new mobile app, a customer identity system, a call center redesign, and staff retraining. The app is of little use if customers cannot verify their identity, and the benefit of lower branch costs appears only after all four are working together. Managing these projects as one program allows Riverstone to sequence them around that benefit.

Not every group of projects needs this structure. An organization should consider a program when the expected benefit depends on several projects succeeding together, when those projects compete for the same scarce people or budget, or when the outcome requires a change in how the business operates. If three projects simply happen to run in the same department and share nothing, the extra layer of governance adds cost without adding value. In that case, they are better handled as separate projects within a portfolio. The UK's Association for Project Management describes programmes in similar terms, with the British spelling.

Project vs. program vs. portfolio

A project is a temporary effort that creates a defined result, a program is a group of related projects managed together for shared benefits, and a portfolio is the collection of programs, projects, and operations through which an organization pursues its strategy. The components of a portfolio do not have to be related to each other, while the components of a program do.

Comparison point Project Program Portfolio
Purpose Create a specific output or result Deliver benefits from related work Achieve strategic objectives
Scope Defined objectives, refined over time The combined scope of its components Organization-wide, tied to strategy
Planning focus Detailed work, using a suitable approach High-level, tracking interdependencies Priorities and resource allocation
Measure of success Value delivered for the effort and expense Benefits collectively realized Strategic value delivered

To see the three levels together, return to Riverstone Bank. The mobile app is a project. The app, the identity system, the call center redesign, and the retraining form the digital banking program. The bank's portfolio contains that program along with unrelated work, such as a regulatory reporting project, a branch maintenance operation, and a commercial lending program. The portfolio managers decide how much money and talent each of these receives.

Ready to take the next step in project management?

200,000+ Professionals Taught by Our Instructors

What does a program manager do?

A program manager leads a group of related projects toward a shared set of benefits and answers for how well those projects work together. The role sits above the individual project managers and reports to a sponsor or a steering group, so its work happens mostly at the boundaries between projects.

The main responsibilities include the following:

  • Defining the program roadmap. The program manager decides which projects are needed and in what order.
  • Managing interdependencies. When one project's output is another project's input, the program manager protects that handoff.
  • Allocating shared resources. Scarce specialists, test environments, and budgets are balanced across the projects.
  • Handling cross-project risks and issues. Problems that a single project manager cannot resolve are settled at this level.
  • Engaging senior stakeholders. The program manager keeps sponsors and business leaders aligned on priorities.
  • Tracking benefits. The program manager checks whether the expected improvements are actually appearing.

Note that the job title varies. In technology companies, a "program manager" or "technical program manager" sometimes manages a single complex product area with no formal group of projects. The description above reflects how PMI and most large organizations use the term.

Program manager vs. project manager

A project manager is accountable for delivering one project's outputs within its agreed scope, schedule, and budget, while a program manager is accountable for the combined benefits of several related projects. Project managers usually report progress to the program manager when their projects belong to a program.

Comparison point Project manager Program manager
Accountable for Outputs of one project Benefits across related projects
Time horizon The project's defined duration Often several years, until benefits are established
Handling of change Controls changes to protect the baselines Adjusts the mix of projects to protect the benefits
Main concern Delivering the work well Making sure the work adds up to the intended change

The difference becomes clear when a project is threatened. Suppose the Riverstone identity project falls six weeks behind. Its project manager analyzes the cause and proposes a recovery plan within that project. The program manager asks a wider question: because the app cannot launch without the identity system, should the app team reassign its testers, should the launch move, or should the retraining be postponed so that staff are not trained too early?

The program management life cycle

The program management life cycle usually has three phases: definition, delivery, and closure. In the definition phase, the program is justified and planned. In the delivery phase, the component projects run and the benefits begin to appear. In the closure phase, the remaining benefits and any continuing work are handed over to the business.

  1. Program definition. The organization confirms the business case, the vision, and the expected benefits, appoints the program manager and the governance board, and drafts the roadmap of component projects.
  2. Program delivery. Projects are started, coordinated, and completed according to the roadmap. New projects may be added and others stopped as the organization learns what is working.
  3. Program closure. The program confirms that the benefits have been achieved or transferred, hands ongoing responsibility to operations, and captures lessons learned.

The delivery phase is what most distinguishes a program from a project. A project is expected to follow its plan, whereas a program may deliberately change its components midway. If early data shows that Riverstone's customers prefer video support, the program can cancel part of the call center redesign and start a new video service project.

Program governance and benefits realization

Program governance is the structure of roles, boards, and decision rules through which a program is authorized and overseen. Benefits realization is the work of making sure that the outputs of the program produce the measurable improvements that justified it.

A program board or steering group usually includes the sponsor, senior business leaders, and the program manager. It approves the roadmap, releases funding in stages, and rules on issues that exceed the program manager's authority.

Benefits need owners and measures, because many of them appear only after the projects have finished. Riverstone's benefit of "lower branch costs" might be defined as a 15% reduction in branch transactions within 18 months of the launch, measured quarterly and owned by the head of retail banking. Without that definition, the program could close successfully on paper while the expected savings never arrive.

What is a program management plan?

A program management plan sets out how a program will be run and how its component projects fit together. Compared with a project management plan, it stays at a higher level and leaves the detailed scope, schedule, and budget to each component project.

A typical program management plan covers the following:

  • The program's vision, objectives, and expected benefits.
  • The roadmap, showing the component projects and their major dependencies.
  • The governance structure and the decision rights of each role.
  • The approach to shared resources and funding.
  • The approach to program-level risks and issues.
  • The stakeholder engagement and communication approach.
  • The method for measuring and reporting benefits.

The roadmap is usually the most used section. At Riverstone, a single page showing the four projects and the dates when each depends on another gives the steering group a clear picture of what a delay would affect.

Program management examples

Program management is used wherever several related projects must combine to produce a lasting change. The table below shows typical examples from different industries.

Program example Typical component projects Intended benefit
Digital banking transformation Mobile app, identity system, call center redesign, staff retraining Lower branch costs and higher customer satisfaction
City light rail network Track construction, station building, vehicle procurement, signaling, public communications Shorter commutes and less road traffic
Hospital records modernization Records software, data migration, device integration, clinician training Fewer medical errors and faster care
New aircraft development Airframe, engines, avionics, certification, production line A marketable aircraft with lower operating costs
Agile release train Several agile teams delivering features to one product on a shared cadence Faster and better coordinated product delivery

The last row shows how the idea applies to agile organizations. In the Scaled Agile Framework, an agile release train coordinates many teams around one value stream, which plays a role similar to a program.

Program management skills

The most valuable program management skills are strategic thinking, stakeholder management, and the ability to lead through influence. A program manager rarely directs the work personally, so results depend on aligning people who report to someone else.

Other important skills include the following:

  • Dependency and systems thinking. Seeing how a change in one project affects the others.
  • Financial and benefits analysis. Building a business case and measuring whether the benefits were achieved.
  • Negotiation and conflict resolution. Settling competing demands for people and money.
  • Risk management at scale. Identifying risks that arise only from the interaction of several projects.
  • Executive communication. Reducing complex situations to the decisions senior leaders need to make.

To illustrate, two project managers at Riverstone both claim the same security architect for the same month. The program manager needs to understand which project sits on the path to the benefit, explain the trade-off to both teams, and secure agreement without damaging either working relationship.

How to become a program manager

Most program managers begin as project managers, then take on larger or multi-team projects before leading a program. The usual path combines several years of project delivery experience with growing exposure to budgets, senior stakeholders, and business strategy.

PMI offers a credential for this level called the Program Management Professional (PgMP)®, which is aimed at experienced practitioners who coordinate multiple related projects. The Project Management Professional (PMP)® certification, by contrast, focuses on leading projects. For most people, the PMP comes first, because it is far more widely requested by employers and it builds the foundation that program work requires. If you are still building that foundation, our Complete Project Management Course covers the discipline from the beginning.

Program Management on the PMP® and CAPM® Exams

In the PMP® exam, program management usually appears as the context of a scenario. You are the project manager of one component, and something crosses the boundary of your project: a shared specialist is double-booked, another project's delay affects your start date, or a decision that helps your project harms a sibling project. If a question describes a conflict between projects in the same program, consider who has the authority to resolve it. Note that the project manager assesses the impact and raises the issue with the program manager, instead of settling it alone or going straight to the executives. Common distractors optimize one project at the expense of the program or handle a cross-project decision through a single project's change control.

The CAPM® exam tests the same ideas in its fundamentals and core concepts domain, which carries 36% of the questions. CAPM questions are also situational, with no definition questions, and the scenarios are simply shorter. Our best-selling PMP Complete Study Guide, the most complete study guide on the market, explains how projects, programs, and portfolios relate the way the exam tests them, and our CAPM Complete Study Guide does the same for entry-level candidates.

PMP Practice Question: Program Management

A project manager leads the billing system replacement, one of four projects in a program to consolidate a utility company's customer platforms. The project is ahead of schedule. The shared test laboratory is booked on a first-come basis, and the project manager could reserve the next six weeks. Doing so would finish billing three weeks early but would delay the customer records project, which also needs the laboratory, by four weeks. The program's benefits case states that the savings begin only when billing and customer records are running together. The billing project's sponsor encourages the project manager to reserve the laboratory immediately.

What should the project manager do next?

a) Reserve the laboratory for the six weeks, since the booking rules allow it and the billing project's sponsor supports finishing early.

b) Ask the portfolio steering committee to rank the billing and customer records projects so that the laboratory can be assigned to the higher-priority one.

c) Submit a change request with an impact assessment to the billing project's change control board to approve the early finish and the laboratory booking.

d) Raise the laboratory conflict with the program manager, together with its impact on both projects and on the program's benefits.

Correct answer: D.

Rationale: The decisive fact is in the benefits case: the savings begin only when both systems are running together. An early billing finish therefore creates no benefit, while a four-week delay to customer records postpones the savings for the whole program. The decision crosses project boundaries, so it belongs with the program manager, and option d) gives that person the information needed to make it. Option a) is the instinct of a project manager measured only on a single project, and the sponsor's encouragement and the booking rules make it feel legitimate. It improves one schedule while harming the outcome that justified the work. Option b) escalates too far, because a portfolio committee ranks competing investments, and these two projects are parts of the same program with a program manager in place to settle exactly this type of issue. Option c) borrows the correct remedy from a scope change on a single project. The billing project's board has no authority over the customer records schedule, so it cannot make this decision. For full-length, realistic, scenario-based practice with detailed explanations, built to train the PMI® mindset, take our PMP practice exams or, at the entry level, our CAPM practice exams.

Ready to take the next step in project management?

200,000+ Professionals Taught by Our Instructors

Frequently asked questions

What is the difference between program management and project management?

Project management delivers the outputs of one temporary project within an agreed scope, schedule, and budget. Program management coordinates several related projects so that together they produce lasting benefits for the organization.

What is an example of program management?

A bank moving customers to digital services might run a mobile app project, an identity system project, a call center redesign, and staff retraining as one program. Each project has its own manager, and the program manager makes sure that they combine to produce the expected savings.

Who gets paid more, a project manager or a program manager?

Program managers usually earn more, because the role is more senior and carries responsibility for several projects and their business results. Actual pay depends on the industry, location, and experience, and technology companies often use the title differently.

Which is better, PMP or PgMP?

They serve different career stages. The PMP certifies experience leading projects and is widely requested by employers, while the PgMP is aimed at experienced professionals who coordinate multiple related projects. Most people earn the PMP first.

What is agile program management?

Agile program management coordinates several agile teams working toward shared outcomes, using short planning cycles, frequent integration, and regular adjustment of priorities. Frameworks such as the Scaled Agile Framework organize this work through groups of teams that plan and deliver on a shared cadence.

What is a program management office?

A program management office is a team that supports a program with shared standards, reporting, resource coordination, and governance. It differs from a project management office that serves the wider organization, because it exists to support one specific program.

Is program management on the PMP exam?

Yes, usually as the context of a scenario. The PMP exam expects a project manager in a program to assess the impact of cross-project issues and raise them with the program manager, instead of optimizing a single project at the expense of the program.

Is program management on the CAPM exam?

Yes. The CAPM exam tests program management within its fundamentals and core concepts domain, which carries 36% of the questions. Expect short scenarios about how projects, programs, and portfolios relate and who makes decisions at each level.

Three colleagues review regulatory documents at a conference table during a project planning meeting.

Enterprise Environmental Factors (EEFs): Examples [2026]

A. Togay Koralturk November 17, 2026 11 min read

What enterprise environmental factors (EEFs) are, with internal and external examples, EEF vs OPA, how to identify them, and how the PMP exam tests them.

Three team members from different departments plan project work together at an office whiteboard.

Matrix Organizational Structure: Types & Examples [2026]

A. Togay Koralturk November 17, 2026 13 min read

What a matrix organizational structure is, how weak, balanced, and strong matrix types differ, an example, pros and cons, and functional vs projectized.

A project manager stands and presents a decision to three members of a project steering committee at a meeting table.

Project Governance: Framework, Roles & Examples [2026]

A. Togay Koralturk November 13, 2026 12 min read

What project governance is, how a governance framework and structure work, the roles involved, real examples, a template, and how the PMP exam tests it.

About the Author

A. Togay Koralturk is a globally recognized pioneer and educator in project management and sustainable design and construction, a best-selling author, and an entrepreneur. His publications have reached hundreds of thousands of professionals worldwide and have been extensively adopted as primary course material in universities throughout the United States. Holding a bachelor’s degree in civil engineering and a master’s degree in construction management from the University of Southern California, he has played a pivotal role in leading numerous construction projects ranging from $100 million to $500 million worldwide, and he has educated thousands of professionals. Continuing his professional journey, he founded Projeric and Projectific, where he serves as the instructor and CEO.