PMP® 2026

Complete Domain Deep Dive

All three domains · all 26 ECO tasks · 100+ practice questions with full solutions

Part I — People · 8 tasks · 33% of the exam

Part II — Process · 10 tasks · 41% of the exam

Part III — Business Environment · 8 tasks · 26% of the exam

Aligned to the July 2026 Exam Content Outline

If You Only Have Ten Minutes

Ten rules that cut across all three domains. Every one decided a real question in testing. Read this page before anything else; it is the fastest path to the highest-value patterns in the full document.

1. Ask what each option requires to already exist

The single highest-yield check on the exam. If an option depends on something that has not happened yet — an agreement, an approval, a completed analysis — it is not the answer, however sound it is as an eventual action.

2. Facilitate, do not adjudicate, do not escalate

When two or more parties hold conflicting expectations, bring them together and produce one agreed position. Options that pick a side, ask someone else to pick, or preserve both positions separately all lose to genuine facilitation.

3. Compliance, safety, and ethics always outrank schedule and cost

This includes sponsor pressure, client pressure, and "low probability of getting caught." There are no exceptions to this in the material tested.

4. Report the truth, then the plan

Accurate status plus a corrective action beats concealment, delay, cherry-picked data, or overreacting. Never let bad news reach a stakeholder from anyone other than you.

5. Match the literal verb in the stem

If the stem asks to align or resolve, an option that only analyses or clarifies is not enough — it has to produce agreement. If the stem asks for something structured or systematic, test every option against that specific word.

6. Read every option to its final word

Qualifiers at the end of an option are frequently the whole discriminator: *with no cost ceiling · in the next release · informally · without approval · regardless of.* A sound-looking option can be disqualified by its last clause.

7. Explicit knowledge lives in documents; tacit knowledge lives in people

Numbers, costs, and historical data belong in repositories. Judgement, context, and "how to handle this" belong in conversation, pairing, and mentoring. Do not ask a person for figures they cannot reliably recall, and do not expect a document to carry nuance.

8. Know your authority boundary

You facilitate, analyse, recommend, and enforce agreements. You do not personally decide a change request’s outcome, delegate a delivery-approach decision to the sponsor, or step into a conversation that belongs to another function (a vendor’s finances, a technical fix that is the team’s job).

9. Vague framework language is a warning, not an invitation

"Strategic framework," "comprehensive methodology," and similar phrasing with no named mechanism should be read literally, not filled in with the strongest technique you can imagine. If it does not name what it actually does, it usually is not the answer.

10. When two options both look right, prefer the one that changes something

Document, store, monitor, and inform are frequently real but incomplete actions — they stop one step short of resolving, deciding, or updating the artifact that governs the situation. Prefer the option that actually moves something.

PMP® 2026

People Domain Precision Guide

Target → Above Target · aligned to the July 2026 ECO

Part 1 — The Discriminator Library: fourteen validated close-call rules

Part 2 — Task-by-task precision reference, all eight People tasks

Part 3 — Mixed discrimination drill

Appendix — Rapid reference and answer-selection sequence

40 original practice questions with full option-by-option solutions

PMP 2026 — People Domain Precision Guide

Built from: the July 2026 Exam Content Outline, a large body of practice items worked under timed conditions, and the official solution rationales for each. Supporting concepts drawn from the PMBOK Guide and the Agile Practice Guide.

Why this document leads with discriminators

Most People-domain material teaches the concepts and stops. That is rarely where marks are actually lost. Candidates who understand servant leadership, conflict modes, and stakeholder analysis still miss items — because on the questions that decide a passing band, two options are both defensible and only one is correct.

Target-to-Above-Target in this domain is a precision problem rather than a knowledge problem. The discriminator is usually a single word in the stem or a trailing qualifier in an option, not a concept you have never met.

So this document leads with the discriminators — the specific rules that decide close calls, every one validated against an official exam-style rationale rather than inferred from principle. The task-by-task reference follows, and the practice items are written at the difficulty where the discrimination actually matters.

Where the questions concentrate

Tasks that moved in the 2026 outline

Two People tasks that existed separately under the 2021 outline have been absorbed elsewhere. If you studied from older material, check these:

Both are covered here, because material that has been renamed or relocated is exactly where stale preparation leaves gaps.

A caution worth carrying

A consistent, one-directional bias shows up in wrong answers across this domain: a preference for the softer, more consultative, more human-facing option over the procedural, artifact-based, or requirement-holding one. PMI is collaborative, but it is not indiscriminately accommodating.

PART 1 — The Discriminator Library

Fourteen rules, each derived from an official exam-style rationale. These are what decide the close calls. Where a rule quotes a rationale directly, that wording is worth memorising, because it is the language the exam itself reasons in.

1. Facilitate beats adjudicate beats escalate

When two or more parties hold conflicting expectations, the correct action is to bring them together and reconcile the difference collaboratively. Not to decide between them. Not to hand the decision upward.

Note both critiques of escalation. It is not merely premature in sequence — it is framed as abdication of a role that belongs to you, and as damage to your own standing with the stakeholders you will still need to manage afterwards.

2. Engaging one party is not alignment

An option that works with only one side of a two-sided disagreement is wrong even when the action it proposes is reasonable. Adjusting a sponsor's expectations is a fine activity; doing it without the team in the room is not.

3. Clarify, document, and record are not the same as resolve

Options whose verb is understand, clarify, gather, document, record stop short of producing agreement. If the stem asks for alignment, resolution, or a decision, those verbs cannot get you there.

That last critique is the sharpest. Documentation as a substitute for engagement is treated not as an incomplete step but as a leadership failure — the project manager stepping back from the role rather than performing it.

4. Organising and clarifying do not deliver outcomes

A close relative of the previous rule, but distinct enough to separate. Role clarity, categorisation, and structural definition are enablers. They do not themselves produce alignment between outcomes and expectations.

This is the rule that catches vocabulary-matching. An option can echo the stem's exact language — internal and external stakeholders — and still be wrong, because matching words is not the same as accomplishing the objective.

5. Match the source to the knowledge type

Quantifiable information lives in records. Experiential judgement lives in people. Asking a person to recall budget figures is as much a mismatch as asking a document to convey nuance.

6. Accommodating a stakeholder preference is not automatically correct

This is the single most counterintuitive rule in the domain, and the one most likely to cost you an Above-Target item. Tailoring communication to stakeholder needs is a real ECO enabler — but it applies to method, not to whether the project's requirements hold.

The discriminator is whether the stakeholder is expressing a constraint or a judgement about value. Constraints get accommodated. "I don't see why this matters" gets addressed, because that is an ADKAR awareness gap, and awareness gaps are closed by communicating rationale.

7. Systematic analysis beats the individual conversation when a position has changed

Direct engagement wins when you need to understand a person's concern. Formal stakeholder analysis wins when you need to understand how a changed position affects the whole picture.

The trigger word is comparative. If the stem tells you someone's influence, authority, or category has shifted — particularly if it now touches funding or approval — the question is about their standing relative to everyone else, and only a systematic reassessment answers that.

8. Scale must match the problem

A technique that works one relationship at a time cannot solve a systemic, multi-site, or multi-region problem.

When a stem specifies breadth — all locations, multiple countries, every franchise, across departments — an option that operates person-by-person is disqualified by arithmetic, regardless of how sound it is in isolation.

9. Storage is not distribution

Getting knowledge into a repository is necessary but not sufficient. Someone still has to receive it.

This is a genuine refinement of everything the Business Environment work established about repositories. There, "add it to the organisational repository" was repeatedly the correct answer — because the task was capturing an innovation for reuse. Here the task is transferring knowledge to people, and passive availability fails it. Read which job the stem is asking you to do.

10. Verify the assumption before designing the intervention

When a stem reports what someone believes, that belief is data about the believer, not established fact about the situation.

Experienced members believing that new members lack skills is an assumption. Any option that acts on it — incentivising mentors, reassigning the newcomers — inherits the assumption unchecked. Note that a supportive-sounding option is not exempt: offering bonuses to mentors was rejected because it "ignores the skills of the newer team members," the same flaw as the punitive option.

11. Diagnose the ADKAR stage from what people actually say

Carried over from the Business Environment work and confirmed again in People contexts. The quoted words in the stem tell you which stage is missing, and prescribing the wrong intervention is the trap.

12. Diagnose conflict severity before deciding whether to act at all

Speed Leas' five levels are the diagnostic layer; the five conflict-resolution modes are the response layer. Most treatments teach only the second.

13. Anticipated tension calls for a preventive artifact, not a disciplinary one

When a stem is anticipatory — tension may arise, the deadline is tight — the answer is the collaborative instrument that sets expectations in advance. Not the organisation's handbook, not performance assessments.

The trap type here is worth naming on its own: a legitimate tool at the wrong scope. The handbook is real and useful; it is organisation-wide where the problem is team-specific. Performance assessments are real; they measure competency where the problem is behaviour.

14. Artificial intelligence complements, it does not replace

This appeared twice in the source material with nearly identical framing, across two different tasks. Given AI is a named driver of the 2026 update, treat the repetition as deliberate.

AI fits explicit-knowledge and efficiency problems: transcription, documentation, sentiment analysis, personalising message format. It does not fix trust, resistance, or tacit knowledge transfer. If an option proposes a tool as the answer to a relationship problem, that is the trap.

PART 2 — Task-by-Task Precision Reference

All eight tasks, with the granular detail that separates Target from Above Target. Four practice items per task, written at the difficulty where discrimination matters. Answer all four before reading any solution.

People Task 1 — Develop a Common Vision

Note for anyone studying from older material: this is where the 2021 outline’s “Build shared understanding” task now lives.

ECO enablers

• Help ensure a shared vision with key stakeholders.
• Promote the shared vision.
• Keep the vision current.
• Break down situations to identify the root cause of a misunderstanding of the vision.

Who owns the vision

This is a predictive-instinct trap. A project charter feels like the project manager's artifact, so the vision statement feels like it should be too. In agile it is not. The role split you already know — product owner owns what and why, the team owns how, the scrum master removes impediments — extends to vision ownership.

What a vision statement contains

A concise, compelling description of purpose, goals, and value. Expanded templates cover: project name, purpose, target audience, benefits, unique differentiators, and long-term impact. Recognise these if presented; do not spend memorisation effort on the field list.

The 2026 outline ties vision to its reframed definition of success — value worth the effort and expense. A vision expressed purely as scope, schedule, and budget is incomplete; it should express outcome and value.

Techniques for building and sustaining shared understanding

• Facilitated workshops and chartering sessions — co-create with the people who will deliver it. Buy-in comes from participation.
• Storytelling — makes abstract vision tangible and relatable; a named technique, distinct from simply communicating clearly.
• Team charter and working agreements — created by the team, which is what drives adherence.
• Information radiators — keep the vision visible rather than filed.
• Regular reinforcement — iteration reviews, planning, and steering updates all connect back to it.

The root-cause enabler

Repeated divergence is rarely defiance. Common causes: the vision was communicated once at kickoff and never reinforced; it was expressed as outputs rather than outcomes, so it gives no guidance for trade-offs; different stakeholder groups received different framings; the environment changed and the vision did not; stated priorities conflict with actual incentives.

Two distinct diagnoses for the same symptom: resistance to the vision

The tell: has this stakeholder previously been informed/trained on the vision already (exclusion, not ignorance), or is this the first time the rationale has actually been explained to them (genuine awareness gap)? A stem describing anticipated, recurring resistance from a stakeholder who already knows the plan is signalling exclusion, not confusion.

Practice

Q1.

A project manager takes over a programme eight months into delivery. During the first fortnight, individual team members describe their assigned work accurately, but when asked what the programme is ultimately intended to achieve, each gives a different answer. Two describe it as a cost-reduction effort, one as a compliance remediation, and one is unsure. The programme is behind schedule. What should the project manager do FIRST?

A. Reissue the programme charter to all team members and confirm receipt.

B. Investigate how the differing understandings arose and facilitate a session with key stakeholders to establish a single agreed vision.

C. Focus on schedule recovery, since the delivery position is the more urgent problem.

D. Escalate to the sponsor that the team lacks clarity on programme objectives.

Q2.

An adaptive project is in its eleventh iteration. The organisation announced a strategic shift six weeks ago from market expansion to margin protection. The product vision statement, written at initiation, still references capturing new market segments. Team members have begun asking whether the work still matters. The project remains funded and on schedule. What should the project manager do?

A. Reassure the team that funding and schedule are unaffected and ask them to maintain focus on delivery.

B. Continue against the original vision, since it was approved and altering it mid-project would create instability.

C. Work with the product owner and key stakeholders to reassess the vision against the current strategy and update it as appropriate.

D. Request that the sponsor confirm in writing that the strategic shift does not apply to projects already underway.

Q3.

During a sprint review, a project manager notices that the delivered increment reflects a different interpretation of the product goal than the one the product owner articulated in planning. This is the third iteration in which the gap has appeared. The team is experienced and has consistently delivered high-quality work. What is the MOST likely explanation?

A. The team is deliberately prioritising work it finds more technically interesting.

B. The product owner lacks the authority to direct the team's work.

C. There is a shared-understanding gap whose root cause has not yet been identified.

D. The team requires additional training on interpreting user stories.

Q4.

A project manager is preparing a vision statement for a new adaptive product development effort. The sponsor has provided a one-line description of the desired outcome and asked the project manager to circulate it to the team and stakeholders for acknowledgement. What is the MOST significant risk in proceeding as instructed?

A. The statement may not follow the organisation's standard template for vision documentation.

B. Circulating for acknowledgement produces compliance rather than genuine buy-in, because stakeholders had no part in shaping the vision.

C. The sponsor rather than the product owner has drafted the description.

D. A one-line description will be insufficient for later scope definition.

Solutions

Q1 — Correct answer: B

B is correct. Team members can execute but cannot articulate purpose, and the descriptions conflict with one another — a shared-understanding failure with a traceable origin. The enabler calls for breaking down the situation to identify the root cause, then establishing one agreed vision with key stakeholders.

A is incorrect. Reissuing a document assumes the problem is transmission. Four people holding three different understandings suggests the framings originated differently, which a circulated charter will not reconcile.

C is incorrect. The schedule position is context. A team without a shared reference point cannot prioritise or self-correct, so the vision gap is plausibly a contributor rather than a separate concern.

D is incorrect. Escalating before investigating skips the project manager's own work and frames a team confusion as something the sponsor must fix.

Q2 — Correct answer: C

C is correct. The enabler "keep the vision current" applies directly. A vision that no longer connects to organisational strategy cannot guide decisions or sustain commitment, and the team's questions are the symptom. Note that the product owner owns the vision, so the project manager works with them rather than revising it unilaterally.

A is incorrect. Funding and schedule assurance does not answer a question about purpose, and it leaves a stale vision in place.

B is incorrect. Vision statements are living artifacts. Formal approval means changes follow a proper route, not that the project should pursue objectives the organisation has abandoned.

D is incorrect. Seeking exemption from a strategic shift protects the project rather than the organisation, and does nothing to restore shared understanding.

Q3 — Correct answer: C

C is correct. Three iterations of consistent divergence from an experienced, high-performing team is a pattern, not carelessness. The enabler is explicit about breaking down the situation to find the root cause of a misunderstanding — which has not yet been done here.

A is incorrect. This assigns motive without evidence. It is also inconsistent with the stem's description of consistent quality delivery.

B is incorrect. Nothing indicates an authority problem, and product owner authority over backlog priority is not the same as directing how the team works.

D is incorrect. Prescribing training presumes a knowledge gap before the cause has been diagnosed. It may be a dependency, a conflicting instruction, or information the team holds that the product owner does not.

Q4 — Correct answer: B

B is correct. "Help ensure a shared vision with key stakeholders" is participatory. A vision circulated for acknowledgement is complied with; a vision co-created is owned. Facilitated workshops exist precisely to close this gap.

A is incorrect. Template conformance is a documentation concern, not a significant project risk.

C is incorrect. Sponsors legitimately articulate desired outcomes. The product owner formalises and maintains the vision, but sponsor input at initiation is normal and not the primary risk here.

D is incorrect. Vision statements are deliberately concise. Scope definition is a separate downstream activity fed by the backlog, not by the length of the vision statement.

People Task 2 — Manage Conflicts

ECO enablers

• Identify conflict sources.
• Analyze the context for the conflict.
• Implement an agreed-on resolution strategy.
• Communicate conflict management principles with the team and external stakeholders.
• Establish an environment that fosters adherence to common ground rules.
• Manage and rectify ground rule violations.

Two layers you need, not one

Most preparation covers the five resolution modes and stops. Above-Target items require the diagnostic layer as well: Leas' levels tell you how severe the conflict is and therefore whether to act; the five modes tell you how to act once you have decided to.

The five resolution modes

Interprofessional versus interpersonal

The hard boundary

A disclosure that workplace conflict is affecting someone's mental health sits close to this boundary. It warrants a private, individual response and consideration of whether support beyond the project manager is needed — not a group intervention.

Ground rules and the team charter

A team charter defines the team's values, agreements, and operating guidelines, including acceptable behaviour and conflict-resolution processes. Established early, it prevents misunderstandings. It is the correct answer for anticipated tension, where nothing has yet gone wrong.

Note the authority point: a project manager without line-management authority still has the authority to decide how work will be conducted on the project. Ground rules on respectful communication and meeting conduct sit inside that authority even when discipline does not.

Practice

Q5.

Two senior engineers disagree about a technical approach during a design session. Both cite evidence, the exchange stays factual, and neither becomes personal, though the discussion is visibly tense. Other team members are following the argument with interest. What should the project manager do?

A. Intervene to mediate a resolution before the disagreement affects morale.

B. Observe the exchange and allow the team to work toward its own resolution.

C. Ask both engineers to submit written positions for the project manager to evaluate.

D. Adjourn the session and hold separate one-on-one meetings with each engineer.

Q6.

A project manager learns that communication between two sub-teams has effectively ceased. Each has begun documenting the other's failures, meetings between them have been cancelled twice, and members now route questions through the project manager rather than speaking directly. What should the project manager do?

