Overview
Strategic Alignment covers eight tasks that turn an organization's strategy into a defined set of portfolio components. You evaluate strategic goals and objectives, identify prioritization criteria, rank strategic priorities with key stakeholders, inventory existing and potential components, build what-if scenarios, recommend a scenario to governance, assess the effect of strategy changes, and create a high-level portfolio roadmap.
The domain exists because a portfolio is only worth managing if it is the right mix of projects, programs and operations for the strategy. Its outputs feed the rest of the exam: Governance approves the scenario and roadmap you recommend, Portfolio Performance balances components against the criteria you defined, Portfolio Risk Management treats strategic misalignment and dependencies as portfolio risks, and Communications Management carries the rationale to stakeholders. At 25%, it shares the top weighting with Portfolio Performance.
How it's tested
Expect long situational stems set in an organization with competing proposals, limited capacity and a strategy that is either unclear or changing. You choose what the portfolio manager should do FIRST or NEXT, or which recommendation BEST fits the stated strategic objectives. Numbers appear, but usually as evidence for a prioritization judgment rather than as a calculation to finish.
-
Criteria before ranking
Stakeholders argue over which proposals matter most. The right move is to agree weighted prioritization criteria tied to strategic objectives before scoring or ranking anything.
-
Strategy has moved
Leadership changes a strategic objective mid-cycle. You assess the impact on every component and the roadmap before recommending changes, rather than cancelling or protecting work on instinct.
-
Scenario recommendation
Several portfolio mixes are compared under a funding or capacity limit. The best answer recommends the scenario with the strongest strategic contribution within constraints and leaves the decision to governance.
Funding drops by 20% and three sponsors each insist their initiative is untouchable. Options include equal cuts, ranking by ROI, or modeling alternative mixes. Look for what is missing: criteria are agreed, so the next step is scenario analysis that tests which combination delivers the most strategic value within the new limit, respecting dependencies, followed by a recommendation to the governance board rather than a unilateral cut.
Tasks 8
Official tasks from the PMI outline, in outline order.
1.1 Evaluate organizational strategic goals and objectivesRead the strategy before shaping the portfolio.
- What it means
- The portfolio manager reviews strategic plans, mission and vision statements and leadership intent through document reviews and interviews, then confirms what the organization is actually trying to achieve and by when.
- What to understand
- Strategy documents are often vague or contradictory, so the output is a clarified, agreed statement of objectives that can be measured. Interviews with executives resolve gaps that documents leave.
- How it shows up
- A new portfolio manager finds proposals piling up and is asked what to do first; confirming current strategic objectives comes before ranking proposals.
- Common confusion
- Treating the budget or the list of pending projects as the strategy, when both should be derived from the objectives.
1.2 Identify prioritization criteriaAgree the yardstick that ranks every component.
- What it means
- You define criteria such as legislative or regulatory mandates, dependencies, ROI, stakeholder expectations and strategic fit, usually with weights, so every proposal is judged the same way.
- What to understand
- Criteria must trace to strategic objectives and be agreed by decision makers before scoring starts. Mandatory items such as legal compliance are often handled as a gate rather than a weighted score, because they cannot be traded away.
- How it shows up
- Two executives push their own projects; the expected answer is to facilitate agreement on objective, weighted criteria rather than rank by sponsor seniority.
- Common confusion
- Using ROI as the only criterion, which ignores mandatory, enabling and strategic-fit work that may have low direct return.
1.3 Rank strategic prioritiesOrder the strategic objectives with key stakeholders.
- What it means
- Working with key stakeholders, you order the strategic priorities themselves using qualitative methods (such as pairwise comparison or expert judgment) and quantitative methods (such as weighted scoring), creating the framework that converts strategy into action.
- What to understand
- Ranking priorities is distinct from ranking components: it fixes the relative weight of objectives such as growth versus cost reduction, which then drives criteria weights and component scores.
- How it shows up
- Leadership says every objective is top priority; the right response is a structured ranking session that forces trade-offs and documents the result.
- Common confusion
- Skipping to scoring individual projects while the objectives they are scored against still have no agreed order.
1.4 Identify existing and potential portfolio componentsBuild the full inventory: running work and new proposals.
- What it means
- You review business plans, proposals, business cases and current project, program and operational records to list every existing component and every candidate for inclusion.
- What to understand
- The inventory must include work already in flight, because it consumes capacity that new proposals compete for. Components can be projects, programs, operations or subsidiary portfolios.
- How it shows up
- A scenario reveals that departments run unregistered initiatives; the right step is to bring them into the inventory before building scenarios.
- Common confusion
- Assuming the portfolio covers only new proposals and that approved, running work is outside its scope.
1.5 Create portfolio scenarios (what-if analysis)Compare alternative portfolio mixes before choosing one.
- What it means
- You assemble alternative combinations of components, score them against the prioritization criteria, and test them with options, risk, SWOT and financial analysis under funding and capacity constraints.
- What to understand
- Scenarios compare whole portfolios, not single projects, so interdependencies matter: dropping an enabling project may make two others undeliverable. A scenario that maximizes value within constraints is often summarized on an efficient frontier.
- How it shows up
- Budget is cut by 15% and the question asks how to decide which work continues; building and comparing what-if scenarios is the expected step.
- Common confusion
- Cutting each component by the same percentage, which preserves no strategic intent and can break dependencies.
1.6 Recommend portfolio scenario(s) and related componentsGive governance a reasoned choice, not a decision already made.
- What it means
- Based on the prioritization analysis, you recommend one or more scenarios and the components they contain, with the rationale, trade-offs and risks that decision makers need.
- What to understand
- The portfolio manager recommends and the governance body decides. A strong recommendation shows strategic contribution, resource fit and what is deferred, so the approval is informed.
- How it shows up
- The portfolio manager has a preferred scenario; the right next action is to present it with rationale to the governance body, not to start the components.
- Common confusion
- Believing the portfolio manager authorizes components directly because they ran the analysis.
1.7 Determine the impact to portfolio and portfolio components due to changes in strategic goalsRe-test alignment when strategy shifts.
- What it means
- When strategic goals or objectives change, you assess how each component and the portfolio as a whole are affected: which still align, which should be changed, accelerated, paused or terminated.
- What to understand
- Impact assessment comes before action. The output is a set of recommendations to governance, and it often triggers rebalancing and roadmap updates in Portfolio Performance.
- How it shows up
- An acquisition or regulatory change alters strategy; the best first step is an impact analysis across components, not immediate cancellation of anything.
- Common confusion
- Keeping a component because it is performing well, even though it no longer supports any current objective.
1.8 Create high level portfolio roadmapSequence components over time with dependencies visible.
- What it means
- With key stakeholders, you build a time-based view of when components start and deliver, using prioritization, interdependency analysis and organizational constraints such as capacity and funding cycles.
- What to understand
- The roadmap communicates sequencing, dependencies and alignment; it is not a detailed schedule. It is a living artifact that Portfolio Performance updates through change analysis.
- How it shows up
- A high-priority component depends on a lower-ranked platform project; the roadmap must sequence the enabler first despite its lower score.
- Common confusion
- Treating the roadmap as an integrated master schedule with task-level dates, which belongs to programs and projects.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Strategic alignment
The degree to which each component and the portfolio as a whole contribute to the organization's stated strategic objectives, not just to local goals.
- Remember
- Alignment is tested continuously; a component can be well managed and still misaligned after a strategy change.
- Tested as
- Most Domain 1 stems ask which action best restores or protects alignment between investment and strategy.
- Trap
- Equating alignment with a project being on time and on budget, which measures delivery, not strategic contribution.
-
Prioritization criteria
The agreed measures, such as strategic fit, ROI, risk, dependencies and regulatory mandate, used to score and compare portfolio components consistently.
- Remember
- Criteria come from strategy and must be agreed by decision makers before any component is scored.
- Tested as
- Expect stems where conflict over priorities is really a symptom of missing or unagreed criteria.
- Trap
- Letting sponsor influence or project size act as an unwritten criterion that overrides the agreed model.
-
Weighted scoring model
Each criterion gets a weight reflecting its strategic importance, each component is scored per criterion, and the weighted sum gives a comparable priority score.
- Remember
- Weights should mirror the ranked strategic priorities, and mandatory components are usually screened in before scoring rather than scored.
- Tested as
- Questions may show a small scoring table and ask which component ranks highest or what changing a weight would do.
- Trap
- Adding raw scores without applying the weights, which silently treats all criteria as equally important.
-
Portfolio component
Any project, program, subsidiary portfolio or operation grouped in the portfolio to achieve strategic objectives.
- Remember
- Operations count as components too, so they compete for the same capacity and funding.
- Tested as
- Used in inventory and scenario questions where running operational work is forgotten.
- Trap
- Assuming only projects and programs belong in the portfolio.
-
What-if scenario analysis
Building alternative portfolio mixes and testing each against criteria, constraints and risk to see which delivers the most strategic value.
- Remember
- Scenarios compare whole portfolios, and dependencies can make a high-scoring component impossible without its enabler.
- Tested as
- The expected response to budget cuts, new mandates or capacity shortfalls.
- Trap
- Evaluating components one by one and summing the winners without testing whether the combination is feasible.
-
Efficient frontier
The set of portfolio mixes that give the highest value for each level of cost or risk; any mix below the curve is dominated by a better option.
- Remember
- A recommended scenario should sit on or near the frontier for the funding level governance can approve.
- Tested as
- Appears in scenario-comparison stems showing value against cost for several mixes.
- Trap
- Choosing the highest-value mix regardless of whether it exceeds the funding constraint.
-
Portfolio roadmap
A high-level, time-based view of the portfolio's components, milestones and dependencies, showing how strategy will be delivered over the planning horizon.
- Remember
- It shows sequence and dependencies at portfolio level; detailed schedules stay with programs and projects.
- Tested as
- Roadmap questions test whether enablers are sequenced first and whether the roadmap is updated after change.
- Trap
- Building the roadmap purely by priority score and ignoring that a lower-ranked enabler must finish first.
-
Interdependency analysis
Mapping how components depend on each other for deliverables, resources, funding or benefits, so sequencing and cancellation decisions account for knock-on effects.
- Remember
- Cancelling or delaying one component can strand the benefits of others.
- Tested as
- Appears in roadmap and scenario stems where the obvious cut breaks a dependency.
- Trap
- Treating each component as independent because each has its own business case.
-
Business case
The documented justification for a component, covering strategic contribution, costs, benefits, risks and options, used as an input to identification and scoring.
- Remember
- A business case is reassessed when strategy or assumptions change; it is not fixed at approval.
- Tested as
- Stems on inventory and impact assessment refer back to the business case to judge continued fit.
- Trap
- Accepting an old business case as proof of alignment after the strategic objective it cites has changed.
-
Recommend vs. decide
The portfolio manager analyzes and recommends; the governance body defined in the governance model approves scenarios, components and roadmaps.
- Remember
- Analysis does not carry authority; authorization comes through governance.
- Tested as
- A frequent distractor has the portfolio manager starting, stopping or funding work directly.
- Trap
- Selecting the answer that acts decisively without the approval step the governance model requires.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Ranking strategic priorities vs. prioritizing components
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Ranking strategic priorities (1.3) | Ordering objectives such as growth, cost reduction or compliance | Sets the relative weight of goals; done with key stakeholders first | Skipping it and arguing over individual projects instead |
| Prioritizing components (1.5 and 3.6) | Scoring projects, programs and operations against weighted criteria | Applies the ranked priorities to specific work | Scoring components before criteria weights reflect agreed priorities |
Portfolio roadmap vs. program roadmap vs. project schedule
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Portfolio roadmap | High-level sequence of components across the portfolio horizon | Shows strategic sequencing and cross-component dependencies | Loading it with task-level dates |
| Program roadmap | Timeline of a program's major stages, components and benefits | Covers one program's related components only | Using it to compare work across unrelated programs |
| Project schedule | Detailed activities, durations and dependencies for one project | Execution-level planning tool owned by the project manager | Expecting the portfolio manager to manage it |
Business case vs. scenario recommendation
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Business case | Justification for one component's investment | Single-component view of value, cost and risk | Approving components one at a time from their cases alone |
| Scenario recommendation | Proposed mix of components with rationale for governance | Whole-portfolio view under shared constraints | Presenting it as a decision rather than a recommendation |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Highest ROI wins
- What candidates pick
- Select the proposal with the best financial return.
- Why it looks right
- ROI is quantitative, objective-sounding and familiar from business cases.
- Why it's wrong
- Strategic fit, regulatory mandates and dependencies are also criteria; a high-return project that serves no current objective lowers alignment.
Clue to watch for The stem states a specific strategic objective, and the high-ROI option does not mention it.
-
Ranking before criteria
- What candidates pick
- Score and rank all pending proposals immediately to clear the backlog.
- Why it looks right
- It produces a visible ordered list and relieves pressure from sponsors.
- Why it's wrong
- Without agreed, weighted criteria the ranking reflects the scorer's opinion and will be challenged by every sponsor whose work drops.
Clue to watch for Executives disagree about what matters most, or no criteria have been documented.
-
Across-the-board cuts
- What candidates pick
- Reduce every component's budget by the same percentage after a funding cut.
- Why it looks right
- It looks fair and spreads the pain evenly.
- Why it's wrong
- Equal cuts ignore priority and can make several components undeliverable; the expected step is what-if scenario analysis to choose which work continues.
Clue to watch for A budget or capacity reduction is announced and options include scenario analysis.
-
Acting on a strategy change at once
- What candidates pick
- Cancel the components linked to the old objective immediately.
- Why it looks right
- It responds quickly and visibly to leadership's new direction.
- Why it's wrong
- Impact must be assessed first; some components may be adapted, and cancelling an enabler can strand benefits elsewhere. The decision belongs to governance.
Clue to watch for The stem announces a new or changed objective and asks what to do FIRST.
-
Portfolio manager authorizes
- What candidates pick
- Start the components in the preferred scenario because the analysis is complete.
- Why it looks right
- The portfolio manager did the work and the result looks clear.
- Why it's wrong
- Task 1.6 is a recommendation; approval comes from decision makers defined in the governance model.
Clue to watch for Options include presenting the scenario and rationale to the governance board or steering committee.
-
Roadmap by score alone
- What candidates pick
- Sequence components strictly from highest to lowest priority score.
- Why it looks right
- It appears to honor the agreed prioritization exactly.
- Why it's wrong
- Interdependencies and constraints can require a lower-ranked enabler to run first, or the top-ranked component cannot deliver.
Clue to watch for The stem mentions a shared platform, prerequisite or dependency between components.
Answer framework
When a Strategic Alignment scenario asks what to do, find the first of these steps that is not yet complete and choose the option that completes it.
- Confirm the current strategic goals and objectives through document review and interviews with leadership, and resolve any gaps or contradictions before going further.
- Agree weighted prioritization criteria with decision makers, tracing each one to an objective and screening mandatory items such as regulatory work separately from scored ones.
- Inventory every existing and proposed component, including operations already consuming capacity, and map the interdependencies between them.
- Build and compare what-if scenarios against the criteria, funding limits and capacity constraints, then recommend the strongest one to governance with its rationale and trade-offs.
- Sequence the approved components on a high-level roadmap that respects dependencies, and reassess impact and alignment across the portfolio whenever strategy changes.
Practice question
Want more like this? The PfMP practice test has questions for every domain.
Checklist
0 of 12
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Study the eight tasks in ECO order, because the order is the logic most questions test: understand the strategy, agree criteria, rank priorities, inventory components, model scenarios, recommend, reassess on change, and roadmap. For each task, note what must already exist before it can start; that habit answers most FIRST and NEXT questions.
Put the most effort into prioritization criteria, weighted scoring and what-if scenarios. Build a small scoring model yourself with five components and four weighted criteria, then change one weight and watch the ranking move. Add a funding cap and a dependency, and see how the best mix changes.
Candidates coming from project roles commonly underestimate task 1.7. Practice stems where a strategy change makes a healthy component a poor fit, and train yourself to assess impact and recommend rather than defend delivery performance. Also review the difference between recommending and deciding, because it carries straight into Governance.
Afterwards, read Governance to see who approves your recommendations, then Portfolio Performance to see how balancing and roadmap updates keep alignment alive during execution. Finish with mixed scenario sets that combine a budget cut with a dependency.
FAQ
How much of the PfMP exam is Strategic Alignment?
PMI weights this domain at 25%, across eight tasks, tied with Portfolio Performance as the largest domains. PMI does not publish a fixed number of questions per domain.
What question style does this domain use?
Mostly long situational stems about competing proposals, constrained funding or a strategy change, asking what the portfolio manager should do first or which recommendation best fits. Calculations, when present, support a prioritization judgment.
Is ROI the main prioritization criterion?
No. ROI is one criterion among several, alongside strategic fit, regulatory mandates, dependencies and stakeholder expectations. The exam rewards answers that weigh criteria agreed from strategy.
What is the difference between ranking strategic priorities and prioritizing components?
Ranking strategic priorities orders the objectives themselves and sets their relative weight. Prioritizing components applies those weights to specific projects, programs and operations.
Who approves the recommended portfolio scenario?
The decision makers defined in the governance model, such as a portfolio governance board or steering committee. The portfolio manager analyzes and recommends.
How long should I study this domain?
Our planning estimate is about 25 to 35 hours, based on its 25% weight and a 120-hour overall plan. Allow more if you have never built a weighted scoring model or compared portfolio scenarios.
How does Strategic Alignment connect to the other domains?
Governance approves what this domain recommends, Portfolio Performance rebalances against its criteria and updates its roadmap, and Portfolio Risk Management treats misalignment and dependencies as portfolio risks.
Other Project Management certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- Program Management Professional Same subject: Domain 1: Strategic Program Alignment (15%)
- PRINCE2 7 Practitioner Study guide
- PMI Risk Management Professional Study guide
- PMI Scheduling Professional Study guide
- Project Management Professional Study guide
- CompTIA Project+ Study guide
- PRINCE2 7 Foundation Study guide
- Certified Associate in Project Management Study guide
- Agile Project Management Study guide
- PMI Agile Certified Practitioner Study guide
- Project Management Professional (PMBOK 7) Study guide
- Disciplined Agile Scrum Master Study guide
Test your Domain 1 knowledge
You have worked through evaluating strategy, agreeing prioritization criteria, comparing what-if scenarios and building a roadmap. Check whether you can choose the right first step when strategy, funding or dependencies change.