- Why Domain 2 Carries Nearly Half the Exam
- The Four Phases of the Program Life Cycle
- Program Formulation and the Business Case
- Program Planning Deep Dive
- Executing and Delivering Components
- Program Closure Mechanics
- How PgMP Questions Test This Domain
- Scheduling Domain 2 in Your Prep Plan
- Common Mistakes Candidates Make
- FAQ
- Program Life Cycle Management is 44% of the PgMP exam - roughly twice any other domain.
- The domain spans formulation, planning, execution, and closure across the full program life cycle.
- The exam has 170 questions (150 scored, 20 unscored) in 240 minutes, administered via Pearson VUE.
- Expect scenario questions that require sequencing decisions across multiple components, not recall of definitions.
Why Domain 2 Carries Nearly Half the Exam
If you only had time to master one domain before sitting for the PgMP, it would have to be this one. Program Life Cycle Management makes up 44% of the exam content outline - more than Strategic Program Alignment (15%), Benefits Alignment (11%), Stakeholder Engagement (16%), and Governance (14%) combined come close to matching on their own. That weighting isn't arbitrary; it reflects how PMI defines the actual work of a program manager: moving a program through formulation, planning, execution, and closure while coordinating multiple, interdependent projects and operational work.
If you haven't yet reviewed how this domain fits alongside the other four, start with our complete guide to all five PgMP content areas before drilling into this one. This article assumes you already understand the exam's overall structure and want a focused breakdown of the life cycle domain specifically.
The Four Phases of the Program Life Cycle
PMI's program-management lexicon (aligned with the fifth-edition standard referenced in the March 2024 exam content outline) organizes the program life cycle into four phases. Each phase generates its own exam questions, and PMI expects candidates to recognize which phase a scenario belongs to before selecting an answer.
- Program Formulation: Defining the program, building the business case, and securing initial authorization.
- Program Planning: Developing the program management plan, roadmap, and supporting subsidiary plans across components.
- Program Execution (Delivery/Component Management): Authorizing, integrating, and overseeing the projects and operational activities that produce program benefits.
- Program Closure: Formally closing the program, transitioning benefits to operations, and releasing resources.
Exam scenarios rarely name the phase outright - you'll need to infer it from context clues like "the sponsor has just approved the charter" (formulation) or "three components are underway and a fourth is being planned" (execution).
Program Life Cycle Management
Candidates must understand how work flows across phases and how decisions in one phase constrain options in the next.
- Sequencing dependencies between component projects
- Transition criteria between life cycle phases
- Integration of planning artifacts across multiple components
- Closure activities distinct from individual project closure
Program Formulation and the Business Case
Formulation is where a program's purpose gets translated into an actionable mandate. This subdomain tests whether you understand the difference between a program charter and a project charter, and whether you can identify when a program should be formally initiated versus when the work should stay at the project level.
Key concepts to master:
- Program business case development and its link to organizational strategy
- Program charter content and sponsor authorization
- Feasibility studies and environmental assessments used to justify the program
- Program mandate and how it differs from a single-project mandate
Questions in this area often present a partially-completed formulation scenario and ask what should happen next - a classic PgMP pattern of testing sequencing knowledge rather than terminology recall.
Program Planning Deep Dive
Planning is the densest part of Domain 2 because it touches nearly every knowledge area a program manager coordinates - scope, schedule, cost, quality, resources, risk, and communications - but at the program level rather than the project level. The exam wants you to distinguish integrated program planning from simply aggregating individual project plans.
- Program roadmap development and how it differs from a project schedule
- Program management plan components and subsidiary plans
- Resource planning across multiple concurrent components
- Risk identification at the program level, including risks that emerge only from component interdependencies
- Financial planning and program-level budgeting
Key Takeaway
When a scenario question describes a risk or issue that only exists because two or more components interact, treat it as a program-level planning question - not a project-level one. This is one of the clearest signals PMI uses to test program thinking.
Executing and Delivering Components
This is the operational heart of the domain. Program execution covers authorizing and overseeing component projects, integrating their outputs, and managing the transition of deliverables into benefits. Expect heavy coverage of:
- Component initiation, authorization, and prioritization
- Integration of component-level status into program-level reporting
- Managing shared resources and resolving cross-component conflicts
- Program-level change control and configuration management
- Monitoring program performance against the roadmap and business case
Because execution activities repeat throughout a program's life, this subdomain tends to generate the highest volume of exam questions within Domain 2. Many candidates underestimate how much of the exam is really about integration and oversight rather than execution mechanics themselves.
Program Closure Mechanics
Closure is smaller in question volume than planning or execution but is frequently missed because candidates default to project-closure thinking. Program closure includes:
- Confirming all components have been closed or transitioned
- Validating that benefits have been realized or transferred to operations for ongoing tracking
- Releasing program resources and archiving program documentation
- Conducting a final program review against the original business case
Note the connection to Benefits Alignment here - closure isn't just administrative wrap-up, it's the point where you confirm benefits have actually landed. If this distinction feels unfamiliar, review the Benefits Alignment domain guide for the full benefits-realization lifecycle.
How PgMP Questions Test This Domain
The PgMP exam consists of 170 multiple-choice questions - 150 scored and 20 unscored - administered over 240 minutes through Pearson VUE, either at a test center or via OnVUE online proctoring. You won't know which questions are unscored, so every item deserves full attention.
Domain 2 questions are almost always scenario-based. A typical stem describes a program with several components at different stages, then asks what the program manager should do next, which document should be updated, or which stakeholder should be consulted first. There is rarely a single "textbook" fact being tested - instead, PMI is checking whether you can apply life cycle logic to a messy, realistic situation.
| Domain 2 Subarea | Typical Question Focus |
|---|---|
| Formulation | Business case, charter authorization, initial mandate |
| Planning | Roadmap, integrated plans, cross-component risk |
| Execution | Component oversight, integration, change control |
| Closure | Benefits confirmation, resource release, final review |
For a broader sense of how difficult these scenario questions feel in practice compared to the PMP exam, see our full difficulty breakdown.
Scheduling Domain 2 in Your Prep Plan
Because this domain is worth roughly three times as much as Benefits Alignment and nearly three times Strategic Program Alignment, it deserves proportionally more calendar time - not just more attention on exam day. A practical approach is to dedicate the largest block of your preparation weeks to Domain 2, revisiting it repeatedly rather than covering it once and moving on.
Formulation and Planning Foundations
- Map out the four life cycle phases and transition criteria
- Study program charter vs. project charter differences
- Work through integrated planning scenarios across components
Execution and Integration
- Practice component authorization and prioritization scenarios
- Review program-level change control processes
- Drill cross-component risk and resource-conflict questions
Closure and Full-Domain Review
- Study benefits confirmation and transition-to-operations steps
- Take mixed practice sets combining all four phases
- Revisit any subarea scoring below your target threshold
This is one of the few places where generic study techniques - spaced repetition of scenario questions, timed review blocks - genuinely pay off, precisely because Domain 2's volume means you'll encounter the same phase-transition logic repeatedly under different scenario dressing. For a full week-by-week plan covering all five domains together, see our complete PgMP study guide.
Common Mistakes Candidates Make
- Treating program planning as project planning at scale. The exam rewards integration thinking, not aggregation.
- Missing phase-transition cues. Scenarios signal phase changes through context, not labels - practice spotting them.
- Underweighting closure. It's a smaller subarea but still costs points when confused with project closure.
- Ignoring the connection to other domains. Life cycle decisions constantly intersect with Stakeholder Engagement and Strategic Program Alignment - questions often blend two domains in one scenario.
Before scheduling your exam, also confirm you meet PMI's eligibility pathway - either a secondary diploma with 48 months of program management experience (or PMP certification held within the past 15 years plus 84 months of program management experience), a bachelor's degree with 48 months, or a GAC-accredited bachelor's degree with 36 months, all within PMI's specified experience windows - and that you've budgeted for the $800 member / $1,000 nonmember exam fee. Full pricing details, including the panel review process, are covered in our PgMP certification cost breakdown. You can also run full-length practice tests that mirror the 170-question, 240-minute format before committing to a test date.
Frequently Asked Questions
PMI's exam content outline reflects the actual proportion of a program manager's responsibilities. Moving a program through formulation, planning, execution, and closure - while integrating multiple components - is considered the core, ongoing work of the role, so it dominates the scored content.
It isn't necessarily conceptually harder, but its sheer volume and scenario complexity make it feel more demanding. Because it spans four distinct phases, there's simply more material to internalize compared to narrower domains like Benefits Alignment.
The exam has 150 scored questions plus 20 unscored ones, for 170 total. Since Domain 2 represents 44% of the content outline, it accounts for the largest single share of those scored items.
Not necessarily. PMI offers multiple eligibility pathways, including one based on PMP certification held within the past 15 years combined with 84 months of program management experience, and others based on education level combined with direct program management experience.
See our companion guides on Strategic Program Alignment, Benefits Alignment, and Stakeholder Engagement, or start from the full domain overview for context on how all five areas fit together.