A. Allow the sub-teams to resolve the situation independently to build their conflict-resolution capability.

B. Intervene and facilitate communication between the parties, focusing on de-escalation.

C. Reassign work so the sub-teams have minimal need to interact for the remainder of the project.

D. Raise the breakdown with both sub-team leads' functional managers as a performance concern.

Q7.

Two team members are in conflict over how testing responsibilities should be divided. The project manager has met each separately and understands both positions. When the project manager convenes them, one proposes that each simply give up half of what they asked for so the matter can be closed before the sprint ends. What should the project manager do?

A. Accept the proposal, since both parties have agreed and the sprint deadline is approaching.

B. Divide the responsibilities evenly by project manager decision to save further discussion time.

C. Explore why each division matters to them and work toward an allocation that serves the project's testing needs.

D. Defer the decision to the team lead with the greater testing experience.

Q8.

During a one-on-one, a team member tells the project manager that a colleague has made repeated comments about their national origin and that they now avoid meetings the colleague attends. What should the project manager do?

A. Establish ground rules on respectful communication and monitor future interactions.

B. Facilitate a conversation between the two team members to resolve the misunderstanding.

C. Escalate the matter through the appropriate organisational channel without delay.

D. Restructure assignments so the two team members interact as little as possible.

Solutions

Q5 — Correct answer: B

B is correct. Factual language, evidence-based argument, focus on the problem rather than the person — this is Level 1 or at most Level 2 on Leas' model. Below Level 4 the correct move is to observe and allow the team to resolve it, because working through the discomfort is how the team develops its own capability.

A is incorrect. Intervening at low severity removes the learning opportunity and signals that the team cannot handle normal disagreement. Tension alone is not a trigger.

C is incorrect. Written positions submitted for the project manager to evaluate converts a team disagreement into an adjudication, which is the force mode in procedural clothing.

D is incorrect. One-on-ones are the right instrument for a conflict you have decided to engage. Here you have not reached that threshold, and adjourning a productive technical debate is disproportionate.

Q6 — Correct answer: B

B is correct. Communication between the sides has broken down, sides have formed, and the parties are documenting grievances — Level 4, Crusade. Above Level 3 the project manager intervenes, and the described intervention at that level is facilitating communication between parties with de-escalation as the priority.

A is incorrect. The self-resolution guidance applies to Levels 1 through 3. Applying it at Level 4 allows a conflict that has already stopped functioning to continue deteriorating.

C is incorrect. Structurally separating the parties avoids the conflict rather than de-escalating it, and two sub-teams on the same project cannot realistically be insulated from each other.

D is incorrect. Escalating to functional managers as a performance matter mislabels a team conflict and skips the facilitation the project manager should lead.

Q7 — Correct answer: C

C is correct. "Each gives up half" is compromise — both parties lose something and the project's actual testing needs never enter the discussion. Exploring why each division matters and allocating against project priorities is collaboration, and it is available here.

A is incorrect. Agreement between two parties does not make an outcome correct. A compromise reached under deadline pressure can leave testing coverage worse than either original proposal.

B is incorrect. An even split decided by the project manager is compromise plus force, and it explicitly abandons the attempt to serve the project's needs.

D is incorrect. Deferring to seniority resolves by authority rather than merit and leaves the other party unaligned.

Q8 — Correct answer: C

C is correct. Repeated comments about national origin, with avoidance behaviour as a consequence, is a discrimination concern. That is explicitly beyond the project manager's purview and is escalated immediately through the appropriate organisational channel. The severity model and the conflict modes do not apply.

A is incorrect. Ground rules address ordinary interpersonal friction. Treating discrimination as a conduct-norms problem understates it and leaves the affected person unprotected.

B is incorrect. Facilitating a conversation between the parties frames discrimination as a mutual misunderstanding and places the affected person in a position they should not be asked to occupy.

D is incorrect. Restructuring assignments manages the project manager's convenience while leaving the underlying conduct unaddressed and unreported.

People Task 3 — Lead the Project Team

One of the highest-frequency tasks in the domain. Broad task; expect it anywhere.

ECO enablers

• Establish expectations at the team level.
• Empower the team.
• Solve problems.
• Represent the voice of the team.
• Support the team's varied experiences, skills, and perspectives.
• Determine an appropriate leadership style.
• Establish clear roles and responsibilities within the team.

Situational leadership

Tuckman, including the parts usually omitted

Forming, storming, norming, performing, adjourning. Teams are not fully effective until performing. Beyond the basic sequence, three points carry exam weight:

• Teams regress. Removing members, adding members, or repeatedly pulling people onto old work sends a team from performing back to norming or storming. If a high-performing team develops sudden friction after a composition change, that is the structural explanation — not a personality or leadership defect.
• Virtual teams take longer to move from storming to norming, for a stated reason: it is easier to withdraw from conflict remotely than to confront and resolve it. Silence in a distributed team is not evidence of calm.
• Tuckman's three factors are content, process, and feelings — the task itself, how the team works together, and the emotional layer. A leader facilitating team development attends to all three.

A practical consequence: because high-performing teams are expensive and slow to build, many organisations keep them intact and bring new work to them rather than disbanding and reforming. If a stem asks what to do with a team that has just reached performing as its project winds down, preserving the team is likely preferred over releasing and reforming.

Empowerment, precisely

Diverse skill levels

The validated instinct: assess competencies across all team members before designing any intervention, because experience does not guarantee proficiency and inexperience does not guarantee deficiency. Then address gaps through training, coaching, and mentoring. Pair programming and non-solo work are the mechanisms that make senior-to-junior transfer concrete.

Practice

Q9.

A project manager leads a team that has delivered three comparable systems successfully together. The project manager reviews and approves each technical decision before work proceeds. Team members have begun raising that decisions are taking longer than the work itself. What should the project manager do?

A. Maintain the review process, since technical decisions carry significant risk.

B. Move to a delegating approach, empowering the team to make technical decisions within agreed boundaries.

C. Replace the approval step with a daily decision-review meeting to maintain visibility.

D. Ask a senior team member to perform the technical reviews on the project manager's behalf.

Q10.

A distributed team reached the performing stage four months ago. Two weeks ago, one member transferred out and two new members joined. The team now reports disagreements about task ownership and decision rights, and the coach observes members competing for informal influence. What is the MOST likely explanation?

A. The new members lack the technical competence required and need remedial training.

B. The team has regressed to an earlier development stage following the change in composition.

C. The project manager failed to establish clear ground rules at the outset.

D. The distributed working arrangement is no longer viable for a team of this size.

Q11.

A project is entering its final month. The team has been together for two years, reached high performance, and is regarded across the organisation as unusually effective. The resource manager intends to release all members to separate assignments at closure. What should the project manager recommend?

A. Release the team as planned, since resource release is a required closure activity.

B. Extend the project to retain the team until a suitable replacement project is identified.

C. Recommend that the intact team be assigned to upcoming work, given the cost and time required to rebuild high performance.

D. Release the team but document their working agreements so a future team can adopt them.

Q12.

A newly formed team of six is starting an unfamiliar regulatory implementation with a fixed statutory deadline. Members have not worked together before and none has delivered this type of work previously. What leadership approach is MOST appropriate initially?

A. Delegating, to establish trust and demonstrate confidence in the team from the outset.

B. Supportive, to build cohesion during the forming stage.

C. Directive, providing clear structure and direction given the inexperience and the fixed deadline.

D. Coaching, to develop capability while the team learns the regulatory domain.

Solutions

Q9 — Correct answer: B

B is correct. A proven, self-sufficient team paired with a project manager who has become an approval bottleneck is a style mismatch. Delegating matches the team's demonstrated competence, and "within agreed boundaries" preserves the boundary-condition principle rather than abandoning oversight entirely.

A is incorrect. Risk level is only one variable; team competence is the other, and the stem establishes it clearly. Maintaining directive control over a proven team produces exactly the delay described.

C is incorrect. A daily review is the same bottleneck on a different cadence. It addresses the schedule of the constraint rather than the constraint itself.

D is incorrect. Delegating the review to a team member preserves the approval gate and adds a peer-approval dynamic. It also sidesteps the project manager's responsibility to adjust their own leadership approach.

Q10 — Correct answer: B

B is correct. Competition for informal influence and disputes over roles and decision rights are storming behaviours. A composition change is a named trigger for regression from performing, and the timing in the stem is unambiguous.

A is incorrect. Nothing indicates a competence problem; the described behaviours concern hierarchy and ownership, not capability. This also repeats the unverified-assumption error.

C is incorrect. The team previously reached performing, which means norms were established. The issue is that a changed team must re-establish them, not that they never existed.

D is incorrect. The team worked effectively while distributed for months. Distribution may lengthen the return to norming, but it is not the cause of the change.

Q11 — Correct answer: C

C is correct. High-performing teams are costly and slow to build, and the recognised practice is to bring new work to an intact team rather than disband and pay the forming, storming, and norming cost again. Recommending this to the resource manager is within the project manager's role as the voice of the team.

A is incorrect. Resource release is a closure activity, but this option treats a standard step as though it overrides an organisational value judgement that the project manager is positioned to inform.

B is incorrect. Extending a project to retain staff is artificial, misrepresents the project's status, and consumes funding for work that is complete.

D is incorrect. Working agreements are specific to the people who made them. Documenting them does not transfer the relationships, trust, and shared experience that constitute high performance.

Q12 — Correct answer: C

C is correct. A newly formed team, no prior experience of this work, and a fixed statutory deadline together indicate low competence on the task and high time pressure. Directive leadership provides the structure a forming team needs, and it is applied in service of the team rather than as an expression of authority.

A is incorrect. Delegating suits proven, self-sufficient teams. Applied to an inexperienced team facing an unfamiliar domain, it withholds the direction they need.

B is incorrect. Supportive fits an experienced team needing encouragement. This team lacks the capability, not the confidence.

D is incorrect. Coaching is the strongest alternative and becomes appropriate as the team develops. Initially, with no domain experience and a statutory deadline, structure precedes development.

People Task 4 — Engage Stakeholders

ECO enablers

• Identify stakeholders.
• Analyze stakeholders.
• Analyze and tailor communication to stakeholder needs.
• Execute the stakeholder engagement plan.
• Optimize alignment among stakeholder needs, expectations, and project objectives.
• Build trust and influence stakeholders to accomplish project objectives.

Identification

A stakeholder is anyone directly or indirectly affected by the project. Cast wide early: over-inclusion is cheap and reversible, under-inclusion is expensive and discovered late. Someone added unnecessarily can be removed; someone missed surfaces as a late objection, often at an approval gate.

Analysis tools

The engagement levels, in order: Unaware → Resistant → Neutral → Supportive → Leading.

Re-analysis triggers

Stakeholder analysis is not a one-time activity. Two distinct triggers require formal reassessment:

• A structural change — the stakeholder's role, authority, or organisational position has changed. This is comparative: their standing relative to everyone else has moved, and only systematic reassessment captures that.
• Observed behaviour over time — someone categorised as low influence begins attending sessions and advocating for outcomes. Evidence has changed, so the categorisation should change.

Tailoring communication versus holding requirements

Discriminator 6 in Part 1 is the highest-value rule in this task; it is restated here because this is where it will be tested.

Building trust

Know stakeholders individually where you can. Understand motivations, not just positions. Recognise that external stakeholders — regulators, government representatives, agencies — are motivated differently from internal teams and require their own analysis rather than an extension of internal assumptions.

Practice

Q13.

A regulatory stakeholder with authority to approve project phases has raised concerns about the compliance approach. This stakeholder is difficult to reach and consistently favours informal contact over the project's formal reporting processes. What approach should the project manager take?

A. Adapt communication methods to the stakeholder's preferences while ensuring compliance requirements continue to be met and documented.

B. Escalate the stakeholder's concerns to senior management and request formal intervention.

C. Hold regular informal meetings to build rapport and address concerns before they affect approvals.

D. Record the stakeholder's communication preferences in the risk register and increase monitoring.

Q14.

A stakeholder categorised at initiation as low influence has, over the last three iterations, attended every design session and argued forcefully for particular features. Their department has also recently been given budget authority over the programme. What should the project manager do FIRST?

A. Meet the stakeholder individually to understand their specific interests and expectations.

B. Conduct stakeholder analysis to assess how the changed position affects influence, priority, and communication needs across the stakeholder group.

C. Update the communications management plan to increase this stakeholder's reporting frequency.

D. Record the increased involvement in the issue log and monitor for further escalation.

Q15.

A project engages three external agencies. One is involved only during content creation, one only during technical build, and one from initiation through closure. The project manager finds that agencies are being invited to meetings irrelevant to them while missing sessions where their input was needed. What technique BEST addresses this?

A. Reassess each agency on the power/interest grid and adjust engagement levels accordingly.

B. Map stakeholders against the deliverables and phases in which each is active, and align meeting participation to that map.

C. Invite all three agencies to all project meetings to eliminate the risk of missing input.

D. Delegate meeting coordination to each agency's account manager.

Q16.

A project manager inherits a project where the stakeholder register lists eleven stakeholders. During execution, a department that was not registered raises a formal objection at a phase gate, causing a three-week delay while its requirements are assessed. What does this MOST clearly indicate?

A. The phase gate process lacks sufficient controls to prevent late objections.

B. Stakeholder identification was incomplete, and the cost of the omission surfaced at an approval point.

C. The department overstepped by raising an objection at a gate rather than earlier.

D. The stakeholder register should be replaced with a more detailed engagement matrix.

Solutions

Q13 — Correct answer: A

A is correct. The stem sets two conditions that must both hold: a genuine channel preference, and live compliance requirements. A satisfies both — adapt the channel to build engagement, while ensuring compliance obligations are still met through proper documentation. Tailoring the method does not mean abandoning the record.

B is incorrect. Requesting formal intervention against a stakeholder who has already signalled discomfort with formal processes is likely to harden the position, and nothing has been attempted directly yet.

C is incorrect. The strongest distractor, and it is A with the compliance half removed. Informal rapport alone with an approval authority risks agreements and concerns that never enter the formal record.

D is incorrect. Logging a preference and monitoring is passive, and framing a communication preference as a risk casts the stakeholder as a threat to manage rather than a party to engage.

Q14 — Correct answer: B

B is correct. Two triggers are present at once — sustained behavioural change and a structural shift in authority, now touching budget. The question is what this stakeholder's new standing means relative to the whole group, which only systematic analysis answers.

A is incorrect. An individual meeting gathers this person's perspective but does not assess impact, influence, or priority across the stakeholder group. Useful, but not first.

C is incorrect. Updating the communications plan formalises a solution before the analysis that would justify it. Frequency may not be the variable that needs to change.

D is incorrect. The issue log records things that have gone wrong. A stakeholder becoming more engaged and gaining authority is a categorisation change, not an issue.

Q15 — Correct answer: B

B is correct. The problem is entirely about when each party is relevant, not how much influence they hold. Timeline-based mapping against deliverables and phases is the technique built for exactly this, and it resolves both symptoms — irrelevant invitations and missed input.

A is incorrect. The power/interest grid sorts on attention level. All three agencies may warrant similar attention; the failure is in timing, which the grid does not capture.

C is incorrect. Inviting everyone to everything solves the missed-input half by making the irrelevant-invitation half considerably worse, and it wastes external parties' billable time.

D is incorrect. Delegating coordination outsources a planning responsibility and gives each agency only its own view, with no one holding the integrated picture.

Q16 — Correct answer: B

B is correct. An unregistered department with standing to object at a phase gate is a missed stakeholder. The characteristic cost profile is exactly as described — invisible during planning, expensive at an approval point. This is why identification should over-include rather than under-include.

A is incorrect. The gate worked as designed; it surfaced an unmet requirement. Adding controls to suppress objections at gates would defeat their purpose.

C is incorrect. A stakeholder raising a legitimate objection at the first point they were consulted has not overstepped. The failure was upstream.

D is incorrect. A different artifact would not have contained a stakeholder nobody identified. The register was not the wrong tool; it was incompletely populated.

People Task 5 — Align Stakeholder Expectations

The highest-frequency task in the domain. If you learn one enabler phrase verbatim, make it this one.

ECO enablers

• Categorize stakeholders.
• Identify stakeholder expectations.
• Facilitate discussions to align expectations.
• Organize and act on mentoring opportunities.

The pattern that decided every item

The wrong answers cluster into four recognisable shapes, and it is worth being able to name them on sight:

The mentoring enabler

The fourth enabler sits oddly alongside the other three and is easy to overlook. Two things belong to it:

Two associated behaviours worth recognising: show rather than tell — a mentor demonstrates rather than only explaining; and give explicit permission and backing — telling someone you stand behind them while they apply an unfamiliar method builds confidence more effectively than solving the problem for them.

The related idea, drawn from agile leadership practice: align project tasks with individual career goals. When someone sees how the work advances their own development, engagement follows. If a stem shows a team member disengaged despite clear vision and genuine empowerment, this is the lever that has not been pulled.

Practice

Q17.

During early planning for a transformation programme, executive stakeholders divide sharply. Several want rapid release of customer-facing capability to capture market position; others insist nothing releases until security controls are fully validated. The sponsor states that one approach must be settled to avoid conflicting baselines. What should the project manager do?

A. Record both sets of priorities in the draft plan so each group is equally represented.

B. Prepare impact analyses for both positions and ask the sponsor to select the stronger plan.

C. Facilitate structured workshops to reconcile the conflicting priorities and document an approved shared vision.

D. Baseline the scope according to the market-capture position, since first-mover advantage is time-limited.

Q18.

A sponsor expects a platform delivered in six months with the full feature set. The delivery team's analysis puts it at nine months for the same scope. What should the project manager do to establish alignment?

A. Meet each party separately to determine which estimate is more credible.

B. Discuss the reasons for the discrepancy with both parties together and develop an agreed timeline.

C. Provide both parties with a detailed plan setting out the constraints and technical challenges.

D. Work with the sponsor to adjust their expectations toward a feasible date.

Q19.

A capable team member has delivered consistently for a year but has recently become noticeably disengaged. The project vision is clear and well communicated, the team is genuinely empowered within agreed boundaries, and the person raises no complaints about the work or their colleagues. What should the project manager explore FIRST?

