September 7, 2026 · 6 min read
TL;DR: 59 question stems in the bank place your project inside a programme or portfolio. When that context appears, the keyed answer is nearly always lateral: agree the sequence with the peer project, trace the programme's new direction through your own deliverables, check the alignment your product owner never made. Escalating the same problem upward appears 34 times among the wrong answers.
Most candidates read "programme manager" in a stem as a cue that someone senior is now available to decide. The bank reads it as a cue that you now have peers, and peers are who you have to go and talk to.
Trace the change through to your own deliverables before changing anything. A programme shift is an input to analysis, not an instruction.
A bank's payments modernisation programme shifts towards instant payments and the programme manager tells the project manager of the card-issuing project that objectives have moved. Four options: carry on because the original objectives were approved, realign the project's objectives straight away, work out which deliverables still serve the programme under its new direction, or pause until the programme settles.
The keyed answer is the third, and the explanation is worth quoting in substance: a project inside a programme earns its place by contributing to the programme's goals, so a shift in those goals has to be traced through to this project's scope and deliverables before anything is changed. The other three each substitute a reflex for that assessment. Holding to approved objectives is a reflex. Realigning immediately is also a reflex, just a more obedient one. Pausing is the reflex candidates reach for when they want to avoid being wrong.
That is the pattern for the whole vein. A programme change is an input to analysis, not an instruction.
The project managers do, between them. This is the most consistent pattern in the vein, and the one where candidates most often reach for the sponsor instead.
A self-storage operator is releasing a self-service move-in flow to 60 branches in three-week increments. The same branch teams take a new card and till platform live next month and move onto a new rota system a fortnight later. The increment is ready, and on the current cadence it lands in the same fortnight as the till platform.
| Option | Verdict | Why |
|---|---|---|
| Release now, slow later increments | Distractor | Puts the counter change in the same fortnight anyway |
| Ask the sponsor to hold the other programmes back | Distractor | Hands upward a conflict three project managers can settle |
| Add a branch-readiness check to the definition of done | Distractor | Records that branches are not ready without changing why |
| Agree a release date with the till and rota programmes | Keyed | Acts on the real constraint, and no one project can decide it alone |
Nothing is wrong with the increment except when it arrives. One team can absorb only so much new routine at once, and the fix is a conversation between three project managers about sequence.
Common trap: treating a programme manager or portfolio owner in the stem as an escalation target. Across the 34 distractor options in this vein, a large share are exactly that move: ask the programme sponsor to reorder the backlog, ask the sponsor to escalate to the executive committee, ask the PMO to estimate across all the programme's projects and issue the plan. The bank flags these by name in its explanations as outsourcing a decision the project manager is positioned to make. The presence of a hierarchy above you is not permission to use it.
One item is a clean diagnostic. An efficient agile team generates its own ideas, puts them in the product backlog, builds and tests them, and on completion the portfolio owner rejects all of them. Why?
The keyed answer is that the product owner never aligned the ideas with the portfolio owner. Not intellectual property, not unwillingness to pay, not a skipped quality step. Everything entering the backlog passes through the product owner, so a wholesale rejection at the end points to that alignment never having been taken upward for agreement.
Note what this does and does not say. Upward alignment is a real obligation. It just belongs to the product owner, as an ongoing thing, before the work happens, rather than to the project manager as an escalation after it fails.
What does the PMP exam expect when the programme changes direction? Trace the change through to your own deliverables before changing anything. The bank keys working out which deliverables still serve the programme, and offers both realigning immediately and pausing until things settle as distractors.
Should I escalate a conflict with another project in the same programme? Usually not. The bank repeatedly keys agreeing directly with the peer project managers and offers asking the sponsor to hold the other projects back as the distractor, because it hands upward a conflict three project managers can settle between them.
How often does the bank use a programme or portfolio context? 59 question stems mention a programme, programme manager, or portfolio, spread across all three domains: 32 People, 22 Business Environment, 18 Process.
Does this change under the 2026 ECO? The weighting does. Business Environment moved from 8% to 26% in July 2026, and this vein sits heavily in it under governance and organisational change tasks, so cross-project coordination scenarios are worth more marks now than they were on the retired exam.
PMP Practice's 2,141 questions are certified against PMBOK 8 and the July 2026 ECO, with every wrong answer explained rather than just marked wrong. Start the free 20-question sample — no card, no signup required to try it.
Related reading: The Escalation Ladder: 27 Keyed Answers, 227 Distractors and Project Governance: Who Decides What, and Where Your Authority Ends. The domain itself is mapped on the Business Environment study page.
What does the PMP exam expect when the programme changes direction?
Trace the change through to your own deliverables before changing anything. The bank keys working out which deliverables still serve the programme, and offers both realigning immediately and pausing until things settle as distractors.
Should I escalate a conflict with another project in the same programme?
Usually not. The bank repeatedly keys agreeing directly with the peer project managers and offers asking the sponsor to hold the other projects back as the distractor, because it hands upward a conflict three project managers can settle between them.
How often does the bank use a programme or portfolio context?
59 question stems mention a programme, programme manager, or portfolio, spread across all three domains: 32 People, 22 Business Environment, 18 Process.