Reviewed 10 October 2026 against the linked published scope. July 2026 outline: People 33%, Process 41%, Business Environment 26%; approaches span all domains.
Memory hook: Align people, deliver value, and use governance to adapt responsibly.
Read the essentials, cover the answers and explain the decision aloud. Open the topic summaries below whenever a distinction is unclear.
People and stakeholders
- Create shared purpose, roles, working agreements and observable success criteria. Adapt leadership to capability and context; coach, facilitate and remove impediments rather than taking every decision away from the team.
- Address conflict through facts, interests and collaboration when suitable. A private, respectful conversation usually precedes punitive escalation; urgent safety, harassment or legal issues require the proper immediate process.
- Identify stakeholders early and reassess influence, interest, expectations and communication needs. Confirm understanding through feedback, not merely message delivery. Tailor channels to complexity, urgency, culture and access.
- Build capability through training, pairing and knowledge transfer. Distributed teams need deliberate inclusion and information access. Track whether the organization is ready to use the outcome, not only whether the project team is busy.
Process, planning and performance
- Predictive approaches suit relatively stable requirements; adaptive approaches learn through short increments; hybrid combines deliberate elements. Change the approach for the situation, not because one label is universally superior.
- Connect scope, schedule, cost, quality, resources, procurement, risk and communication. WBS decomposes deliverable scope; an ordered backlog supports adaptive discovery. Acceptance criteria describe conditions for acceptance; a Definition of Done expresses shared completion quality.
- Critical path is the longest-duration dependency path driving earliest completion. Float is scheduling flexibility; the critical path can change. Fast tracking overlaps work and adds rework risk; crashing adds resources/cost where extra resources can shorten duration.
- Three-point triangular estimate:
(O + M + P) / 3; PERT expected estimate:(O + 4M + P) / 6. State assumptions; estimates are not promises. - Earned value: PV = planned budgeted work, EV = completed budgeted work, AC = actual cost. CV = EV − AC; SV = EV − PV; CPI = EV / AC; SPI = EV / PV. Negative variances and indices below 1 generally indicate unfavorable cost/schedule performance.
- EAC = BAC / CPI assumes current cost efficiency continues. If the original remaining estimate is still reasonable,
EAC = AC + BAC − EV; a fresh bottom-up estimate usesAC + revised ETC.ETC = EAC − AC;VAC = BAC − EAC. Select the formula matching the stated assumption. - Quality assurance improves process; quality control inspects results. Grade is a feature/category distinction, not conformance quality. Pareto prioritizes contributors, cause-and-effect explores causes and control charts examine process behavior.
- Procurement starts with make-or-buy, scope and risk allocation. Fixed-price generally shifts more cost risk to the seller for defined scope; cost-reimbursable shifts more to the buyer; time-and-materials needs bounds/monitoring. Read the actual contract and change clauses.
Business environment, risk and change
- A deliverable is an output; an outcome is the change it enables; a benefit is measurable value. Revisit the business case and benefits through delivery; finishing the original scope is not automatically success if the need has changed.
- Governance defines decision rights, escalation, compliance and acceptable conduct. Assess a proposed change's impacts before the authorized decision; predictive baseline changes need the defined control process, while adaptive backlog refinement operates within its governance.
- Risk is uncertain; an issue exists now. Threat responses include avoid, mitigate, transfer, accept and appropriate escalation; opportunities may be exploited, enhanced, shared or accepted. Assign owners, triggers and contingency; monitor residual and secondary risk.
- Incorporate regulatory, organizational, sustainability and external-environment changes. AI can assist analysis but requires privacy, evidence checking, bias awareness and human accountability. Do not upload confidential information into an unauthorized tool.
- Transition needs ownership, training, documentation, support, access, monitoring and recovery readiness. Obtain acceptance, settle appropriate procurements, transfer knowledge and assign ongoing benefit ownership at closure.
Scenario traps
- Prefer understanding and collaboration before unilateral replacement/escalation, unless the scenario requires urgent action.
- Do not bypass an agreed change process to satisfy an influential stakeholder.
- This guide uses the July 2026 People 33%, Process 41%, Business Environment 26% outline; older 42/50/8 weightings are not the target.
Final active recall
1. EV=80, AC=100 and PV=90. What do CPI and SPI indicate?
CPI=0.8: over budget for work performed. SPI≈0.89: less budgeted work completed than planned.
2. A sponsor requests extra scope immediately. What first?
Clarify and assess the change and its impacts, then use the agreed decision/change process.
3. Fast tracking versus crashing?
Overlap activities with added coordination/rework risk versus add resources/cost where this shortens work.
4. A deliverable is complete but nobody adopts it. Has value necessarily been realized?
No. Adoption, outcomes and measurable benefits still need evaluation and ownership.
5. When is BAC/CPI an appropriate EAC?
When the current cumulative cost efficiency is expected to continue for the remaining work.
Sources and further practice
- Official exam scope
- Objective-to-topic coverage map. Each full topic links to its supporting primary technical documentation.
Every topic at a glance
Open any topic to revisit its essential facts, decisions and exam traps. Use the full topic for active recall and supporting references.
01 · Leadership, Team Agreements and Conflict
Memory hook: Understand the cause; involve the people; remove the blocker.
Must remember
Begin with a shared purpose and agreed success criteria. Adapt leadership to the team’s capability, urgency and context: a new team may need clearer direction; an experienced team needs room to decide how to deliver. Servant leadership supports the team by removing impediments, enabling learning and protecting focus, rather than assigning every technical task.
Clarify roles, decision rights and working agreements. A RACI distinguishes who performs work, who is accountable, who is consulted and who is informed. Psychological safety lets people expose errors and risks early. Cultural differences, accessibility and remote time zones should influence collaboration practices, not be treated as misconduct.
When conflict appears, establish facts, hear the parties and identify the underlying interest or constraint. Collaborating can solve the underlying problem; compromising gives each side something; accommodating yields; avoiding postpones; directing imposes a decision. No style is always correct: immediate safety/compliance issues may require urgent action, while routine disagreement usually benefits from facilitated resolution.
Coach skill gaps, use pairing/mentoring and agree measurable improvement. Address persistent behavior directly and respectfully using the organization’s process. Escalate when authority, policy or unresolved impact requires it, with evidence and options. Automatically replacing a team member or escalating every disagreement prevents local problem solving.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| Developers disagree about an approach | Facilitate evidence-based discussion and agree evaluation criteria. |
| Team blocked by another department | Work with the dependency owner; escalate if resolution exceeds authority. |
| Safety violation | Act promptly through the applicable safety/governance process. |
Traps
- Servant leadership does not mean avoiding difficult decisions.
- The best first action depends on urgency; assessment must not delay necessary containment.
02 · Stakeholders, Communication and Knowledge
Memory hook: The right message reaches the right decision maker in time.
Must remember
Identify stakeholders early and keep the analysis current. Consider influence, interest, impact, expectations and attitude; a quiet operational team may be critical to adoption. Engagement moves beyond sending status reports to understanding concerns and involving people in decisions they affect.
Tailor communication to purpose and audience. Executives may need benefit/risk decisions, while delivery teams need detailed dependencies. Choose interactive discussion for ambiguity or conflict, push messages for targeted updates, and pull repositories for reference material. Agree frequency, owner, channel, confidentiality and escalation thresholds.
Use feedback to confirm understanding. A transmitted message is not proof of a shared interpretation. Keep decision logs, assumptions, action owners and agreed changes visible. In distributed teams, combine accessible written context with appropriate synchronous discussion; do not assume everyone can attend one time zone’s meeting.
Monitor expectation gaps throughout delivery. If a stakeholder requests something outside agreed scope, understand the need and evaluate the appropriate change/backlog process rather than promising it privately. Knowledge transfer includes operational runbooks, demonstrations, pairing and recorded decisions; verify the receiving team can actually perform the work.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| Stakeholder upset despite weekly reports | Discuss expectations and feedback, then adjust engagement. |
| Complex disagreement | Interactive conversation with decision evidence. |
| Operations must support the product | Early involvement, training and demonstrated handover readiness. |
Traps
- More communication is not automatically better communication.
- A knowledge repository alone does not prove knowledge transfer.
03 · Delivery Approach, Scope and Value
Memory hook: Tailor the method; protect the goal; deliver useful increments.
Must remember
Predictive planning suits relatively stable requirements and a definable delivery path. Adaptive work uses short feedback cycles when needs/solutions are uncertain. Hybrid combines practices deliberately; it is not an excuse for contradictory governance. Tailor to risk, regulation, dependencies, stakeholder availability and feedback cost.
An integrated plan connects scope, schedule, cost, quality, resources, procurement, communication and risk. The charter authorizes a project and its high-level purpose; the detailed plan explains delivery. Trace requirements to business objectives and acceptance criteria. Decompose scope into manageable deliverables/work packages using a WBS in suitable predictive contexts.
For adaptive delivery, maintain an ordered backlog, refine near-term work and prioritize by value, risk, dependency and learning. The team’s capacity and evidence inform forecasts. A fixed date does not make all requested scope feasible; discuss trade-offs transparently. Rolling-wave planning details near work while leaving later work at an appropriate level.
An output is a deliverable; an outcome is the change it enables; a benefit is measurable value. Define who measures benefits, when, and against which baseline. Early increments can test assumptions before a large irreversible investment. A completed feature that nobody uses may satisfy an output measure while failing the business objective.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| Stable regulated construction sequence | A suitable predictive plan with formal control. |
| Uncertain user needs | Adaptive experiments and frequent feedback. |
| Requested scope exceeds capacity | Make value/dependency trade-offs with authorized stakeholders. |
Traps
- Agile does not mean no planning or documentation.
- Finishing all tasks is not proof of business value.
04 · Resources, Negotiation and Procurement
Memory hook: Allocate by capability; contract by uncertainty.
Must remember
Estimate people, equipment, facilities and materials with availability and calendars. Resource leveling resolves over-allocation and may change the critical path or finish date; smoothing adjusts work within available float where possible. A specialist’s nominal availability is not the same as usable capacity across competing projects.
Build a procurement strategy from make-or-buy analysis, internal capability, risk and delivery constraints. Use clear specifications, evaluation criteria and acceptance terms. Fixed-price arrangements shift more cost-overrun risk toward the seller when scope is defined; cost-reimbursable arrangements leave more cost uncertainty with the buyer; time-and-materials needs rate and consumption controls. Actual contract clauses determine the real allocation of risk.
Negotiate interests, alternatives, authority and measurable commitments. Assess vendor competence, capacity, security, sustainability and continuity, not just lowest initial price. A supplier relationship may involve subcontractor/fourth-party risks. Monitor milestones, deliverable quality and contractual obligations throughout delivery.
Handle disputes and changes through agreed commercial procedures. Do not casually direct extra vendor work without considering authorization and liability. Document acceptance, outstanding claims, warranties, knowledge transfer and final payments at closure. Procurement completion and project completion are related but not identical events.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| Well-defined deliverable and price certainty | Consider a suitable fixed-price contract. |
| Highly uncertain research scope | Consider a controlled reimbursable arrangement. |
| Scarce person assigned twice | Reconcile priorities and capacity; level/smooth as appropriate. |
Traps
- The cheapest bid may have the highest lifecycle risk.
- Contract labels alone do not reveal every legal obligation.
05 · Schedule, Finance and Performance Calculations
Memory hook: Earned is completed value; actual is money spent.
Must remember
The critical path is the longest-duration dependency path controlling the earliest finish in the current model. Total float is allowable delay without delaying the relevant project finish; a critical activity normally has zero total float in a simple unconstrained network. Recalculate after changes. Crashing adds resources/cost to shorten feasible work; fast tracking overlaps work and increases coordination/rework risk.
For three-point estimates, triangular expected duration is (O + M + P) / 3; a commonly used PERT weighted estimate is (O + 4M + P) / 6. Estimates depend on assumptions and uncertainty. Story points express relative team estimates, not a universal conversion to hours or a fair comparison between teams.
Earned value uses PV (budgeted planned work), EV (budgeted completed work) and AC (actual cost). CV = EV - AC, SV = EV - PV, CPI = EV / AC, SPI = EV / PV. Negative variance or an index below one indicates unfavorable performance in that dimension. Example: EV 80, AC 100, PV 90 gives CPI 0.8 and SPI about 0.89.
EAC = BAC / CPI assumes current cost efficiency continues. EAC = AC + ETC uses a new estimate to complete; VAC = BAC - EAC. Select the formula whose assumptions match the scenario. Schedule variance expressed in money is not a direct count of days late, and SPI can lose usefulness near completion.
Contingency addresses identified uncertainty within the appropriate plan/baseline; management reserve addresses broader unplanned work under governance control. Track forecasts, cash flow and benefit value alongside spent cost. Report unfavorable trends honestly rather than changing baselines merely to hide variance.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| Need faster finish with extra feasible staffing | Evaluate crashing on critical work. |
| Current cost efficiency likely persists | BAC/CPI forecast. |
| Remaining work materially re-estimated | AC plus new ETC. |
Traps
- CPI is EV/AC, not AC/EV.
- A noncritical task shortened within its float may not shorten the project.
06 · Quality, Evidence and Continuous Improvement
Memory hook: Build quality in; inspect outcomes; improve the system.
Must remember
Quality means meeting relevant requirements and fitness for intended use; grade describes a category or feature level. A basic product can be high quality. Prevention and appraisal are costs of conformance; internal/external failure are costs of nonconformance. Investing in prevention can reduce expensive rework and customer harm.
Quality assurance/process improvement asks whether the delivery process can produce suitable results; quality control examines outputs. Acceptance validates that authorized stakeholders accept the deliverable against criteria. Testing performed by the development team does not automatically constitute business acceptance.
Use cause-and-effect analysis to explore contributors, Pareto analysis to prioritize significant categories, control charts to study process variation, and checksheets to collect consistent observations. A process can be statistically stable yet consistently outside specification. Avoid changing a stable process after every random fluctuation without evidence.
Choose metrics that inform decisions: defects escaping to customers, lead/cycle time, throughput, rework and benefit adoption. Maintain accurate accessible artifacts and versioned decisions. A dashboard of green task statuses can conceal low product value or poor quality. Run retrospectives/lessons learned during delivery and assign improvement owners rather than waiting until the end.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| Repeated defects from one handoff | Investigate process causes and prevention. |
| Stable process still fails customer tolerance | Improve capability; stability alone is insufficient. |
| Need formal deliverable acceptance | Compare with agreed criteria and obtain authorized confirmation. |
Traps
- Quality is not the same as luxury or feature count.
- A lesson recorded but never acted on is not an improvement.
07 · Governance, Change, Risk and Compliance
Memory hook: Risk may happen; issue has happened; change needs authority.
Must remember
Governance defines decision rights, reporting, escalation and acceptable conduct. Establish success criteria and tolerances early. Follow legal, contractual, safety, privacy and sustainability obligations; an aggressive schedule does not authorize ignoring them. Seek the appropriate specialist where interpretation is required.
Assess a proposed change’s impact on scope, schedule, cost, quality, risk and benefits before the authorized decision. Predictive baselines usually use formal integrated change control. Adaptive backlog reprioritization operates within agreed funding, scope boundaries and product authority; it does not bypass compliance or every contract constraint. Implement approved changes and update affected artifacts.
A risk is an uncertain condition with potential effect; an issue already requires attention. Identify threats/opportunities, assess probability and impact, assign an owner and plan responses. Threat strategies include avoid, mitigate, transfer, accept or escalate. Opportunities may be exploited, enhanced, shared, accepted or escalated. Transfer does not eliminate accountability or all residual risk.
Track triggers, residual risks and secondary risks introduced by a response. Qualitative analysis prioritizes; quantitative analysis models numerical effects where useful. EMV = probability × financial impact, with sign conventions stated. When a risk occurs, activate the planned response and manage the resulting issue. Reassess rather than leaving the register frozen after kickoff.
AI tools may assist analysis and reporting, but protect sensitive inputs, check source evidence and retain human accountability. Generated forecasts or status narratives are not verified project facts.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| Sponsor requests extra functionality | Assess impact and use the authorized change route. |
| Vendor failure is only a possibility | Risk with owner and response. |
| Vendor has already failed | Issue management and any triggered contingency. |
Traps
- A risk register is not an issue log.
- Transferring a risk does not mean it no longer needs monitoring.
08 · Benefits, Adoption and Responsible Closure
Memory hook: Deliver, hand over, measure value, then learn.
Must remember
Track the business case throughout the project. Market, regulation, technology and organizational strategy can change the value of continuing. Reassess benefits and costs with the sponsor/governance body instead of completing obsolete work merely because money has already been spent. Sunk cost alone is not a reason to continue.
Organizational change needs stakeholder readiness, communication, training, support and feedback. A technically successful deployment can fail if users cannot adopt it. Consider sustainability across procurement, operation and disposal, balancing measurable environmental/social objectives with the project’s business requirements.
Agree transition criteria with operations: documentation, ownership, support model, monitoring, access, training, known issues and recovery arrangements. Obtain formal acceptance where required. Close contracts, reconcile finances, release resources, archive records and capture lessons. If a project ends early, controlled closure is still necessary.
Benefits can continue after project closure. Assign an operational/business owner, baseline, measurement frequency and review dates. Distinguish acceptance of deliverables from proof that intended benefits were realized. Share improvements back into organizational procedures, templates and future estimates.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| Business case no longer viable | Escalate evidence and evaluate redirecting or ending the work. |
| Users resist a new system | Investigate needs/readiness and support adoption. |
| Project closes before benefits mature | Transfer benefit ownership and measurement to the responsible business owner. |
Traps
- Sunk spending does not justify future waste.
- Project closure does not necessarily end benefits measurement.