A. Whether the person's current assignments connect to their own development and career goals.

B. Whether the person's technical skills have fallen behind the demands of the role.

C. Whether team ground rules need to be re-established.

D. Whether the person should be reassigned to a project better matched to their interests.

Q20.

A junior team member repeatedly asks the project manager how to handle a category of technical problem. The project manager wants the person to become capable of resolving this class of problem independently. Which approach BEST serves that intent?

A. Demonstrate the established method so the person can follow it accurately in future.

B. Ask guided questions that lead the person to work out an approach themselves.

C. Provide written documentation of the standard procedure for reference.

D. Pair the person with a senior colleague who will handle these problems going forward.

Solutions

Q17 — Correct answer: C

C is correct. Conflicting expectations across multiple stakeholders, with the sponsor explicitly requiring a single approach. Facilitated reconciliation producing one documented shared vision is the enabler applied directly, and it is the only option that yields agreement rather than a selection.

A is incorrect. Recording both positions separately preserves the conflict inside the plan. It directly contradicts the sponsor's stated requirement and leaves the vision fragmented.

B is incorrect. Asking the sponsor to choose takes responsibility that belongs to the project manager, and it produces one side's vision formally selected rather than a shared one.

D is incorrect. Baselining on one camp's position ignores the security stakeholders entirely and invites exactly the mid-project dispute the sponsor is trying to prevent.

Q18 — Correct answer: B

B is correct. Two parties, two conflicting estimates, no agreement. Bringing both into the same discussion to examine why they diverge and building one timeline together is inclusive alignment.

A is incorrect. Separate meetings may clarify each view but do not create alignment between the parties, and judging whose estimate is more credible casts the project manager as adjudicator.

C is incorrect. A detailed plan is one-way communication. Documentation informs; it does not reconcile a three-month gap between two parties' expectations.

D is incorrect. The most tempting distractor. Working only with the sponsor ignores team input and risks bias — this is one-sided negotiation rather than inclusive alignment.

Q19 — Correct answer: A

A is correct. The stem systematically eliminates the usual causes: vision is clear, empowerment is real, no interpersonal or work complaints. What remains is the connection between the work and the individual's own goals — aligning assignments with personal development is the recognised lever, and it sits under this task's mentoring enabler.

B is incorrect. The person has delivered consistently for a year. Nothing indicates a capability decline, and this repeats the unverified-assumption error.

C is incorrect. Ground rules address team-level behaviour. This is one individual's engagement, with no reported friction.

D is incorrect. Reassignment is a response, not an exploration, and the stem asks what to explore first. Moving someone before understanding the cause may relocate the problem.

Q20 — Correct answer: B

B is correct. The stated intent is independent capability. Coaching draws the solution out of the person so that the answer comes from them, which is what builds the ability to handle the next instance without help.

A is incorrect. Demonstrating a method is mentoring. It is valuable and often correct, but it transfers a specific solution rather than developing independent problem-solving, which is what the stem asks for.

C is incorrect. Documentation supports recall of a known procedure. It does not develop the judgement to work through an unfamiliar instance.

D is incorrect. Assigning a senior colleague to handle the problems removes them from the junior member entirely, which is the opposite of building independence.

People Task 6 — Manage Stakeholder Expectations

ECO enablers

• Identify internal and external customer expectations.
• Align and maintain outcomes to internal and external customer expectations.
• Monitor internal and external customer satisfaction/expectations and respond as needed.

Task 5 or Task 6?

These overlap and a single item may touch both. The practical distinction:

Meeting expectations is not the same as organising around them

Quality as an expectations concept

A validated and slightly counterintuitive point: a quality-driven approach is a legitimate answer to a stakeholder-expectations question. Quality here is not narrow conformance to written specification — it encompasses regulatory requirements, regional specifications, and stakeholder standards that may exceed regulatory minimums.

Responding to dissatisfaction

When users report that delivered functionality is confusing or does not meet their needs, the first responsibility is to understand the root cause — gather direct feedback and engage the team to analyse what went wrong and how the next iteration improves. Informing the team without acting "reflects poor responsiveness and weakens user trust." Documenting in the change and issue logs is administrative and delays resolution.

Practice

Q21.

A shipping company is extending services into an unfamiliar regional market. The project manager must align and maintain project outcomes with the expectations of both internal and external stakeholders. What should the project manager do?

A. Apply a predictive approach to ensure the project satisfies all regulatory and governmental specifications.

B. Differentiate the roles and responsibilities of internal and external stakeholders to ensure consistent expectations.

C. Implement a quality-driven approach that addresses stakeholder expectations and ensures their standards are met.

D. Experiment with project specifications so deliverables exceed the stated objectives.

Q22.

Two iterations after release, a team member reports that several users find newly delivered functionality confusing and say it does not meet their needs. Further releases are already scheduled. What should the project manager do?

A. Inform the team of the feedback and proceed with the planned release schedule.

B. Document the concern and update the change and issue logs accordingly.

C. Collect feedback directly from the affected users and discuss it with the team to understand what went wrong.

D. Review individual responsibilities within the delivery team to prevent recurrence.

Q23.

A project delivers a system that meets every documented regulatory requirement for the market it serves. At acceptance, the principal customer states that the system falls short of the standard they expected and declines to endorse the rollout. Which statement BEST characterises the situation?

A. The customer is applying standards beyond the agreement and the objection should be declined.

B. Regulatory compliance was achieved but customer expectations, which exceeded the regulatory minimum, were not identified or met.

C. The quality management plan was not executed correctly during delivery.

D. The customer should have raised their standards during requirements gathering, so the gap is theirs.

Q24.

Midway through delivery, a project manager notices that satisfaction feedback from an internal customer group has declined across three consecutive reporting periods, though no formal complaint has been raised and all deliverables have been accepted. What should the project manager do?

A. Continue as planned, since deliverables are being accepted and no complaint has been raised.

B. Investigate the decline with the internal customer group and respond to what it reveals.

C. Record the trend in the project status report for the steering committee's awareness.

D. Increase the frequency of satisfaction surveys to obtain more data before acting.

Solutions

Q21 — Correct answer: C

C is correct. A quality-driven approach accounts for regulatory requirements, regional specifications, and stakeholder expectations together. Addressing the full standard set — including standards that exceed legal minimums — is what aligns outcomes with what stakeholders actually expect.

A is incorrect. Regulatory compliance is necessary but insufficient. A delivery methodology also does not address the broader stakeholder system, and choosing an approach is a different question from meeting expectations.

B is incorrect. The strongest distractor because it echoes the stem's own "internal and external" language. But clarifying who does what does not guarantee that expectations are met — it organises rather than delivers.

D is incorrect. Exceeding stated objectives without first establishing what stakeholders expect is gold plating. Objectives must be grounded in identified expectations before anything can meaningfully exceed them.

Q22 — Correct answer: C

C is correct. The enabler requires monitoring customer satisfaction and responding as needed. With releases still ahead, understanding the root cause directly from users and analysing it with the team is what allows the next iteration to improve.

A is incorrect. Informing the team without acting ignores the feedback loop, and is characterised as poor responsiveness that weakens user trust.

B is incorrect. Logging is an administrative step rather than a leadership action. It delays resolution and disconnects the project manager from the engagement responsibility.

D is incorrect. The users are confused about the product; nothing indicates the team was confused about their roles. This addresses the wrong party entirely.

Q23 — Correct answer: B

B is correct. Conformance to regulation was achieved; expectations were not. The gap is that the customer's standards exceeded the regulatory minimum and were never identified — which is the first enabler of this task, not a defect in delivery.

A is incorrect. Declining a principal customer's objection on the grounds that regulation was satisfied treats compliance as the ceiling. It also abandons the relationship rather than addressing the gap.

C is incorrect. Nothing indicates the quality plan was executed incorrectly. The plan appears to have targeted the regulatory standard successfully; the failure was in what the standard was set against.

D is incorrect. Assigning fault to the customer for not stating their standards does not resolve anything, and identifying customer expectations is explicitly the project manager's enabler.

Q24 — Correct answer: B

B is correct. The enabler is to monitor satisfaction and respond as needed. A sustained three-period decline is a signal regardless of whether a complaint has been filed; acceptance of deliverables does not establish satisfaction with them.

A is incorrect. Waiting for a formal complaint means acting only once dissatisfaction has escalated. Monitoring exists precisely to catch the trend earlier.

C is incorrect. Reporting the trend informs the steering committee without investigating or responding. Documentation in place of engagement is the recurring administrative trap.

D is incorrect. More data on a trend already visible across three periods delays response without changing what you know. The signal is sufficient to act on.

People Task 7 — Help Ensure Knowledge Transfer

ECO enablers

• Identify knowledge critical to the project.
• Gather knowledge.
• Foster an environment for knowledge transfer.

Explicit and tacit

Four mechanics that separate Above Target

1. Selection comes first

Knowledge is not equal. Prioritise what materially affected outcomes: revisit risk logs and the decisions that shaped the project's course, mine stakeholder conversations for unexpected wins and setbacks, and capture the turning points where the team gained clarity or changed direction. Exhaustive documentation of everything is not the goal and is not the answer.

2. Verify transfer; do not assume it

3. Format follows audience

End users need simple instructions; technical staff need documentation; operators need checklists; managers need scheduling guidance. Recognise the formats: manuals and wikis for reference, hands-on training for practical skill, Q&A for clarification, runbooks for operations, quick reference cards, job shadowing, and train-the-trainer for multiplying reach.

4. Storage is not distribution

Timing and acceptance

• Build knowledge transfer into the project timeline rather than compressing it into handover week. Plan training cycles before go-live; schedule practice runs so receiving teams can operate under supervision.
• Make it part of the acceptance criteria. A deliverable is not complete if the people who must run it cannot demonstrate that they can. This extends acceptance beyond technical conformance to operational readiness.
• Eliminate single points of failure. Where one expert holds critical knowledge, document thoroughly and spread training. Knowledge stewards — named owners responsible for keeping records current — are the organisational form of this.

Environment

Knowledge transfer fails where people fear blame or hoard expertise for job security. The enabling conditions: leaders share openly and model the behaviour; knowledge-sharing appears in performance discussions; post-project reviews focus on learning rather than fault; peers are paired for informal mentoring. Organisations that sustain this are described as learning organisations — the same underlying principle as blameless culture, applied to sharing.

Sources, matched to knowledge type

Restating Discriminator 5, because this is the task where it is tested: quantifiable information — hours, costs, budgets, overruns — lives in financial and knowledge repositories, not in people's recollection. Experiential context lives in people. A stem can wrap a quantitative question in relational narrative; answer the question asked.

Practice

Q25.

A national franchise operator is rolling out a product upgrade. A long-serving stakeholder wants to share their experience of the existing product with staff at other locations. The sponsor requires a systematic approach ensuring knowledge reaches employees at every franchise. What should the project manager do?

A. Record one-to-one video interviews capturing first-hand employee experiences.

B. Compile the knowledge gathered at each location into a shared document accessible to all employees.

C. Develop a formal knowledge transfer framework that collects tacit knowledge such as personal experience.

D. Arrange face-to-face sessions at each location to replace the current informal exchange.

Q26.

A project manager new to a client wants to understand how previous teams handled resourcing and labour requirements on comparable engagements. What should the project manager do?

A. Hold a session with project managers from the previous engagements to learn from their experience with this client.

B. Examine financial data repositories for hours worked, incurred costs, budgets, and cost overruns.

C. Meet the client and stakeholders to understand expectations based on previous project performance.

D. Compare scope baselines from the previous engagements against the current scope.

Q27.

Before go-live on a new operational system, the project team delivers structured training to the operations group. Attendance is complete and every participant confirms verbally that the material is clear. Three weeks after go-live, the operations group is escalating routine issues it was trained to resolve. What should the project manager have done differently?

A. Extended the training to cover additional depth on advanced scenarios.

B. Asked participants to demonstrate handling specific scenarios rather than relying on verbal confirmation.

C. Supplied written manuals alongside the training sessions.

D. Deferred go-live until the operations group requested additional training.

Q28.

The only engineer who understands a legacy interface is leaving the project in four weeks. The project manager asks them to produce comprehensive documentation before departure. The documentation is delivered and is thorough. Two months later, the remaining team still cannot resolve interface faults efficiently. What was the PRIMARY shortcoming?

A. The documentation should have been reviewed for completeness before the engineer left.

B. Documentation captured the explicit knowledge but not the tacit judgement, which required pairing or shadowing alongside it.

C. The engineer should have been retained until the team demonstrated competence.

D. An external specialist should have been engaged to cover the interface.

Solutions

Q25 — Correct answer: C

C is correct. The sponsor asked for a systematic approach covering every location, and the content in question — personal experience — is tacit. A formal framework is the only option that is both scalable across all franchises and built to capture tacit knowledge.

A is incorrect. Video interviews are a technique, not a framework, and as written the option omits the distribution mechanism. Recordings are useful only if hosted centrally with access granted.

B is incorrect. Compiling into a shared document does nothing to push the information out to employees, and a document is a poor vessel for experiential knowledge.

D is incorrect. Face-to-face sessions at every location would be prohibitively costly and would still not share information across franchises.

Q26 — Correct answer: B

B is correct. Resourcing and labour requirements are quantifiable — hours, costs, budgets, overruns. That information lives in repositories, which hold it accurately and completely. The mention of the client is context, not the subject of the question.

A is incorrect. The most tempting option, because client experience feels tacit. But a project manager is unlikely to recall quantifiable figures such as budget numbers and overruns from past engagements. Right source for judgement; wrong source for data.

C is incorrect. Stakeholders may not hold the relevant historical information, and their expectations for the current project are a different question from how prior teams resourced the work.

D is incorrect. Scope baselines are useful for defining current scope but do not contain lessons learned, cost overruns, or resourcing history.

Q27 — Correct answer: B

B is correct. Training was delivered and verbally confirmed, yet the capability is absent — the classic gap between delivery and verification. Demonstration is the technique that surfaces it: ask the person to show how they would handle a scenario.

A is incorrect. More depth addresses a coverage gap. Routine issues were within the training scope, so coverage was not the failure.

C is incorrect. Manuals add a reference format but do not verify that understanding was achieved. This adds material rather than confirming capability.

D is incorrect. Waiting for the receiving group to request more training relies on them recognising a gap they are unaware of — verbal confirmation showed they believed they understood.

Q28 — Correct answer: B

B is correct. Thorough documentation captured the explicit layer — what the interface does and how it is configured. Troubleshooting a legacy interface depends on tacit judgement: which symptom points where, what has failed before, why an obvious fix is wrong. That transfers through pairing, shadowing, and mentoring alongside documentation, not instead of it.

A is incorrect. The stem states the documentation was thorough. Reviewing it for completeness would have confirmed what was already true and left the tacit gap untouched.

C is incorrect. Demonstrated competence is a sound principle, but retaining a departing engineer indefinitely is not actionable, and the underlying error was the method chosen, not its duration.

D is incorrect. An external specialist transfers nothing and substitutes one dependency for another, with less project context than the departing engineer had.

People Task 8 — Plan and Manage Communication

Live-validated since the original fifteen-item gap was flagged. A distributed, multi-timezone team with unclear requirements and difficulty arranging meetings was correctly resolved by reviewing the communications management plan and shifting toward documentation as the primary channel — "when teams are virtually distributed, increased documentation helps ensure that requirements are understood by all involved... relying solely on verbal communication limits success." For distributed teams specifically, the default fix for unclear requirements is documentation-first, not meeting-first, since interactive channels are structurally hardest to arrange for exactly this population.

ECO enablers

• Define a communication strategy.
• Promote transparency and collaboration.
• Establish a feedback loop.
• Understand reporting requirements.
• Create reports aligned with sponsors and stakeholder expectations.
• Support reporting and governance processes.

The three methods

Planning the strategy

1. Identify audiences. Executives, regulators, delivery teams, operators, and end users need different content at different depths.
2. Define objectives. What should each audience know or do after receiving this? A weekly email nobody reads has no objective.
3. Choose channels to fit the audience — formal reporting for regulators, dashboards for executives, calls for urgent matters, face-to-face where trust must be built.
4. Set frequency by audience. Daily suits a delivery team; weekly summaries suit executives. Too much overwhelms, too little creates gaps.
5. Plan feedback loops. Build in space for questions and responses; this is where misunderstandings surface before they become adoption failures.
6. Document it in a communications matrix: audience, content, channel, frequency, owner.

Two principles that decide items

Transparency

Transparency about why a decision was made does not require agreement with it. A product owner who walks through the criteria used to order the backlog builds trust even among those who disagree with the ordering. Do not read "not everyone agreed" as evidence that the communication failed.

Information radiators

A visual control displaying project information where passers-by absorb it without asking. Not one artifact but a consolidated surface, typically carrying:

• Charter summary — objectives, key features, risks, key roles, glossary of project terms
• Impediments and blockers — outstanding and resolved, colour-coded
• Product backlog and iteration backlog
• Iteration burndown — work remaining, against committed work
• Release burnup — progress toward the release goal, and scope changes
• Working agreements — how the team works together and what members expect of each other

Recognise the pattern rather than only the term: a single visual surface consolidating status, blockers, and team agreements is an information radiator whether or not the phrase appears.

Distributed teams

• Fishbowl window — a persistent video link between distributed locations, distinct from a timeboxed video conference. It exists to enable informal participation throughout the day and therefore osmotic learning.
• Remote pairing — non-solo work over 1:1 collaboration tools, best supported by a shared whiteboard or document plus real-time audio and video, and ideally between near time zones.
• Persistent chat and shared repositories address asynchronous working; video conferencing addresses the loss of tone and body language.

Practice

Q29.

A project manager issues detailed written status updates to all stakeholders each week. Despite this, several key stakeholders state they were unaware of a schedule slip that was reported in three consecutive updates. What should the project manager do?

A. Mark critical items as high priority within the existing updates so they stand out.

B. Establish a two-way mechanism, such as brief review sessions, to confirm that key stakeholders have understood critical information.

