PKMC Module III common mistakes
PKMC Module III · Understand the traps and how to avoid them.
Calculating EAC by simply adding the original budget to the cost variance (EAC = BAC + CV) or mixing up which formula applies to which scenario, instead of selecting the formula based on whether the remaining work will proceed at the budgeted rate or the current CPI.
Candidates memorize a list of EAC formulas without linking each to its underlying assumption. Under exam pressure they grab the first formula that comes to mind, and because several produce plausible-looking numbers, the error is invisible. They also confuse CV/CPI (cost) with SV/SPI (schedule) sign conventions.
What to do instead
Before computing, write one line stating the assumption: 'atypical variance, remaining work at budgeted rate' means EAC = AC + (BAC - EV); 'typical variance, current CPI continues' means EAC = BAC / CPI. Compute CPI and SPI separately and sanity-check the sign: negative CV means over budget, negative SV means behind schedule. Practice three scenarios side by side until the assumption-to-formula mapping is automatic.
Treating the WBS as a task list and decomposing straight to activities, or building a WBS whose lower levels are verbs ('test system', 'train users') rather than deliverables.
Most candidates have seen Gantt charts and to-do lists far more often than proper deliverable-oriented WBSs, so they default to activity thinking. The exam's WBS questions hinge on the 100% rule and on work packages being deliverable-based, which activity-flavored answers violate.
What to do instead
Remember the hierarchy: WBS (deliverables) → work packages → activities (schedule). The lowest WBS level is a work package that can be estimated and assigned; activities belong to the activity list, not the WBS. Apply the 100% rule: child elements must sum exactly to the parent, no more, no less. When an answer option describes an action rather than a thing, eliminate it.
Confusing quality assurance with quality control, or placing quality planning after execution begins, when answering process-group questions.
The words sound interchangeable in everyday speech, and candidates answer from general intuition rather than from the PMBOK process map. They also misplace processes in the wrong process group (e.g., putting Manage Quality in Monitoring and Controlling).
What to do instead
Anchor on the distinction: quality assurance (Manage Quality) is process-focused and preventive, performed during Executing; quality control (Control Quality) is product-focused and detective, performed during Monitoring and Controlling. Quality planning (Plan Quality Management) belongs in Planning. For any process question, first name the process group, then the process, then the tool.
Answering stakeholder questions by focusing only on the sponsor and customer, and skipping identification of negative or overlooked stakeholders, or failing to update the stakeholder register as the project evolves.
Candidates default to a mental model of 'the people who pay and the people who use it.' The exam deliberately tests whether you identify all stakeholders early, analyze power/interest, and revisit the register iteratively rather than treating it as a one-time document.
What to do instead
For any stakeholder scenario, run a checklist: who is affected, who can influence, who has been omitted (regulators, functional managers, end users, operations, suppliers, negative stakeholders). Classify with a power/interest grid and match the engagement strategy to the quadrant. Treat the stakeholder register as a living artifact updated at each phase gate and after every change.
Handling a change request by approving it, implementing it, or telling the requester to proceed, without routing it through the Perform Integrated Change Control process and assessing impact on scope, schedule, cost, quality, and risk first.
In real workplaces, small changes often get waved through informally, so candidates carry that habit into the exam. The exam consistently rewards the formal path: document, assess impact, submit to the change control board, then update the change log and baselines if approved.
What to do instead
Whenever a question presents a change, choose the answer that first documents and evaluates impact, not the one that acts. Remember the sequence: request → log → assess impact across all knowledge areas → CCB decision → update plan/baselines → communicate → implement. Never select an option that bypasses the CCB or that changes a baseline without approval.
Mixing up contract types and who bears cost risk, for example assuming a fixed-price contract protects the buyer from all risk or that a cost-plus contract shifts risk to the seller.
Candidates memorize contract names without the risk-transfer logic. They also confuse time-and-materials with cost-reimbursable, and misidentify which contract type suits a well-defined scope versus an uncertain one.
What to do instead
Build one table mapping each contract type to who carries cost risk and when it fits: Firm Fixed Price (seller bears most risk, well-defined scope); Fixed Price Incentive Fee (shared, with performance incentives); Cost Plus Fixed Fee (buyer bears cost risk, uncertain scope); Cost Plus Incentive Fee; Time and Materials (buyer bears risk of hours, good for staff augmentation). Ask 'whose cost overrun is this?' to orient each answer.
Confusing risk response strategies, such as labeling 'accept' as 'mitigate', mixing up 'transfer' with 'share', or applying a threat strategy to an opportunity.
The strategy names are short and overlap in casual usage. Candidates also forget that opportunities have their own strategies (exploit, enhance, share, accept) and that 'avoid' means changing the plan to eliminate the threat, not merely reducing its probability.
What to do instead
Memorize two parallel lists. Threats: avoid (eliminate the threat), transfer (shift financial impact, e.g., insurance), mitigate (reduce probability or impact), accept (active or passive). Opportunities: exploit, enhance, share, accept. For each scenario, ask whether the response changes the plan (avoid/exploit), shifts ownership (transfer/share), or reduces/raises likelihood (mitigate/enhance).
Treating the critical path as the path with the most activities or the most expensive activities, or failing to recalculate float and the critical path after a schedule change.
Without a network diagram in front of them, candidates estimate by intuition. They also forget that the critical path is defined by longest duration, has zero total float, and can change when activities are compressed or delayed.
What to do instead
Define the critical path as the longest-duration path through the network, which determines the shortest project duration and has zero total float. Compute forward pass (early start/finish) and backward pass (late start/finish); total float = LS - ES or LF - EF. Whenever a question says an activity slipped, recompute float before answering, and check whether a new critical path emerged.
Answering leadership and team questions with an authoritarian or purely directive response, such as escalating to the sponsor or reassigning a team member, when the situation calls for servant leadership, coaching, or conflict resolution at the source.
Candidates project workplace instinct ('escalate it') onto exam scenarios that are designed to test the PM's interpersonal judgment. They also confuse the Tuckman stages or misread which conflict-resolution mode fits (collaborate vs. compromise vs. force).
What to do instead
Default to the least-escalatory, most-collaborative option that addresses the root cause: facilitate, coach, or use collaborate/problem-solving for conflict. Reserve force or escalation for safety or compliance issues. Know Tuckman's stages (forming, storming, norming, performing, adjourning) and recognize that storming is normal, not a failure requiring intervention by the sponsor.
Skipping closure activities, such as failing to obtain formal acceptance, archive lessons learned, release resources, or close contracts, and instead treating delivery of the product as the end of the project.
Candidates equate 'work is done' with 'project is closed.' The exam tests whether they know closure is a distinct process group with its own outputs, including final product acceptance, transition, lessons-learned repository updates, and procurement closure.
What to do instead
For any closure scenario, run the checklist: verify scope against requirements, obtain formal sign-off, transition the product to operations or the customer, close contracts (with procurement audits), release team resources, archive project documents, and capture lessons learned. If a question asks 'what should the PM do first at closure,' choose obtaining formal acceptance before releasing resources or celebrating.