C. Move status information to a shared dashboard that stakeholders can consult at any time.

D. Increase the frequency of the written updates to improve the likelihood they are read.

Q30.

A project manager becomes aware of an emerging compliance exposure that may affect a forthcoming milestone. The full impact assessment will take a further week. An internal audit review of the project is scheduled in three days. What should the project manager do?

A. Complete the impact assessment before informing any stakeholder, to avoid raising alarm on incomplete information.

B. Inform relevant stakeholders now of the exposure and the assessment underway, and commit to reporting the full impact when available.

C. Request that the audit review be rescheduled until the assessment is complete.

D. Manage the exposure within the project team and inform stakeholders only if the auditor raises it.

Q31.

On a hybrid programme, the adaptive team holds daily standups and retrospectives and considers its practices highly transparent. The predictive workstream leads and two external stakeholders report that they have no visibility of the adaptive team's progress or blockers. What is the MOST likely cause?

A. The adaptive team is not genuinely transparent within its own ceremonies.

B. Transparency was maintained inside the team's practices but never extended to the wider programme and its stakeholders.

C. The predictive workstream leads lack the background to interpret adaptive terminology.

D. External stakeholders should not expect the same level of detail as the delivery team.

Q32.

A distributed team has been provided with a persistent video link, a shared repository, and a persistent chat platform. Six weeks later, members rarely use the video link, context continues to be missed between locations, and duplicated work has occurred twice. What is the MOST likely cause?

A. The tools are inadequate and should be replaced with a more capable integrated platform.

B. The team was not trained on how and when to use the tools, and no shared norms for their use were agreed.

C. The time zone spread is too wide for any collaboration tooling to be effective.

D. The persistent link should be replaced with scheduled, timeboxed video conferences.

Solutions

Q29 — Correct answer: B

B is correct. The information was pushed and not absorbed. That is a comprehension gap, and the remedy is a feedback loop — interactive communication that confirms critical messages have been received and understood.

A is incorrect. Priority flags are still push, still one-way. Louder is not understood.

C is incorrect. Moving to pull asks stakeholders who are already not absorbing pushed information to go and retrieve it. This makes the gap wider, not narrower.

D is incorrect. Frequency is not the issue; the information was reported three times. More of an ineffective method compounds it and risks disengagement.

Q30 — Correct answer: B

B is correct. Bad news must reach stakeholders from the project manager first. Informing them now — with the assessment acknowledged as in progress — preserves credibility and gives them time to prepare. Waiting risks the auditor surfacing it, which damages trust well beyond the exposure itself.

A is incorrect. Withholding until certainty is achieved is the reasoning that produces exactly the failure described: stakeholders learning of a project risk from a third party.

C is incorrect. Rescheduling an audit to manage the timing of disclosure manipulates the process rather than communicating honestly, and edges toward an integrity problem.

D is incorrect. Contingent disclosure — informing only if caught — is concealment. Options structured this way are reliably wrong.

Q31 — Correct answer: B

B is correct. Internal ceremonies are transparent to their participants and to nobody else. On hybrid programmes, information must be deliberately radiated beyond the team to the predictive workstream and to stakeholders; standups do not do that by default.

A is incorrect. The stem gives no indication of a problem inside the ceremonies, and this misplaces the failure.

C is incorrect. This treats a visibility gap as a comprehension deficiency in the audience, which reverses responsibility for communication.

D is incorrect. Deciding stakeholders are not entitled to visibility is dismissive, and the complaint is about having none rather than about depth of detail.

Q32 — Correct answer: B

B is correct. Tools were provided; usage and norms were not. Without training on how and when to use them, and agreed working agreements governing their use, collaboration tooling goes unused and the gaps it was bought to close remain.

A is incorrect. The toolset described is appropriate to the problem. Replacing adequate tools that are not being used produces better tools that are not being used.

C is incorrect. Time zone spread is a genuine constraint but does not explain non-use of an asynchronous repository and a persistent chat platform, which exist precisely for that condition.

D is incorrect. Timeboxed conferences remove the ambient, informal participation the persistent link was intended to create, discarding osmotic learning rather than enabling it.

PART 3 — Mixed Discrimination Drill

Eight items, no task labels, drawn from across the domain and deliberately built around the discriminators most likely to cost an Above-Target mark. Answer all eight before checking any solution.

Q33.

A project manager wants to understand why a supplier consistently outperformed on two previous programmes, in order to replicate the arrangement. What should the project manager do FIRST?

A. Retrieve the supplier's performance metrics and contract terms from the procurement records.

B. Speak with the project managers who ran those programmes about how they managed the relationship.

C. Meet the supplier to ask what contributed to their performance.

D. Review the lessons learned registers from both previous programmes.

Q34.

Team members from two regions have stopped sharing information across regional lines on a global programme. The sponsor has emphasised that cross-regional collaboration is essential. What should the project manager do?

A. Arrange structured one-to-one meetings between members from each region to build individual relationships.

B. Provide cultural awareness training to build understanding of differing practices across the team.

C. Assign work so that each region has minimal dependency on the other.

D. Offer language training in each region's primary language.

Q35.

A key stakeholder tells the project manager that the fortnightly steering report is too long and that they only read the first page. They ask for a one-page summary instead. What should the project manager do?

A. Continue the current report, since it satisfies the governance reporting requirement.

B. Provide a one-page summary tailored to this stakeholder while maintaining the full report for governance purposes.

C. Coach the stakeholder on why the full detail matters to their oversight role.

D. Shorten the report for all recipients to a single page.

Q36.

Three team members have independently told the project manager that a fourth colleague dominates design discussions and dismisses alternative proposals. The colleague concerned has said nothing. Discussions have become noticeably quieter over recent weeks. What should the project manager do FIRST?

A. Raise the pattern in the next team meeting so it can be discussed openly.

B. Meet the colleague individually to understand their perspective before deciding on any action.

C. Introduce a facilitation technique that gives every participant a turn to contribute.

D. Escalate the behaviour to the colleague's functional manager.

Q37.

A project team has developed a lightweight estimation technique during delivery that materially improved forecast accuracy. The organisation does not currently use it. What should the project manager do to ensure future projects benefit?

A. Record it in the project's lessons learned register and reference it in the final report.

B. Demonstrate it to other project managers at the next community of practice session.

C. Document it in reusable form and add it to the organisational knowledge repository.

D. Obtain the sponsor's endorsement of the technique for use on future work.

Q38.

During planning, a project manager identifies that two departments hold incompatible assumptions about who will own the system after handover. Neither has raised it; the project manager noticed it while comparing their submitted requirements. What should the project manager do?

A. Document both assumptions in the assumption log and raise them at the next steering committee.

B. Bring both departments together to surface the incompatibility and agree ownership.

C. Ask the sponsor to determine which department should own the system.

D. Proceed with planning and address ownership during transition, when the operating model is clearer.

Q39.

A newly promoted team lead confides in the project manager that they doubt they can handle an upcoming complex workstream and are considering asking to step back. Their performance to date has been strong. What is the MOST appropriate response?

A. Accept the request and assign the workstream to a more experienced lead.

B. Reassure them, express confidence in their capability, and offer to stand behind them as they apply the approach.

C. Arrange formal training on the technical content of the workstream.

D. Reduce the scope of the workstream so it is within their current comfort level.

Q40.

An organisation runs a hybrid programme. The adaptive team wants to add three newly identified features to its backlog. Separately, a regulator has issued a requirement affecting a baselined deliverable in the predictive workstream. What should the project manager do?

A. Process both through formal change control to maintain consistent governance across the programme.

B. Let the product owner prioritise the three features into the backlog, and raise a change request for the regulatory requirement.

C. Add all four items to the adaptive backlog so they can be delivered iteratively without disturbing the baseline.

D. Raise a change request for the three features and implement the regulatory requirement immediately, since compliance is mandatory.

Solutions

Q33 — Correct answer: A

A is correct. Supplier performance metrics and contract terms are quantifiable and recorded. Match the source to the knowledge type: records hold performance data accurately, where recollection does not.

B is incorrect. Prior project managers hold valuable context about the relationship, but that is the second step. Beginning with recollection risks building on partial memory of measurable facts.

C is incorrect. The supplier's own account of their performance is neither neutral nor evidenced.

D is incorrect. Registers hold raw, unvalidated lessons from those projects. They are a reasonable secondary source but do not contain the performance and contractual data being sought.

Q34 — Correct answer: B

B is correct. The barrier is cultural trust, and training that builds understanding of differing practices addresses the stated cause at a scale that reaches the whole programme.

A is incorrect. One-to-one meetings help individual relationships but are not scalable or systemic for a cross-regional team. Correct instinct, wrong scale.

C is incorrect. Reducing interdependency accommodates the problem by segregating along the lines causing it, reinforcing silos and undermining the collaboration the sponsor requires.

D is incorrect. Nothing indicates a language barrier. Members have stopped sharing, which concerns trust and comfort rather than vocabulary.

Q35 — Correct answer: B

B is correct. This is a genuine format preference from a stakeholder with a real information need, and it is accommodated at the level of method — a tailored summary — while the full report continues to satisfy the governance requirement. Both conditions are held.

A is incorrect. Satisfying a reporting requirement while the recipient reads only the first page means the information is not landing. Compliance with the process is not the same as effective communication.

C is incorrect. Coaching is the response to an awareness gap. This stakeholder is not questioning the value of oversight; they are describing a format constraint.

D is incorrect. Shortening for everyone imposes one stakeholder's preference on all audiences and may strip detail that governance and other recipients require.

Q36 — Correct answer: B

B is correct. Three independent reports establish a pattern worth acting on, but only one side has been heard. Meeting the individual privately to understand their perspective — explicitly to gather information rather than to solve — precedes any group action.

A is incorrect. Raising it in the team meeting exposes a pattern reported privately, puts the colleague on the spot without warning, and risks making discussions quieter still.

C is incorrect. A facilitation technique is a plausible eventual remedy, but applying it before understanding the cause treats a symptom and may be the wrong intervention.

D is incorrect. Escalating to a functional manager before speaking with the person is premature and converts a manageable team dynamic into a performance matter.

Q37 — Correct answer: C

C is correct. The objective is that future projects benefit, which requires the technique to become an organisational process asset in reusable form. Only the repository achieves that.

A is incorrect. The register holds raw lessons for this project, and the final report documents rather than institutionalises. Neither makes the technique reusable.

B is incorrect. Demonstrating to peers spreads knowledge but does not institutionalise it; it depends on who attended and who remembers.

D is incorrect. Endorsement alone does not update process assets. Approval without the artifact leaves nothing for a future team to use.

Q38 — Correct answer: B

B is correct. Two parties hold incompatible expectations about ownership. Facilitating them to surface the incompatibility and agree is the alignment action, and doing it in planning is far cheaper than discovering it at transition.

A is incorrect. Documenting both assumptions preserves the conflict rather than resolving it, and deferring to the steering committee escalates before any attempt at direct resolution.

C is incorrect. Asking the sponsor to decide takes responsibility that belongs to the project manager and produces an imposed answer rather than agreement.

D is incorrect. Deferring a known ownership conflict to transition guarantees it surfaces at the least convenient moment, with the operating model built on an unresolved assumption.

Q39 — Correct answer: B

B is correct. Strong performer, genuine crisis of confidence, no evidence of a capability gap. The mentoring response is to express confidence, give explicit permission to apply the approach, and make clear you stand behind them — which builds confidence through use rather than removing the challenge.

A is incorrect. Accepting the step-back at first request confirms the doubt and removes the development opportunity from someone whose record does not warrant it.

C is incorrect. Formal training addresses a knowledge gap. The stem describes confidence, not competence, and prescribing training misdiagnoses the stage.

D is incorrect. Reducing scope to fit a temporary confidence dip changes the project to accommodate a feeling, and signals that the concern was well founded.

Q40 — Correct answer: B

B is correct. Handling depends entirely on which workstream the change lands in. New features on the adaptive side are normal backlog refinement, ordered by the product owner without a control board. A change to a baselined predictive deliverable requires a change request and formal change control — the regulatory driver makes it necessary but does not make it pre-approved.

A is incorrect. Applying formal change control to adaptive backlog items defeats the purpose of choosing an adaptive approach for that workstream and slows the feedback loop it exists to create.

C is incorrect. Routing a baselined predictive change into the adaptive backlog to avoid the control board is the classic hybrid evasion.

D is incorrect. Both halves are inverted. Backlog items do not need change requests, and a mandatory requirement still requires impact analysis and authorisation before implementation.

Appendix — Rapid Reference

The eight tasks in one line each

Distinctions that decide items

Answer-selection sequence for a People item

7. Identify the actual question. What is being asked for — data, alignment, a decision, a capability? Narrative context is not the subject.
8. Eliminate concealment and dismissal. "Only if raised," "without informing," "regardless of impact on the relationship," and options that brush off a stated concern.
9. Check for a hard boundary. Harassment, discrimination, or comparable conduct concerns are escalated immediately and nothing else applies.
10. Check severity if it is a conflict. Levels 1–3 let the team resolve; Level 4 and above, intervene.
11. Test remaining options against scope. Does this scale to the breadth the stem describes?
12. Test against verb strength. Clarify, document, record, and organise do not deliver alignment, resolution, or outcomes.
13. Prefer the option that includes all affected parties over any that engages one side, adjudicates, or escalates.
14. Read every option to its final word. A qualifier — only, regardless, immediately, informally, without — frequently disqualifies an otherwise sound option.

Where the remaining risk sits

15. Task 8 — communication. Untested across fifteen live items. Highest unknown in the domain.
16. The accommodation trap. Discriminator 6 cost a live item and is the most counterintuitive rule here.
17. Source-to-knowledge-type matching. Quantifiable data belongs in records; the pull toward the human option is strong and wrong.
18. Leas' levels. The only place where "observe and do not intervene" is correct. Easy to over-apply the intervention instinct.
19. Task 5 volume. Highest-frequency task; the facilitate-align pattern is worth being able to recognise instantly.

PMP® 2026

Process Domain Complete Guide

All ten tasks · 41% of the exam · July 2026 ECO

Part 1 — Task-by-task reference, all ten Process tasks

Part 2 — Graphic interpretation: burndown, burnup, CFD, velocity, EVM

Part 3 — Agile framework reference

Appendix — Distinctions, formulas, answer-selection sequence

40 original practice questions with full option-by-option solutions

PMP 2026 — Process Domain Complete Guide

Built from: the July 2026 Exam Content Outline, a large body of practice items worked under timed conditions, and the complete Process reading set. Supporting concepts from the PMBOK Guide and the Agile Practice Guide.

Why this document exists

Process is 41% of the exam — the largest single domain, roughly 74 questions. It is also where preparation most often goes wide but shallow: candidates cover the familiar tasks (scope, schedule, quality) and leave the rest at a surface level. That pattern produces a middle-band result rather than a clear pass.

This document covers all ten tasks at the same level of detail, rather than concentrating on the few that feel most familiar.

What Process items actually test

Across timed practice, Process items turn on sequence and dependency far more often than on content recall — what must exist before this action makes sense?

How this document is organised

• Part 1 — all ten tasks, with the mechanics, named techniques, and traps for each. Four practice items per task.
• Part 2 — graphic interpretation reference. The 2026 exam introduced graphic-based questions, and Process is where they will appear: burndown, burnup, cumulative flow, velocity, earned value.
• Part 3 — agile framework reference, for recognition-format items.
• Appendix — formulas, distinctions, and answer-selection sequence.

Process Task 1 — Develop an Integrated Project Management Plan and Plan Delivery

Commonly under-prepared: development approach selection is heavily tested and frequently reduced to “predictive versus agile” without the tailoring logic.

ECO enablers

• Assess project needs, complexity, and magnitude.
• Recommend a project management development approach (predictive, adaptive/agile, or hybrid).
• Determine critical information requirements (e.g., sustainability).
• Recommend a project execution strategy.
• Create an integrated project management plan.
• Estimate work effort and resource requirements.
• Assess consolidated project plans for dependencies, gaps, and continued business value.
• Maintain the integrated project management plan.
• Collect and analyze data to make informed project decisions.

Choosing the development approach

Roughly 40% of exam items reflect predictive approaches and 60% adaptive or hybrid. Before most scenarios can be answered, you must establish which world you are in — the same event gets a different correct response depending on the workstream it lands in.

Where factors point in different directions, a weighted scoring matrix — rating how well each approach satisfies each factor — makes the trade-off explicit rather than intuitive.

Building the integrated plan

The plan is not one document. It is the consolidation of subsidiary plans — scope, schedule, cost, quality, resource, communications, risk, procurement, stakeholder engagement — plus the three baselines. Without integration you get duplicated effort, missed handoffs, and lost visibility.

20. Gather the pieces — identify stakeholders and teams, clarify objectives, develop the charter, assess complexity and magnitude, build a RACI, and establish how changes will be managed.
21. Break it down — decompose deliverables via WBS, ensure every task traces to a deliverable, sequence activities, identify dependencies, assign responsibility.
22. Schedule activities against resource availability.
23. Review the budget — the cost plan mirrors the WBS; every deliverable is accounted for; include contingency reserves.
24. Plan risk — identify early and assign named risk owners.
25. Define change controls — thresholds for acceptable change, escalation paths, approval workflows.
26. Review and validate with stakeholders, incorporate feedback, then lock commitments.

Estimation

Execution strategy

At initiation the most overlooked risk category is people and process, not technology. Handoffs between teams routinely fail to account for the receiving team's own priorities. The remedy is getting the interdependent parties in one room to align on a single strategy — which is itself a risk-identification exercise.

Where interdependent teams lack formal programme governance, one project manager acting informally as a cross-team coordinator prevents roadmaps drifting apart. Repeatedly pushing a constraint — especially a release date — is a critical risk, because it cascades into future projects, not just this one.

Practice

Q1.

A project manager is assigned to deliver a regulatory reporting platform. The statutory calculation rules are fixed and have not changed in six years. The user-facing dashboard, however, is being designed from ongoing user research and is expected to evolve. The organisation has delivered both waterfall and Scrum projects successfully. What should the project manager recommend?

A. A predictive approach throughout, since statutory requirements dominate and must be baselined.

B. A hybrid approach, applying predictive planning to the statutory reporting components and an adaptive approach to the dashboard.

C. An adaptive approach throughout, since ongoing user research means requirements will keep emerging.

D. Whichever approach the organisation used on its most recent successful platform project.

Q2.

A project manager determines that an adaptive approach best fits an upcoming mobile application project, and the organisation supports adopting it. Most of the team has only ever worked predictively. What should the project manager do next?

A. Request that the project be reassigned to a team experienced with adaptive delivery.

B. Use a predictive approach, since the team is experienced with it and will deliver more reliably.

C. Provide training on adaptive principles and mindset for the current team.

D. Replace the team members who lack adaptive experience.

Q3.

During planning for a remote infrastructure project, the project manager identifies that two specialist engineers are the only people in the organisation qualified to commission the equipment. The execution strategy currently assumes both are available throughout the installation window. What is the MOST significant gap?

A. The schedule should be compressed so the installation window is shorter.

B. There is no resource continuity plan defining what happens if either specialist becomes unavailable.

C. The specialists should be contractually committed to the project for its full duration.

D. Additional specialists should be recruited before the project begins.

Q4.

Three weeks into planning a predictive project, the project manager finds that the resource management plan assumes a specialist is available from month three, while the schedule sequences that specialist's activities beginning in month two. Both plans were developed by different leads and separately approved. What should the project manager do NEXT?

A. Instruct the schedule owner to move the activities to month three to match resource availability.

B. Escalate to the sponsor, since two approved plans cannot be reconciled at the project manager's level.

C. Assess the consolidated plans for dependencies and gaps, then resolve the conflict with both leads and update the integrated plan.

D. Proceed with execution and address the conflict if the specialist's availability actually becomes a constraint.

Solutions

Q1 — Correct answer: B

B is correct. Two components with genuinely different certainty profiles: fixed statutory rules (predictive) and an actively evolving interface (adaptive). The detail that the organisation has run both successfully removes capability as a constraint.

A is incorrect. Forcing the whole solution to the most rigid component means baselining a dashboard whose design is expected to change, guaranteeing repeated change requests.

C is incorrect. Forcing everything to the most fluid component. Statutory rules are fixed and known; treating them as emergent adds no value and risks compliance gaps.

D is incorrect. Precedent is never the basis for approach selection.

Q2 — Correct answer: C

C is correct. The approach fits the project and the organisation supports it, so the only gap is capability — and capability gaps are closed by building skill in the team you have. Training also prepares them for future projects, not just this one.

A is incorrect. Reassigning the project is disproportionate and impractical; experienced adaptive teams may not be available.

B is incorrect. Choosing the approach for team comfort rather than project fit inverts the rule. The project manager has already assessed adaptive as more suitable.

D is incorrect. Replacing people treats inexperience as disqualifying when it is addressable, and is disruptive.

Q3 — Correct answer: B

B is correct. An execution strategy that assumes critical resources remain available, with no defined failover, is a Plan A with no Plan B. Resource continuity planning names who steps in, from where, and how escalation works.

A is incorrect. Compressing the window increases the consequence of unavailability rather than mitigating it.

C is incorrect. A contractual commitment does not protect against illness, emergency, or competing organisational priority.

D is incorrect. Recruiting additional specialists may be impossible in the timeframe and does not constitute a continuity plan.

Q4 — Correct answer: C

C is correct. The enabler reads "assess consolidated project plans for dependencies, gaps." A conflict between subsidiary plans is precisely the integration work only the project manager performs, and resolving it with both owners before updating the plan is the correct sequence.

A is incorrect. Imposing one plan's assumption over the other without analysis. The schedule may be constrained for good reason.

B is incorrect. Reconciling subsidiary plans is core project manager work, well within your authority.

D is incorrect. Knowingly proceeding with an unresolved internal conflict defers a known problem to a more expensive moment.

Process Task 2 — Develop and Manage Project Scope

Commonly under-prepared: scope decomposition, and specifically when bottom-up beats top-down.

ECO enablers

• Define scope.
• Obtain stakeholder agreement on project scope.
• Break down scope.

Predictive scope vocabulary

Decomposition runs in either direction

Adaptive scope

Scope lives in the product backlog, continuously refined rather than baselined. The decomposition hierarchy runs epic → feature → story → task: an epic describes major functionality, features deliver interim value toward it, squads write stories from features, and stories break into tasks.

Two supporting concepts: acceptance criteria define what the story must satisfy, and the definition of done is the shared standard for completion. Anyone may write a story, but the team cannot work on it until they understand it.

Scope creep and gold plating

Validate Scope versus Control Quality

Protecting scope in practice

• Be the translator between intention and impact. A request to "just move the button down" may trigger a flow redesign, restarted testing, and recalibration. Most such requests are not malicious — they come from not seeing the backend. Your job is explaining the cost, not silently absorbing it.
• If it is not in writing, it does not exist. Especially across languages, cultures, and experience levels, where the same term is understood differently.
• Misunderstanding is perspective, not sabotage. "Dashboard" meant KPI charts to the business, filterable tables to IT, and a budget tracker to finance. Nobody was wrong. Validate with walkthroughs, mockups, and demos, not documents alone.
• Vagueness accepted at the offer stage is paid for later. Not asking the uncomfortable clarifying question to avoid losing the opportunity is a scope risk before the project even starts.
• Internal pressure is harder than client pressure. Sales promising a feature, a sponsor adding "just a small change." The three questions: Is it approved? Is it documented? What is the impact? One undocumented favour becomes a precedent.

Practice

Q5.

A project team is preparing to finalise the scope baseline for a data analytics platform. Previous email surveys produced vague responses, and stakeholders hold conflicting priorities regarding scope. The product owner wants alignment before approval and wants to avoid repeating ineffective techniques. What should the project manager do?

A. Ask each stakeholder to submit a ranked list of preferred deliverables for inclusion.

B. Facilitate a collaborative workshop to validate the scope and build consensus among stakeholders.

C. Ask the functional managers to provide deliverable lists for incorporation into the baseline.

D. Finalise the scope statement based on sponsor direction and circulate it for stakeholder signatures.

Q6.

A project team is eager to begin scheduling now that the scope statement is complete. In a scope planning meeting, functional managers say staff need to stay focused on technical work, while the business analyst is concerned that not all scope has been captured. What should the project manager do next regarding the WBS?

A. Use the schedule development process to identify activities and build the WBS from them afterwards.

B. Create the WBS from the scope statement and share it with the team during schedule development.

C. Use a bottom-up WBS approach in collaboration with the team to capture all scope efficiently.

D. Use a top-down WBS approach with functional managers to decompose the project into deliverables.

Q7.

A customer formally rejects an interim deliverable during a review, stating it does not meet expectations. The contract includes detailed acceptance criteria, and milestone payments are tied to approved deliverables. Several downstream tasks are blocked. The customer requests immediate rework. What should the project manager do FIRST?

A. Begin rework based on the customer's feedback to ensure a quick turnaround.

B. Conduct a joint review session with the customer to agree the specific changes needed.

C. Review the reason for rejection, verify the deliverable against the acceptance criteria, and determine whether the rejection is valid.

D. Document the rejection in the quality log and update the lessons learned register.

Q8.

During execution of a predictive project, a project manager discovers that a developer added an automated notification feature to a reporting module. No stakeholder requested it; the developer explains users will find it helpful and it took three days. What is the PRIMARY concern?

A. The feature should be retained but documented retroactively in the requirements traceability matrix.

B. Three days were diverted from baselined work, and unrequested functionality introduces untested risk without approved value.

C. There is no concern, since the cost was low and user experience improved.

D. The developer should have obtained the product owner's approval first.

Solutions

Q5 — Correct answer: B

B is correct. Email surveys — asynchronous, one-way — already failed, and the stem explicitly asks to avoid repeating ineffective techniques. A facilitated workshop is interactive communication, which is what complex, contested, consensus-requiring topics need. Facilitated workshops enable real-time clarification, validation, and consensus building.

A is incorrect. Ranked lists submitted individually are the survey again. With conflicting priorities you would receive incompatible rankings and no mechanism to reconcile them.

C is incorrect. Narrow input from functional managers is insufficient for full agreement; the scope baseline requires broader consensus.

D is incorrect. Sponsor-only approval undermines buy-in and does not ensure true agreement. Signatures on a document nobody agreed to are compliance, not consensus.

Q6 — Correct answer: C

C is correct. When completeness is the stated concern, bottom-up is the recommended approach — it surfaces work a top-down pass would miss. Developing the WBS with the team is what prevents missed scope and builds ownership.

A is incorrect. Activities should not drive the WBS; it reverses the process. The WBS feeds activity definition, not the other way round.

B is incorrect. Developing the WBS without involving relevant stakeholders, including the team, risks missing scope and undermines ownership — a common pitfall.

D is incorrect. Top-down is less effective than bottom-up when completeness is the concern, and excluding the team repeats the same participation gap.

Q7 — Correct answer: C

C is correct. The contract contains detailed acceptance criteria, so validity is a factual determination against a document, not a matter of opinion. Verify first; that tells you whether the problem is a defective deliverable or misaligned customer expectations, which are fixed differently.

A is incorrect. Rework before confirming the rejection is valid risks unnecessary changes, wasted effort, and scope creep.

B is incorrect. A joint session is helpful but should follow verification — you need to know which of the two problems you have before convening it.

D is incorrect. Lessons learned is a closing activity and does not address the immediate need to validate and correct.

Q8 — Correct answer: B

B is correct. This is gold plating. Effort belonging to baselined work was diverted, and the feature was never assessed for value, quality, security, or support impact, yet now exists in the product.

A is incorrect. Retroactive documentation legitimises unapproved work and addresses neither the diverted effort nor the unassessed risk.

C is incorrect. Low cost does not make unrequested work acceptable. The real cost is untested risk and the precedent set.

D is incorrect. This is a predictive project with a baseline; there is no product owner role, and the issue is unapproved change to a baselined deliverable rather than a missing signature.

Process Task 3 — Help Ensure Value-Based Delivery

One of the largest conceptual shifts in the 2026 outline. Success is reframed as value that was worth the effort and expense — a project can hit scope, schedule, and budget perfectly and still fail.

ECO enablers

• Identify value components with key stakeholders.
• Prioritize work based on value and stakeholder feedback.
• Assess opportunities to deliver value incrementally.
• Examine the business value throughout the project.
• Verify a measurement system is in place to track benefits.
• Evaluate delivery options to demonstrate value.

The value pipeline

Prioritising by value

Stories are often aggregated into themes — discrete sets of functionality valued by users — and prioritised relative to one another to form a release plan. The product owner owns prioritisation, supported by the team.

Discovering what value means to this customer

When you do not ask, you assume — and assumptions produce deliveries that are technically correct and practically useless. A Wednesday delivery rather than Tuesday is not a whim if that is the only day regional staff are on site.

Measuring value

Earned value measures cost and schedule efficiency, not value. Supplement with measures such as net promoter score, return on investment, benefits realised index, safety records, and community impact.

Note the contrast with the risk domain, where silence is a warning sign. During a rollout requiring active engagement, silence signals disengagement. After a clean handover with no friction reported, silence signals value. Read which situation the stem describes.

Saying no as value delivery

Refusing a shortcut can be the highest-value action available. Declining to leave equipment with a security guard because a guard cannot inspect or approve delayed handover by 24 hours and preserved a proper acceptance. Refusing to deliver generators to an unpowered site prevented equipment damage that would have been blamed on the project. Neither appears in a report; both protected value.

Practice

Q9.

An agile team has limited capacity for the coming release. Among the candidate items is a technical spike that generates little direct revenue but would resolve a major architectural uncertainty affecting three later features. Two revenue-generating features are also candidates. How should the product owner approach prioritisation?

A. Prioritise the two revenue-generating features, since financial value is the primary measure of business value.

B. Evaluate all three against value, cost including delay cost, knowledge created, and risk removed.

C. Prioritise the spike first, since technical risk always outranks feature delivery.

D. Split capacity evenly across all three so that each stream progresses.

Q10.

A project delivers a reporting module that meets every documented requirement and passes all tests. Three weeks after handover the client reports that their team has reverted to the previous manual process because the output cannot be imported into their existing system. What does this MOST clearly illustrate?

A. A quality failure, since the deliverable did not meet its specification.

B. An output was delivered but no outcome or value was realised, because the deliverable did not fit the client's operating context.

C. A training gap, since the client's team was not shown how to use the new output.

D. A change control failure, since the import requirement was never formally raised.

Q11.

A sponsor asks the project manager to demonstrate that a completed adaptive project delivered value. The project met its schedule and cost baselines, and all sprints produced accepted increments. What additional evidence BEST demonstrates value was delivered?

A. Cost performance index and schedule performance index for each sprint.

B. The number of story points accepted across the project.

C. Evidence that the increments were released and produced measurable benefits and stakeholder outcomes.

D. Confirmation that all increments met the definition of done.

Q12.

A vendor is preparing to ship equipment to a customer site. The contract specifies delivery to the site gate. The driver, wanting to be helpful, moves the pallets inside the compound to a location closer to the customer's storage area. The ground is unstable, a pallet tips, and goods are damaged. What is the PRIMARY project management failure?

A. Inadequate site survey, since the ground conditions were not assessed beforehand.

B. Delivering beyond the contracted scope without approval, which is noncompliance rather than added value.

C. Insufficient packaging, since the goods should have withstood normal handling.

D. Poor driver training on handling procedures at customer sites.

Solutions

Q9 — Correct answer: B

B is correct. The four-factor model exists precisely for this situation. A spike with low direct revenue but high risk-removal value affecting three downstream features may well outrank a modest revenue feature once knowledge and risk are weighed alongside value and cost.

A is incorrect. Financial value usually dominates the conversation, which is why the model exists — knowledge and risk are explicitly named as critical additional factors.

C is incorrect. Reverses the error rather than correcting it. Technical risk does not automatically outrank everything; it is one of four factors to weigh.

D is incorrect. Splitting capacity evenly abandons prioritisation entirely and is likely to deliver three partial items instead of finishing anything.

Q10 — Correct answer: B

B is correct. The deliverable satisfied specification, so an output exists. But nobody uses it, so no outcome occurred and no value was realised. The failure is that value was defined from the delivery team's perspective rather than discovered in the client's operating context.

A is incorrect. It met specification and passed testing. Quality, defined as conformance to requirements, was achieved — which is exactly what makes this a value question rather than a quality one.

C is incorrect. The problem is not that they cannot operate it; it is that the output is technically incompatible with their system.

D is incorrect. Framing it as a missed change request places the fault on the client for not stating a requirement, when identifying context-specific needs is the delivery team's responsibility.

Q11 — Correct answer: C

C is correct. Accepted increments are outputs. Value requires release into use and measurable benefit — the pipeline runs outputs to outcomes to value, and only the last step demonstrates value was delivered.

A is incorrect. CPI and SPI measure cost and schedule efficiency. A project can be perfectly efficient and deliver nothing of value.

B is incorrect. Story point counts are an activity measure — a vanity metric that reflects volume of work, not benefit delivered.

D is incorrect. The definition of done confirms increments were complete to standard. It says nothing about whether they were released or produced benefit.

Q12 — Correct answer: B

B is correct. The contract specified the site gate. Moving goods beyond that point, however well intentioned, is delivery outside the agreed scope without approval — and the client was angry both about the damage and about the location deviation itself. Doing more without approval means doing it wrong.

A is incorrect. The ground conditions inside the compound were not the vendor's to survey, because delivery was never contracted to that location.

C is incorrect. Packaging adequate for the contracted delivery point is not the failure; the goods were taken somewhere they were never meant to go.

D is incorrect. Handling training is a contributing factor at most. The root failure is exceeding contracted scope unilaterally.

Process Task 4 — Plan and Manage Resources

ECO enablers

• Define and plan resources based on requirements.
• Manage and optimize resource needs and availability.

Resources means people and physical assets — equipment, materials, facilities. Physical resources carry procurement lead times; people carry availability, skill, and competing-priority constraints.

Responsibility assignment

RACI — Responsible (does the work), Accountable (owns the outcome — only one per row), Consulted (two-way input), Informed (one-way updates). The single-accountable rule is a recurring exam point.

Resource optimisation in predictive scheduling

Float calculation is a prerequisite to either technique — you cannot smooth within flexibility you have not measured. After adjusting, review allocation across all activities to confirm an even spread and reduced idle time.

Agile capacity planning

• Ideally one squad delivers a project end to end — design, build, test, deploy — with minimal outside dependency. As scope grows, several squads are needed, coordinated as a solution or agile release train.
• Capacity must account for non-project work. Squads typically carry post-production maintenance, vulnerability management, and break-fix responsibilities alongside project delivery. That standing load must come off available capacity before commitments are made.
• Program increment (PI) planning is where capacity planning happens, spanning roughly five to six sprints. Squads review prioritised features, write stories, assign story points for complexity, and commit against historical velocity.

A worked illustration: a feature decomposes into stories totalling 16 points. The squad's historical velocity is 10 points per two-week sprint, so the feature needs two sprints — about four weeks — and the 20 points of capacity across those sprints leaves 4 points of slack for reduced availability, or for pulling forward stories from another feature.

Managing resource conflict

For scheduling purposes, also plan for holidays, vacation periods, and known absences — including the tendency to take an extra day after a holiday — and establish whether redundancy exists for critical roles. If one QA analyst is a single point of failure, discuss the schedule with them and their functional manager to surface competing deadlines early.

Artificial intelligence in resource allocation

AI genuinely fits here: forecasting demand from historical completion times and workload patterns, real-time reallocation as conditions shift, and dashboards tracking utilisation rate, predicted bottlenecks, and cost efficiency.

Practice

Q13.

A project manager is planning capacity for an adaptive project. The assigned squad has a historical velocity of 30 story points per two-week sprint. The squad also handles production support for two existing systems, which consumes roughly 20% of their time. The upcoming feature set totals 120 story points. How many sprints should the project manager plan for?

A. Four sprints, based on 120 points divided by the historical velocity of 30.

B. Five sprints, because the production support load reduces effective capacity below historical velocity.

C. Four sprints, with the production support absorbed into existing slack.

D. Six sprints, to allow contingency for unknown work.

Q14.

A project manager finds that two activities scheduled concurrently both require the same specialist equipment, which is available only for one at a time. Both activities sit on the critical path. What technique should the project manager apply?

A. Resource smoothing, adjusting within available float so the end date is preserved.

B. Resource levelling, adjusting the schedule to the resource constraint even though the end date may change.

C. Fast-tracking, running the activities in parallel with partial overlap.

D. Crashing, adding resources to shorten both activity durations.

Q15.

A functional manager has repeatedly reassigned a key engineer from the project to unrelated operational work, and project progress is suffering. What is the BEST first action?

A. Escalate to the sponsor and request that the engineer be assigned full time.

B. Have a direct conversation with the functional manager, explaining the impact and negotiating availability.

C. Redistribute the engineer's project work across other team members.

D. Document the situation in the risk register and monitor.

Q16.

A project manager is assembling resources for a large adaptive programme requiring front-end, back-end, data, and integration work. What approach BEST reflects agile resource planning?

A. Request individual specialists in each discipline and assign them to workstreams.

B. Request existing cross-functional squads with relevant domain experience and known delivery history, coordinated as a release train.

C. Form a new team from the strongest available individuals in each discipline.

D. Assign one squad and extend the timeline to accommodate the broader scope.

Solutions

Q13 — Correct answer: B

B is correct. Historical velocity of 30 assumes normal conditions, but standing operational work must be accounted for in available capacity. With roughly 20% consumed by production support, effective capacity is closer to 24 points per sprint, so 120 points needs five sprints rather than four.

A is incorrect. Dividing scope by raw historical velocity ignores the standing non-project load the squad carries, which is explicitly part of capacity planning.

C is incorrect. Assuming support fits into unstated slack is exactly the assumption that produces overcommitment. The load is known and should be planned for.

D is incorrect. Six sprints adds arbitrary padding rather than calculating against known constraints. Contingency should be reasoned, not guessed.

Q14 — Correct answer: B

B is correct. A hard resource constraint that cannot be satisfied concurrently requires levelling — adjusting the schedule to fit resource availability, accepting that the critical path and end date may move.

A is incorrect. Smoothing works only within available float. Both activities are on the critical path, which by definition has no float to smooth within.

C is incorrect. Fast-tracking runs activities in parallel — the opposite of what a single shared resource permits.

D is incorrect. Crashing adds resources to compress duration, but the constraint is a single piece of equipment that cannot be duplicated by adding people.

Q15 — Correct answer: B

B is correct. In a matrix organisation the functional manager controls the engineer's time. Direct, collaborative negotiation at your own level is both the appropriate first step and within your authority.

A is incorrect. Escalating before attempting direct resolution is premature and undermines your standing with the manager you will keep working with.

C is incorrect. Redistributing the work treats the symptom, quietly overloads the rest of the team, and surrenders a key resource without a conversation.

D is incorrect. Documenting without acting is passivity. The register is not where problems go to be ignored.

Q16 — Correct answer: B

B is correct. Agile resourcing selects squads, not individuals — intact teams with domain expertise and an established velocity, which is what makes capacity forecasting possible. Multiple squads on a large programme are coordinated as a solution or release train.

A is incorrect. Requesting individuals and assigning them to workstreams is the predictive resourcing model, and it discards the delivery history that makes velocity-based planning work.

C is incorrect. A newly formed team of strong individuals has no shared velocity and must work through forming, storming, and norming before performing — which is precisely the cost that using intact squads avoids.

D is incorrect. Extending the timeline for a single squad ignores that the scope spans disciplines beyond one squad's capability.

Process Task 5 — Plan and Manage Procurement

Note for anyone studying from older material: the negotiation enablers moved into this task from People in the 2026 outline.

ECO enablers

• Plan procurement.
• Execute a procurement management plan.
• Select preferred contract types.
• Evaluate vendor performance.
• Verify objectives of the procurement agreement are met.
• Participate in agreement negotiations.
• Determine a negotiation strategy.
• Manage suppliers and contracts.
• Plan and manage the procurement strategy.
• Develop a delivery solution.

Contract types and risk allocation

A second, independent dimension: who specifies the requirement

This is not the same axis as fixed-price versus cost-reimbursable. That axis governs how payment scales; this one governs who defines the requirement and therefore who bears the risk of getting the estimate wrong. They combine.

Solicitation and definition

• SOW / TOR — describes what is being procured in enough detail to be priced.
• RFI — market intelligence; you are not buying yet. RFQ — price-driven, for well-defined comparable items. RFP — used when the solution is not fully defined and you want sellers to propose an approach.
• Source selection criteria — agreed and documented before responses arrive.
• Make-or-buy analysis — decide whether to build internally or procure.

Selecting and evaluating vendors

Where multiple internal groups depend on the outcome, gather requirements from all affected teams before drafting the RFP, shortlist against those consolidated requirements, and run interviews where every affected team can question the shortlisted vendors. Surveying those groups for consensus before recommending both improves the decision and surfaces risks early. Final authority may still rest with senior leadership — inclusive input and final decision rights are different things.

The five-step vendor performance evaluation

27. Define project success — what does success mean for this project?
28. Choose metrics derived from those success factors, ideally a mix of quantitative and qualitative.
29. Confirm the baseline for each metric. Where no historical data exists, baseline against contractual versus actual performance.
30. Track performance against baseline.
31. Analyse and communicate results, including feedback to the vendor for subsequent reviews.

Repeat engagement builds a trust bank — verified knowledge of who reliably delivers what, which a CV cannot tell you. That accumulated performance history is an organisational asset, and like other institutional knowledge it must be deliberately carried forward rather than assumed to persist.

Negotiation

Prepare before you negotiate: know your objectives and their relative priority, know your walk-away point and alternatives, and understand the other party's interests rather than only their stated position. A supplier holding firm on unit price may be flexible on payment terms, delivery schedule, scope of services, volume, or contract duration.

Managing contracts and disputes

Alternative dispute resolution runs in escalating order: negotiation (parties talk directly, no third party) → mediation (neutral third party facilitates; parties still decide) → arbitration (neutral third party issues a binding decision) → litigation (courts; the last resort once other means are exhausted).

Two field cautions

Fixed-price commitments made before project manager involvement are common in service industries — pricing locked and promises made by sales, then handed over. When the commitment proves undeliverable, go directly to whoever made it and force the choice: either you reset the client's expectations or I will. Never absorb it quietly through unplanned overtime. Getting involved earlier in the lifecycle almost always improves outcomes.

Over-delivering against a contract creates an expectation ratchet. Once end users experience a service level above what was contracted, returning to the agreed level is perceived as a service reduction — even though you are now simply meeting the agreement. This is a distinct consequence from the cost of gold plating.

Practice

Q17.

An organisation needs a multi-year facilities support agreement. The scope of services is well defined and stable, but the contract spans five years in a market where energy and labour costs have been volatile. Which contract type is MOST appropriate?

A. Cost plus award fee, so the buyer can reward the supplier for managing volatility.

B. Firm fixed price, so the supplier absorbs all price movement across the term.

C. Fixed price with economic price adjustment, so a defined index governs price movement.

D. Time and materials, so pricing tracks actual market conditions.

Q18.

A client contracts a facilities provider by specifying the exact number of security personnel required per shift. Midway through the contract, the client concludes that the specified headcount is insufficient for the coverage they actually need. Who bears the risk of the incorrect calculation?

A. The provider, since they are responsible for delivering effective security coverage.

B. The client, because this is an input-based contract in which the client specified the inputs.

C. Both parties equally, since the contract is silent on adequacy of coverage.

D. The provider, unless the contract explicitly transfers the risk to the client.

Q19.

A supplier notifies a project manager two days before final delivery that prices must be renegotiated or shipment will be withheld. The components are critical and the timeline is at risk. What should the project manager do FIRST?

A. Agree to renegotiate to avoid delay and additional costs.

B. Initiate legal action for breach of contract.

C. Review the current contract for clauses on pricing adjustment and renegotiation rights.

D. Engage alternative vendors to assess feasibility of sourcing the remaining components.

Q20.

A project manager is evaluating three shortlisted vendors for a specialist engineering package. Which approach BEST reflects sound procurement practice?

A. Compare the three quoted prices and shortlist further on cost, then verify capability of the lowest bidder.

B. Confirm which vendors have the required skills and capability for this specific work, then negotiate commercial terms.

C. Select the vendor with the longest relationship with the organisation to reduce onboarding risk.

D. Request revised quotes from all three and select whichever offers the largest reduction.

Solutions

Q17 — Correct answer: C

C is correct. Stable, well-defined scope points to the fixed-price family. The complication is a long term with volatile input costs, which is exactly the condition FP-EPA exists to handle — a pre-agreed index adjusts price so neither party carries the full market risk.

A is incorrect. Cost-reimbursable arrangements suit uncertain scope. Scope here is stable, so shifting cost risk to the buyer is unnecessary.

B is incorrect. FFP across five volatile years forces the supplier either to price in a large risk premium or to face losses that threaten performance.

D is incorrect. T&M suits undefined scope and short engagements, not a well-defined multi-year service scope.

Q18 — Correct answer: B

B is correct. The client specified the input — headcount per shift — and the provider supplied exactly what was specified. In an input-based contract, the risk that the specified input proves insufficient rests with the party that specified it.

A is incorrect. The provider would bear calculation risk under an output-based contract, where the client specifies the required service level and the provider determines the resourcing.

C is incorrect. The risk allocation follows from the contract structure, not from silence on a particular clause.

D is incorrect. This inverts the default. In an input-based arrangement the client already holds the calculation risk without needing an explicit transfer clause.

Q19 — Correct answer: C

C is correct. Before conceding, escalating, or seeking alternatives, establish what the agreement actually permits — pricing adjustment rights, renegotiation provisions, and remedies for failure to ship. This typically involves legal and procurement, and it determines every subsequent option.

A is incorrect. Immediate renegotiation without analysing the contract undermines contractual leverage and sets a negative precedent for future dealings.

B is incorrect. Legal action is a last resort, not a first step. It consumes time and resources and escalates conflict unnecessarily.

D is incorrect. Sourcing alternatives may be impossible or may breach the existing agreement — which you cannot know until the contract has been reviewed.

Q20 — Correct answer: B

B is correct. Capability screening precedes commercial negotiation. Establishing that a vendor can actually deliver this specific work, then negotiating terms, protects against selecting on price alone and avoids wasting negotiation effort on vendors who cannot perform.

A is incorrect. Leading with price and verifying capability afterwards inverts the sequence and risks anchoring on a bidder who cannot deliver.

C is incorrect. Relationship length is not a substitute for verified capability on this particular scope, though accumulated performance history is a legitimate input.

D is incorrect. Driving all three toward discounting focuses entirely on cost and ignores whether any of them can perform the work.

Process Task 6 — Plan and Manage Finance

ECO enablers

• Analyze project financial needs.
• Quantify risk and contingency financial allocations.
• Plan spend tracking throughout the life cycle.
• Plan financial reporting.
• Anticipate future finance challenges.
• Monitor financial variations and work with the governance process.
• Manage financial reserves.

The budget stack

Activity cost estimates aggregate into work package costs; work packages plus contingency reserves form the cost baseline; the cost baseline plus management reserve forms the total budget.

Selection and value metrics

• NPV — higher is better; positive means worth doing. IRR — higher is better. Payback period — shorter is better. BCR — above 1 is good.
• Sunk cost is irrelevant. Decisions rest on remaining cost against remaining benefit. Money already spent is gone whether you continue or stop.
• Beyond financial return, value can be measured through net promoter score, benefits realised index, safety records, and community impact — cost efficiency and value delivery are different axes.

Budgeting under volatility

A worked field example: a 12-month project achieved 98% on-time delivery and 0.6% budget overrun using scenario budgeting reviewed quarterly, an explicit and approved 12% buffer, a delegated local decision threshold for emergencies, and jargon-free weekly reporting.

Hidden costs the report does not show

Financial control by signal

Traditional accounting reports what has already happened. Control requires foresight, which means defining triggers in advance:

The mechanism matters as much as the thresholds. One project manager reported "all good" monthly while costs crept 10% each period — drivers were rerouting for legitimate security reasons and not reporting it. Without a defined signal, that reads as unexplained inefficiency rather than a manageable, explicable cost.

Two supporting practices: a delegated local decision threshold for emergencies (one project secured a €5,000 limit without prior sign-off), and a short reality sync — fifteen minutes, no formal presentation, three questions: what has changed on the ground, where do we risk a cash-flow gap, and what needs a decision now? That practice halved approval times.

Cost control and integrity

CPI has a secondary use beyond performance tracking: detecting billing inconsistency. A consultancy billed senior-engineer rates at $150/hour while a junior at $50/hour performed the work. Stricter statements of work, invoice review, and random audits corrected it, and CPI was what flagged the anomaly.

Where scope creep drives cost increases, linking each change request to a cost-benefit scoring matrix at the change control board ensures additional expense delivers proportionate value rather than simply being absorbed.

Practice

Q21.

A project completed under budget with unused contingency reserves. The customer requests that the remaining funds be applied to team-building activities for the operational team. What should the project manager do?

A. Approve the request, since the funds are available within the approved budget.

B. Close the project financials and reject the request.

C. Submit the customer's change request for review through formal change control procedures.

D. Record the request in the lessons learned register and inform the customer of project closure.

Q22.

A project has spent $800,000 of a $1,000,000 budget. Analysis shows completing the work will cost a further $500,000, while the expected benefit on completion has fallen to $300,000 following a market shift. The sponsor argues that abandoning the project would waste the $800,000 already invested. What should the project manager recommend?

A. Continue, since stopping would waste the investment already made.

B. Recommend terminating the project, since remaining cost exceeds remaining benefit.

C. Reduce the remaining scope so the project completes within the $200,000 left.

D. Continue, since stopping midway damages team morale and stakeholder confidence.

Q23.

A project operating across several countries faces exchange rate movements of up to 18% within a single month and fuel prices that have risen 40% in one quarter. The organisation requires a budget submission for the coming year. What approach BEST addresses this?

A. Submit a fixed budget based on current rates and request changes if conditions move.

B. Submit optimistic, realistic, and pessimistic budget scenarios, reviewed on a defined cycle.

C. Submit a budget with a large single contingency line to absorb any movement.

D. Delay budget submission until exchange rates stabilise.

Q24.

An invoice from a critical supplier has been pending internal approval for three weeks. The supplier has stopped delivery, the installation crew is idle in a hotel, and paid warehouse space sits unused. What does this situation MOST clearly demonstrate?

A. A supplier performance failure requiring contract remedies.

B. The cost of delay and idle cost exceeding the value of the payment being withheld, indicating a need for defined approval-time triggers.

C. A budgeting failure, since insufficient funds were allocated to the supplier.

D. A procurement failure, since the supplier should have continued delivery in good faith.

Solutions

Q21 — Correct answer: C

C is correct. Any request to alter the project budget after completion goes through integrated change control, even when the project is under budget or contingency is unused. The change control board evaluates it against deliverables, project documents, and the plan.

A is incorrect. Approving because funds happen to be available skips evaluation entirely. Availability is not authorisation, and this is new scope rather than an identified risk contingency was set aside for.

B is incorrect. Rejecting outright disregards proper evaluation and may damage the stakeholder relationship. The project manager does not hold unilateral authority to reject a change request.

D is incorrect. Recording the request archives it without following the process required for budget modification — documentation substituting for action.

Q22 — Correct answer: B

B is correct. Decisions rest on remaining cost against remaining benefit: $500,000 to obtain $300,000 destroys $200,000 of value. The $800,000 already spent is sunk and irrelevant to the decision.

A is incorrect. This is the sunk cost fallacy stated plainly. The money is gone whether the project continues or stops.

C is incorrect. The $300,000 benefit assumed the complete deliverable. Cutting scope to fit the remaining budget almost certainly reduces that benefit further, and invents a favourable assumption the scenario does not support.

D is incorrect. Morale and confidence are real considerations, but continuing a value-destroying project damages credibility more than stopping one for sound reasons.

Q23 — Correct answer: B

B is correct. Scenario-based budgeting is the appropriate response to genuine, quantified volatility. Three scenarios reviewed on a cycle give the organisation visibility of the range rather than false precision, and make the trigger points for action explicit.

A is incorrect. A fixed budget in this environment will be wrong almost immediately, and reactive change requests arrive after the damage rather than before.

C is incorrect. A single large contingency line obscures which factors are driving exposure and invites challenge as padding, without providing the visibility scenarios give.

D is incorrect. Waiting for volatile rates to stabilise defers planning indefinitely; volatility is the operating condition, not a temporary state.

Q24 — Correct answer: B

B is correct. Idle crew, unused paid warehouse space, and halted delivery are idle costs and cost of delay, and they are almost certainly exceeding the value of the payment being withheld. The corrective mechanism is a defined trigger — an invoice pending beyond a threshold escalating automatically.

A is incorrect. The supplier stopped delivering because they have not been paid for three weeks, which is a reasonable commercial response rather than a performance failure.

C is incorrect. Nothing indicates insufficient funds were budgeted; the funds exist and the approval is stuck.

D is incorrect. Expecting continued delivery on an unpaid three-week-old invoice relies on goodwill rather than addressing the internal process causing the problem.

Process Task 7 — Plan and Optimize Quality of Products and Deliverables

Commonly under-prepared: the split between assurance and control, and the cost-of-quality categories.

ECO enablers

• Gather quality requirements for project deliverables.
• Plan quality processes and tools.
• Execute a quality management plan.
• Help ensure regulatory compliance.
• Manage cost of quality (CoQ) and sustainability.
• Conduct ongoing quality reviews.
• Implement continuous improvement.

Two aspects of quality, not one

Quality versus grade

Quality is the degree to which characteristics fulfil requirements — fitness for purpose. Grade is a category of technical characteristics for items with the same functional use.

Quality assurance versus quality control

Prevention over inspection

Cost of quality

Investment in conformance is normally far cheaper than non-conformance, and external failure is the most expensive category of all. Where historical data shows escaped defects costing many times the inspection that would have caught them and many times again the prevention that would have avoided them, prevention is the economically rational allocation.

Tools

• Cause-and-effect (Ishikawa / fishbone) — structures the search for root causes by category. Can also be used before implementation to identify potential failure points.
• Five Whys — iterative questioning from symptom to root cause.
• Pareto chart — the vital few; 80/20 prioritisation of where to act.
• Control chart — process stability. Specification limits come from the customer; control limits come from the process. A point outside control limits means the process is out of control. The rule of seven: seven consecutive points on one side of the mean signals a non-random pattern requiring investigation, even though every point is within limits.
• Histogram, scatter diagram, checksheet, flowchart — supporting analysis tools.
• Audits — quality assurance; confirm processes are being followed.
• Benchmarking — comparison against comparable organisations.

Continuous improvement and sustainability

The enabler pairs cost of quality explicitly with sustainability: material waste, energy consumption, rework-driven emissions, and end-of-life impact are quality considerations. Kaizen (many small continuous improvements) and PDCA (Plan-Do-Check-Act) are the improvement cycles. PDCA is the structured answer when a stem asks for a systematic approach to problem solving against a measurable target.

Practice

Q25.

Stakeholders on a medical device project raise concerns that current work processes may no longer align with documented quality expectations after the steering committee pushed to accelerate delivery. What should the project manager do FIRST?

A. Conduct inspections and statistical sampling of completed components to verify compliance with documented standards.

B. Perform a quality audit to evaluate adherence to defined processes and identify improvement opportunities.

C. Integrate new assurance and control tools into the project management plan based on the concerns raised.

D. Escalate the unresolved concerns to the sponsor and document them in the issue log.

Q26.

A manufacturing team sets a goal of reducing a production line defect rate by 20% over the next quarter. The sponsor asks for a structured approach to problem solving and informed decision making. What should the project manager do?

A. Develop a contingency plan with defined trigger conditions and add it to the risk management plan.

B. Empower team members to make decisions within their areas of expertise for faster response.

C. Offer training to build the team's problem-solving skills for sustained improvement.

D. Iterate through the plan-do-check-act cycle to refine processes and drive incremental improvement.

Q27.

A control chart for a filling process shows every measurement within the upper and lower control limits. However, the last nine consecutive measurements fall above the mean. What is the MOST appropriate interpretation?

A. The process is performing well, since no control limit has been exceeded.

B. The control limits should be recalculated, since the process mean appears to have shifted.

C. A non-random pattern is present, indicating the process should be investigated despite remaining within limits.

D. The measurements exceed specification limits and the affected units should be scrapped.

Q28.

A software project is experiencing high defect volumes discovered during system testing. Testing costs have risen 40% over three months and the schedule has slipped twice due to rework. The test manager proposes hiring two additional testers. What should the project manager do?

A. Approve the additional testers to increase throughput and clear the defect backlog.

B. Conduct root cause analysis on the defects and improve the upstream development process generating them.

C. Accept the defect rate as characteristic of the technology and build additional rework time into the schedule.

D. Reassign development work to the most experienced engineers to reduce defect injection.

Solutions

Q25 — Correct answer: B

B is correct. The concern is explicitly about process alignment, which is quality assurance territory. A quality audit is performed during execution and targets how work is being done — exactly what the stakeholders are questioning.

A is incorrect. Inspections and sampling assess outputs, not processes. Valid techniques, wrong target for a process-conformance concern.

C is incorrect. Integrating new tools into the plan is a planning activity, and it presumes a fix before anyone has evaluated current execution. The scenario asks whether existing processes are being followed, not for the plan to be redesigned.

D is incorrect. Escalation reflects issue management rather than quality assurance, and it skips the assessment that would establish whether there is a problem.

Q26 — Correct answer: D

D is correct. The stem asks for a structured approach to problem solving with a specific measurable target. PDCA is the named cyclical methodology for exactly that — plan the change, implement, check against the 20% target, act on the result, repeat.

A is incorrect. Contingency planning is reactive risk management for events that may occur; it is not a structured problem-solving approach for an already-identified defect problem.

B is incorrect. Empowerment is always sound practice but is not a structured approach to enhancing project outcomes.

C is incorrect. Training is likewise a good idea but is not itself the structured problem-solving method the sponsor asked for.

Q27 — Correct answer: C

C is correct. The rule of seven. Seven or more consecutive points on one side of the mean indicates a non-random pattern — the process has drifted or something systematic has changed — warranting investigation even though no limit has been breached.

A is incorrect. Staying within control limits is necessary but not sufficient. Control charts also detect patterns, and this is a clear one.

B is incorrect. Recalculating limits to fit a drifting process disguises the drift instead of investigating its cause.

D is incorrect. The scenario refers to control limits, which come from the process, not specification limits, which come from the customer. Nothing indicates specification has been breached.

Q28 — Correct answer: B

B is correct. Prevention over inspection. Defects are being generated upstream; adding testers increases detection capacity while the source continues unchanged, so cost and rework keep growing. Root cause analysis and process improvement address the actual driver.

A is incorrect. More inspection is the classic symptom-treating answer — it raises appraisal cost without reducing defect injection.

C is incorrect. Building rework into the schedule institutionalises the waste and abandons improvement.

D is incorrect. Concentrating work with strong individuals is an unsustainable band-aid that leaves the process defect unresolved and creates a single point of dependency.

Process Task 8 — Plan and Manage Schedule

ECO enablers

• Prepare a schedule based on the selected development approach.
• Coordinate with other projects and operations.
• Estimate project tasks (milestones, dependencies, story points).
• Utilize benchmarks and historical data.
• Create a project schedule.
• Baseline a project schedule.
• Execute a schedule management plan.
• Analyze schedule variation.

Two kinds of schedule

The predictive approach frequently needs to be executed with an adaptable mindset — change control handles disruptions after they occur, but preventing the need for change in the first place produces a schedule you can defend.

Building a defensible predictive schedule

Decompose activities properly

Sequence with deliberate overlap

Estimate and allocate realistically

• Factor in holidays and vacation periods, including the tendency to take an extra day after a holiday, and known events such as annual conferences.
• Establish whether redundancy exists for critical roles. If one analyst is a single point of failure, discuss the schedule with them and their functional manager to surface competing deadlines.
• Plan explicitly for external stakeholder and vendor delay where there is a track record of it.

Compression techniques

Critical path

The longest sequence of dependent activities determining the earliest completion date. Activities on it have zero float. Knowing the critical path tells you where to prioritise resources and where a delay directly moves the end date — and it is the reason resource levelling can change the completion date while smoothing cannot.

Earned value

Selecting the EAC formula

Velocity and adaptive forecasting

Practice

Q29.

A project has BAC = $500,000. Current status: PV = $200,000, EV = $150,000, AC = $180,000. Analysis shows the cost overrun was caused by a one-time customs delay that will not recur, and the remaining work is expected to proceed as originally budgeted. What is the EAC?

A. $530,000

B. $600,000

C. $500,000

D. $740,000

Q30.

An agile team has completed three sprints, delivering 22, 31, and 27 story points. The sponsor asks the project manager to forecast the release date for the remaining 300 points of backlog. What should the project manager do?

A. Use the average of 26.7 points per sprint to forecast approximately eleven more sprints.

B. Use the highest observed velocity of 31 points to give the sponsor the earliest achievable date.

C. Explain that velocity has not yet stabilised and provide a forecast range, refining it as velocity settles.

D. Use the lowest observed velocity of 22 points to give a conservative commitment.

Q31.

While defining activities for a system migration, the technical lead lists a single activity: "migrate data to the new platform," estimated at three days. What is the MOST significant concern?

A. Three days is likely an underestimate for a migration of this type.

B. The activity compresses several distinct work steps — migration downtime, quality assurance testing, and error correction — that should appear separately on the schedule.

C. The activity should be assigned to more than one resource to reduce risk.

D. The activity has not been linked to a work package in the WBS.

Q32.

A project manager reviewing a draft schedule finds that every activity is linked to the next by a finish-to-start dependency, and several depend on deliverables from an external vendor with a history of late delivery. What should the project manager do?

A. Accept the schedule, since finish-to-start is the standard dependency type.

B. Add buffer time after each vendor-dependent activity to absorb potential delay.

C. Look for opportunities to overlap activities and reduce dependencies on the external vendor where possible.

D. Escalate the vendor's delivery history to procurement before finalising the schedule.

Solutions

Q29 — Correct answer: A

A is correct. "Will not recur" plus "remaining work proceeds as originally budgeted" points to the atypical-variance formula: EAC = AC + (BAC − EV) = 180,000 + (500,000 − 150,000) = $530,000. The past overrun is absorbed; everything remaining runs at budgeted rates.

B is incorrect. $600,000 is BAC ÷ CPI (500,000 ÷ 0.833) — the correct answer to a scenario where performance continues, which is not what this stem describes. This is the primary trap.

C is incorrect. $500,000 is simply BAC, which assumes the overrun somehow disappears.

D is incorrect. $740,000 is approximately the cost-and-schedule formula, applicable when both performance indices are expected to persist.

Q30 — Correct answer: C

C is correct. Three sprints of 22, 31, and 27 show velocity still settling. Forecasting a release date from unstabilised velocity produces an unreliable commitment. Providing a range now and refining as velocity stabilises is both honest and more useful.

A is incorrect. Averaging three unstable data points and presenting a single sprint count implies a precision the data does not support.

B is incorrect. Selecting the best observed sprint produces an optimistic commitment the team has achieved once out of three attempts.

D is incorrect. Selecting the worst sprint is equally arbitrary in the other direction, and sandbagging a forecast is its own form of misrepresentation.

Q31 — Correct answer: B

B is correct. A subject matter expert steeped in the process has compressed several distinct steps into one line. Migration downtime, QA testing, and time to correct errors found during migration are separate work with separate durations, and each belongs on the schedule so the true duration and dependencies are visible.

A is incorrect. The estimate may well be low, but that is a symptom. The structural problem is that the activity hides multiple steps, which is what makes the estimate unreliable.

C is incorrect. Adding resources to a poorly defined activity does not clarify what work it contains.

D is incorrect. WBS linkage matters, but the immediate defect is the granularity of the activity definition itself.

Q32 — Correct answer: C

C is correct. A schedule composed entirely of finish-to-start dependencies is destined to be delayed. Building deliberate overlap where work can proceed concurrently, and reducing reliance on a vendor with a known delay history, prevents lag from accumulating rather than absorbing it after the fact.

A is incorrect. Finish-to-start is common but a schedule built exclusively from it has no resilience — every delay propagates fully to the end date.

B is incorrect. Buffers absorb delay rather than preventing it, and buffering every vendor dependency inflates the schedule without addressing the structural fragility.

D is incorrect. Procurement may need to address vendor performance, but that does not fix a schedule whose structure guarantees delays propagate.

Process Task 9 — Evaluate Project Status

ECO enablers

• Develop project metrics, analysis, and reconciliation.
• Identify and tailor needed artifacts.
• Help ensure artifacts are created, reviewed, updated, and documented.
• Help ensure accessibility of artifacts.
• Assess current progress.
• Measure, analyze, and update project metrics.
• Communicate project status.
• Continually assess the effectiveness of artifact management.

Choosing the right metrics

Data becomes information becomes reports: raw work performance data (tasks done, actual cost) is analysed into work performance information (CV, SV, forecasts), which is packaged into work performance reports for stakeholders.

Dashboards and radiators

• Keep it in a central location and treat it as a living, regularly updated source. The team must know where it is and what is expected of them in keeping it current.
• Set a defined update interval — short enough to be current, long enough not to burden the team. It should not be less than once per week.
• The dashboard should be consulted daily by the project manager, alongside email and chat, so a status question can be answered on a moment's notice and problems are spotted early.
• Information radiators make status visible without anyone having to ask — typically consolidating charter summary, impediments and blockers with colour coding, product and iteration backlog, burndown and burnup, and the team's working agreements.

Assessing the assessment

Practice

Q33.

A project has most of its deliverable due dates clustered in the final two months of a nine-month timeline. At the four-month mark the sponsor asks for a status assessment. Which metric will provide the MOST meaningful picture of progress?

A. The count of completed versus incomplete tasks.

B. Hours worked against planned effort, and interim milestones achieved.

C. The number of tasks currently overdue.

D. The percentage of total deliverables formally accepted.

Q34.

A project manager is closing a project and preparing the lessons learned session. The team has raised that the twice-weekly dashboard updates felt burdensome, and the project manager noticed that one tracked metric was never actually used in any decision. How should these observations be handled?

A. They are process complaints rather than project outcomes and fall outside the scope of lessons learned.

B. They should be included, since evaluating the status monitoring process is a legitimate part of closure and improves future projects.

C. They should be raised separately with the PMO rather than documented in project closure.

D. They should be noted informally but not recorded, to avoid implying the project was poorly managed.

Q35.

A cumulative flow diagram for a Kanban team shows the "Testing" band widening steadily over three weeks while other bands remain constant. What does this MOST likely indicate?

A. The team is completing work faster than expected and no action is needed.

B. Testing has become a bottleneck where work is accumulating; investigate and address the constraint.

C. Project scope has increased and the baseline should be updated through change control.

D. Velocity is increasing and the team can take on additional work in progress.

Q36.

A project manager needs to report progress to a sponsor who wants a single view of whether the project is on track, and to the delivery team who need to know which specific items are blocked. What is the MOST appropriate approach?

A. Provide both audiences with the full detailed dashboard to ensure transparency.

B. Provide the sponsor with a summarised view and the team with detailed blocker-level information, drawing both from the same central source.

C. Provide the sponsor with a summary and direct the team to request details as needed.

D. Maintain separate tracking systems tailored to each audience.

Solutions

Q33 — Correct answer: B

B is correct. With due dates clustered at the end, very few tasks will be complete at the four-month mark regardless of how well the project is progressing. Hours worked against planned effort and interim milestones achieved reveal actual progress where completion counts cannot.

A is incorrect. Task completion counts are precisely the metric that misleads on this schedule shape — a low count reflects the schedule design, not performance.

C is incorrect. Overdue counts are useful where due dates are distributed across the timeline. With few dates yet reached, this tells you almost nothing.

D is incorrect. Formal acceptance will be near zero by design at this point, for the same reason.

Q34 — Correct answer: B

B is correct. The enabler calls for continually assessing the effectiveness of artifact management. Closure is where you evaluate whether the monitoring approach worked — cadence, metric usefulness, team burden — so future projects inherit an improved process rather than repeating the same friction.

A is incorrect. Status monitoring effectiveness is explicitly part of what should be reviewed; it directly affected how the project was managed.

C is incorrect. These observations belong in the project's own lessons learned before being carried into organisational assets; routing them elsewhere skips the documented record.

D is incorrect. Omitting findings to protect appearances defeats the purpose of lessons learned and is closer to concealment than discretion.

Q35 — Correct answer: B

B is correct. A band widening while others hold steady means work is arriving at that state faster than it leaves — the definition of a bottleneck. The response is to investigate the cause and relieve the constraint, often by limiting upstream work in progress.

A is incorrect. A widening band is accumulation, not faster completion.

C is incorrect. Scope growth would show as the total rising, not one band widening while others stay constant.

D is incorrect. Adding work in progress to a system with a bottleneck worsens the jam; Kanban limits WIP at the constraint.

Q36 — Correct answer: B

B is correct. Tailoring the view to the audience while drawing from one central, living source gives each party what they need without fragmenting the truth. The sponsor gets an on-track judgement; the team gets blocker-level detail.

A is incorrect. Giving an executive the full detailed dashboard buries the answer they need in information they will not use.

C is incorrect. Requiring the team to request details defeats the purpose of a radiator — status should be visible without anyone having to ask.

D is incorrect. Separate systems create divergence between what each audience believes, which is the single-source-of-truth problem.

Process Task 10 — Manage Project Closure

ECO enablers

• Obtain project stakeholder approval of project completion.
• Determine criteria to successfully close the project or phase.
• Validate readiness for transition (e.g., to operations team or next phase).
• Conclude activities to close the project or phase (final lessons learned, retrospectives, procurement, financials, resources).

The closure sequence

32. Formal acceptance. Verify all requirements against the acceptance criteria established in the charter and scope statement. Hold a final review with sponsor and key stakeholders confirming deliverables meet expectations, contractual obligations are satisfied, and no open issues remain. The customer formally approves and acceptance documentation is signed and stored.
33. Verify closure criteria defined in the project management plan — performance metrics achieved, financial reconciliation complete, procurement closed, operational documentation finalised. Finance reconciles actual expenditure against baseline; procurement confirms contracts are closed or transitioned, including licence renewals and SLA updates.
34. Transition. Verify organisational readiness to receive the deliverable. Run knowledge transfer sessions covering configuration, support protocols, and escalation procedures. Formally transfer administration guides and maintenance schedules — and reassign access credentials.
35. Retrospective analysis. Facilitate a lessons learned workshop involving the stakeholder community, documenting insights into the organisational lessons learned repository.
36. Administrative closure. Compile the closure report, finalise and archive all documents, mark the project closed in the portfolio system, release or reassign the team, and recognise the work.

The closure report

Summarises overall performance, cost and schedule variances, risks encountered and how they were resolved, key achievements, and remaining recommendations — the report carries forward-looking guidance for whoever inherits the deliverable, not only a retrospective record. Proper archival of schedules, change logs, quality records, contracts, and communications supports future audits and similar project reviews.

Two rules that decide exam items

Practice

Q37.

A development team has finished the final deliverable of a system integration project. Functional managers are pressing for immediate release of the team to a newly approved initiative with an aggressive start date. The PMO notes that several governance-mandated closure activities remain incomplete. What should the project manager do?

A. Release the resources immediately to support the new initiative, then complete the remaining closure activities.

B. Communicate to stakeholders that the window for final feedback and lessons learned is closing soon.

C. Coordinate with the PMO to extend the project end date so all compliance tasks are completed before closure.

D. Follow the governance process to formally close the project, obtain sponsor approval, and then release resources.

Q38.

A project is cancelled by senior management halfway through, following a strategic shift, before any deliverables were completed. The team is eager to move to new assignments. What should the project manager do?

A. Release the team immediately, since no deliverables were produced and there is nothing to formally close.

B. Formally close the project — document the cancellation reason, capture lessons learned, close procurements, and release resources.

C. Keep the project open in case management reverses the decision, to avoid repeating closure work.

D. Archive the project files but omit lessons learned, since the project produced no successful outcomes.

Q39.

A project team is transitioning a new analytics platform to the IT operations group. Training sessions have been delivered and system documentation transferred. What remaining transition step is MOST likely to be overlooked?

A. Obtaining formal sponsor sign-off on the deliverable.

B. Reassigning system access credentials to the operations group.

C. Archiving the project schedule and change logs.

D. Conducting the lessons learned workshop.

Q40.

At the final review meeting for a contracted deliverable, one stakeholder raises an unresolved concern about a minor feature. The sponsor is willing to sign acceptance anyway to avoid delay. What should the project manager do?

A. Proceed with acceptance, since the sponsor holds approval authority and the concern is minor.

B. Address and resolve the open concern before acceptance is signed, to avoid subsequent dispute.

C. Sign acceptance and record the concern in the lessons learned register for future projects.

D. Sign acceptance and open a separate change request to address the feature post-closure.

Solutions

Q37 — Correct answer: D

D is correct. Formal governance procedures must be completed before releasing resources. This ensures administrative, financial, and procurement activities are concluded and maintains compliance with PMO oversight and audit standards.

A is incorrect. Prematurely releasing resources violates governance and risks losing closure documentation and accountability once the team disperses.

B is incorrect. Stakeholder communication is valid but does not address the required formal closure or resource release process.

C is incorrect. Artificially extending the timeline misrepresents closure progress and is not compliant with governance expectations.

Q38 — Correct answer: B

B is correct. Every project is closed properly regardless of how it ends. Document why, capture lessons learned, close procurements, release resources — the reason a project ends changes nothing about the need to close it well.

A is incorrect. "No output means no closure needed" is false. Unclosed vendor agreements, no record of the cancellation rationale, and no captured lessons are all live loose ends.

C is incorrect. A cancelled project is cancelled. Leaving it open against a hypothetical reversal avoids the work rather than doing it.

D is incorrect. Failed and cancelled projects often carry the most valuable lessons — why the strategy shifted, what early signals were missed. Skipping them is exactly backwards.

Q39 — Correct answer: B

B is correct. Credential reassignment is the operational step most easily forgotten once training and documentation are complete — and without it the receiving team cannot actually administer the system they have just been trained on.

A is incorrect. Sponsor sign-off is a prominent, formally scheduled step unlikely to be overlooked, and it belongs to acceptance rather than transition.

C is incorrect. Archival is administrative closure, a later phase, and is typically a tracked checklist item.

D is incorrect. The lessons learned workshop is a distinct, scheduled closure activity rather than a transition detail.

Q40 — Correct answer: B

B is correct. The final review exists to confirm that deliverables meet expectations, contractual obligations are satisfied, and no open issues remain — specifically to prevent subsequent disputes or claims. Signing over a live unresolved concern defeats that purpose.

A is incorrect. Sponsor authority does not eliminate the exposure created by accepting a deliverable with a known open concern from a stakeholder.

C is incorrect. Lessons learned records the observation for future projects while leaving this project's dispute risk live.

D is incorrect. Opening a post-closure change request on a project being closed leaves an unresolved obligation attached to a formally completed engagement.

PART 2 — Graphic Interpretation Reference

The 2026 exam introduced graphic-based questions on all modalities, requiring you to read a chart and answer from it. Process is where these will concentrate. Each chart below has one reliable discriminator.

Burndown chart — work remaining

Burnup chart — work completed

Velocity chart

Story points completed per sprint. Early sprints are typically uneven while the team forms; velocity stabilises after several sprints, and only then is it a sound basis for forecasting releases or completion dates.

Cumulative flow diagram — four bottleneck signatures

Distinguish temporary from chronic — a one-off accumulation and a systemic constraint call for different responses, and telling them apart requires monitoring over time rather than reading a single snapshot.

Duration measures read from a CFD

Reading earned value from a chart

Where PV, EV, and AC are plotted over time: EV below PV means behind schedule; AC above EV means over budget. The vertical gaps at any point in time are SV and CV respectively.

PART 3 — Agile Framework Reference

For recognition and matching items. Each framework has one defining mechanism worth knowing.

Task assignment differs by framework: Scrum pushes — work is assigned during sprint planning. Kanban pulls — team members select work as capacity allows.

Pair programming appears in XP as an engineering practice, and doubles as a knowledge transfer mechanism — it ensures no single team member becomes a bottleneck for specialised information.

PART 2.5 — Corrections and Extensions

Everything below comes from real, timed practice items — most straightforward on first read, several genuinely counterintuitive. Where a rule sharpens or overrides something stated earlier in this document, that supersession is noted explicitly.

New tool: Value Breakdown Structure

A genuinely new artifact for Process Task 3, distinct from a value proposition, cost-benefit analysis, or EMV.

The tool-vs-governing-process trap (confirmed twice)

A recurring shape worth treating as reliable: one option offers a specific tool or data source; another offers the governing process that tool operates within. When the stem emphasises procedural rigour, fairness, or auditability, the governing process wins — the tool is only as objective as the framework applying it consistently.

In both cases the rationale did not call the losing option wrong — it called it incomplete: "helpful when paired with clear metrics," "KPIs are valid, but the project manager must perform a full structured evaluation, not just use past metrics." A specific data point is an input to the governing process, not a substitute for it.

The role-boundary rule

Same boundary, different context: when a leading indicator flags an unclear-cause problem, the PM's job is judging communication and coordination around the signal (consult the communications management plan for who/when to notify), not personally researching and fixing the underlying technical issue — that belongs to the team.

"Assumes a future outcome as already true"

A distinct trap shape, separate from ordinary prematurity: an option that lets work continue based on an expected approval that has not happened yet.

EV analysis versus impact analysis — a genuine distinction

Sequencing confirmed explicitly: "too complex for the first step... start with straightforward impact analysis before running advanced risk simulations." Basic impact analysis precedes sophisticated quantitative tools, which in turn precede formal re-baselining.

Verb-matching: when the stem asks to align, analysis alone is not enough

A related, distinct boundary: "involving stakeholders in decision-making" is not the same as "facilitating." Handing decision authority to stakeholders directly risks diluting the project manager's own coordinating role; facilitation keeps the PM actively running the process toward resolution. Where both are offered, facilitation is the PM-appropriate action.

Approach and delivery-strategy decisions belong to the PM

The mirror trap: rigidly refusing to even evaluate a proposed change to the approach, purely to protect an already-approved plan, is "control-focused rather than value-driven." Sound judgement means genuinely evaluating a suggested improvement, not reflexively protecting the original plan or reflexively deferring the decision upward.

Named governance term: investment control

A formal financial-stewardship governance model suited to public corporations and government agencies, where public accountability requires strict controls. Wrong fit for dynamic, fast-moving environments (software development, adaptive delivery) — the same rigour that makes it appropriate for public accountability actively slows down responsive work. Recognise it as a distractor in agile/dynamic contexts specifically.

Procurement: MSA with appendices

A contract-restructuring option missing from the original contract-type table. When a vendor has been performing more work than the current contract anticipated (commonly under T&M) and the contract is expiring, shifting to a master services agreement with appendices allows additional work to be added without renegotiating the entire agreement — faster and more flexible than switching vendors or re-tendering, and it directly fixes the open-ended-scope problem that caused the original overrun, unlike simply renewing the same structure.

Reporting integrity — five confirmations, one line worth keeping verbatim

Tested repeatedly today (hybrid dual-metric reporting, defect metrics under sponsor pressure, schedule variance before an executive demo) with total consistency: report accurately, explain the variance, present a corrective plan. Every wrong option was a variant of concealment — outright manipulation, timed delay, cherry-picking favourable numbers, or omitting a metric to "simplify."

Vanity-metric correction, same family: when a metric is actively misleading (raw completion count masking that only small, low-value items are finished), the fix is to revise it to measure outcomes tied to major goals — not supplement it with additional metrics alongside the flawed one. Supplementing leaves the bad signal in place.

Investors need the full three-part package

Confirmed: market analysis + business plan + risk management strategies together — not financial projections alone, not risk alone. "This holistic approach addresses their concerns about project viability." Any single-dimension option (cost-benefit only, risk only) is incomplete for an investment decision, and planning future stakeholder engagement is premature when their participation isn't yet confirmed.

Contingency and reserves: "quantify" is the operative word

When senior management or a sponsor asks for stronger planning discipline via quantified risk exposure and reserves, the first step is analysing lessons learned from a comparable prior project to quantify impacts — not merely identifying or recording root causes.

Scope: additional funding after approval is scope creep

Requesting more budget to preserve full original scope against a hard external deadline, after the budget was already approved, is functionally scope creep through the funding door rather than the requirements door. Where a backlog has genuine slack (a large nice-to-have share), the correct lever is collaborative reprioritisation toward minimum viable scope with the accountable role (product owner), not resourcing escalation.

Schedule compression: constraint-driven elimination

Confirmed cleanly: with SPI significantly below 1.0 and explicit "no additional budget, no scope change" constraints, crashing is disqualified by definition (it requires added resources = added cost) and scope reduction is disqualified explicitly. Fast-tracking is the only compression technique that fits inside both stated boundaries. Read the stem's stated constraints as elimination filters before evaluating which technique is generally "better."

Information radiators extend beyond status

Not limited to backlog, burndown, and blockers. A radiator displaying recently taught, complex, or consistency-critical reference material is a legitimate retention tool — confirmed over informal peer pairing specifically because informal peer review "lacks structure and doesn't ensure consistency in critical knowledge." Structured, constantly visible reference beats informal discussion when the content must stay uniform across the whole team.

The ten tasks in one line each

Distinctions that decide items

Answer-selection sequence for a Process item

37. Establish the world. Predictive, adaptive, or hybrid — and if hybrid, which workstream does this event land in? Predictive baselined work means change control; adaptive backlog means re-prioritisation.
38. Ask what each option requires to already exist. If it depends on something that has not happened, it is not first, however sound it is eventually.
39. Check for a smuggled decision. Two options can both begin with assess and differ entirely in what follows — "evaluate for the next release" has already decided the timing.
40. Match any property the stem names. If it asks for something structured, systematic, or proactive, test each option against that word specifically.
41. Prefer analysis before commitment, and note that this cuts both ways — premature yes and premature no are equally wrong when neither has been assessed.
42. Read every option to its last word. A qualifier — with no cost ceiling, in the next release, informally, without informing — frequently disqualifies an otherwise sound option.

Where the remaining risk sits

43. Graphic interpretation. New format, and burndown-versus-burnup direction is the easiest thing to invert under pressure.
44. EAC formula selection. The arithmetic is trivial; the wrong answers are the other formulas' correct results.
45. Hybrid workstream identification. The same event has opposite correct handling depending on which side it lands on.
46. Agile capacity mechanics. Squads not individuals, velocity stabilisation before forecasting, non-project work coming off capacity.
47. Contract type plus the input/output axis. Two independent dimensions that combine.
48. Value versus output. A completed increment is not value until it is released and produces benefit.

PMP® 2026

Business Environment Field Notes

Mechanics and named techniques beyond the ECO enablers · July 2026 ECO

Governance · Compliance · Impediments · Risk · Improvement · Change

Field mechanics and named techniques beyond the ECO enablers

Reading the options · cautionary notes · rapid reference

Appendix — Rapid reference, escalation triggers, acronyms

24 original practice questions with full option-by-option solutions

PMP 2026 — Business Environment Field Notes

What this part adds. The task-by-task sections cover all eight Business Environment tasks from the ECO enablers outward. This one adds the mechanics, named techniques, and field-tested distinctions drawn from the wider reading set — the material that is not in the enabler list but that questions are built on top of.

Why this domain deserves more attention than it usually gets. Business Environment was worth 8% of the exam under the 2021 outline. It is now worth 26% — roughly 47 questions. Preparation built on older material systematically under-weights it, and the tasks themselves (governance, compliance, organisational change) are less intuitive than their People and Process counterparts.

What is new here

BE Task 1 — Define and Establish Project Governance

The PPM hierarchy

Governance operates at three levels, and each governs a different question. This is the structural layer beneath the escalation paths and thresholds in the enabler list.

Leading versus lagging indicators

Validated in live practice, and a dimension the KPI-by-level table above does not capture. When a stem asks for metrics that anticipate, predict, or get ahead of a problem, it is asking for a leading indicator — and most metric options offered will be lagging ones.

Embedding a missing mechanism

Governance structures, distinguished

Five steps to define governance

49. Clarify decision rights — who approves scope changes, who reallocates budget, who escalates.
50. Establish escalation paths — so disagreements resolve rather than stall.
51. Set oversight mechanisms — governance includes monitoring, not only decision-making.
52. Define documentation requirements — records create the audit trail that regulators trust. Memories fade; records remain.
53. Communicate governance — a published governance chart that nobody understands is not governance. Walk teams through it; make it part of kickoff.

Two failure modes, in opposite directions

Buy-in, and the sponsorship gap

Governance imposed without buy-in fails. Teams that see governance as bureaucracy imposed by outsiders resist it; teams involved in shaping it own it. This is the same co-creation principle that governs vision-building and organisational change — it applies to governance itself.

Practice

Q1.

A portfolio review identifies four separate projects across three departments, each with overlapping requirements, all contributing to a single customer-experience outcome. Each has its own project manager and reports independently. What should be recommended?

A. Consolidate the four projects into one project with a single scope baseline.

B. Regroup them under a programme with a rewritten business case reflecting the larger outcome, and establish programme-level oversight.

C. Retain the four projects and add a coordination meeting between the project managers.

D. Escalate the overlap to the portfolio level and allow portfolio governance to resolve it.

Q2.

A project manager finds that the organisation's change approval process requires seven sequential sign-offs, and a recent low-risk configuration change took four weeks to approve. Delivery teams have begun making minor changes without submitting them. What is the MOST appropriate response?

A. Enforce the existing process strictly and address the unauthorised changes as compliance violations.

B. Raise the disproportionate approval burden with the governance body and propose a right-sized process for low-risk changes.

C. Allow low-risk changes to bypass approval to restore delivery pace.

D. Document the delays in the issue log and continue with the existing process.

Q3.

A programme operating in a regulated organisation has clearly defined governance requirements but no executive sponsor. Workstream leads have stopped submitting status updates, and the programme manager has no visibility of emerging risks. What should the programme manager do FIRST?

A. Design a new governance framework better suited to the programme's structure.

B. Escalate the absence of an executive sponsor to the portfolio governance body and pause reporting until one is appointed.

C. Centralise coordination and rebuild reporting through direct engagement with each workstream lead.

D. Make status reporting mandatory by issuing a formal directive to all workstream leads.

Q4.

A newly appointed project manager is asked to define success metrics for a programme delivering three related initiatives. What metrics are MOST appropriate at the programme level?

A. Scope, schedule, and cost performance for each constituent project.

B. Benefits realisation and business value across the constituent initiatives.

C. Objectives and key results tied to enterprise strategy.

D. Return on investment and net present value for the programme as a whole.

Solutions

Q1 — Correct answer: B

B is correct. Three or more projects with overlapping requirements contributing to a bigger outcome is the recognised trigger for programme formation. The business case is rewritten to reflect the larger goal, and oversight moves to programme level where alignment to shared outcomes is governed.

A is incorrect. Merging four distinct efforts into a single project collapses their individual scope and delivery structures. A programme coordinates related projects; it does not dissolve them.

C is incorrect. A coordination meeting adds communication without governance. Nobody owns the cumulative outcome, and the alignment problem persists.

D is incorrect. Portfolio governance addresses strategic priorities across the organisation. The problem here is alignment among a related cluster, which is programme-level work.

Q2 — Correct answer: B

B is correct. Governance should enable rather than paralyse, and the evidence of failure is already visible in teams routing around the process. Raising the disproportion with the governance body and proposing a right-sized path for low-risk changes fixes the cause while keeping the decision where it belongs.

A is incorrect. Enforcement addresses the symptom and confirms that compliance is more costly than evasion. It leaves a process that generates its own violations untouched.

C is incorrect. The project manager does not have authority to grant bypasses unilaterally, however sensible the judgement. Right-sizing is a governance decision, not a personal one.

D is incorrect. Logging the delays records the problem without addressing it, and leaves unauthorised changes continuing in the meantime.

Q3 — Correct answer: C

C is correct. The framework is not the problem — the absence of sponsorship has made compliance with it effectively optional. Centralising coordination and rebuilding reporting through direct relationships restores the fact base that governance depends on, and is achievable at the programme manager's level.

A is incorrect. Designing a new framework replaces something that is already well defined. The gap is in adherence, not in design.

B is incorrect. Pausing reporting removes the last remaining visibility, and escalating without first attempting to restore discipline skips the work the programme manager can do directly.

D is incorrect. A directive issued without sponsorship carries no weight — that is precisely why the updates became optional.

Q4 — Correct answer: B

B is correct. Programme governance aligns constituent initiatives to shared outcomes and ensures cumulative value delivery, so benefits realisation and business value are the level-appropriate measures.

A is incorrect. Scope, schedule, and cost are project-level metrics. Rolling them up measures execution discipline rather than whether the programme's outcome is being achieved.

C is incorrect. OKRs tied to enterprise strategy belong at portfolio level, written into portfolio business cases.

D is incorrect. ROI and NPV are portfolio-level financial measures, and are explicitly noted as insufficient on their own even there.

BE Task 2 — Plan and Manage Project Compliance

Four categories, not three

The enabler names security, health and safety, sustainability, and regulatory compliance. Field practice sorts requirements into four categories, and the fourth is where the unexpected failures come from.