PKMC Module I common mistakes
PKMC Module I · Understand the traps and how to avoid them.
When a question asks whether a change is authorized, treating any approved change request as automatically approved for execution, without checking whether the change was formally approved through integrated change control and the baseline updated.
Candidates blur the distinction between a submitted change request, a reviewed recommendation, and an approved-and-baselined change; exam stems often describe a request that has been 'approved by the sponsor' but not yet reflected in the baseline, tempting a premature 'proceed' answer.
What to do instead
For every change scenario, run a fixed checklist: was the request documented, analyzed for impact on scope, schedule, cost, quality, and risk, approved by the correct authority, and then reflected in the relevant baseline and communicated? Answer with the next step in that sequence, not the end state. Practice by writing the checklist on scratch paper before starting the section.
Confusing project life cycle phases with the process groups, and mapping 'initiation' to the first phase of the product life cycle rather than to the process group that authorizes the project.
The words 'initiation', 'planning', and 'execution' appear in both the phase and process-group vocabularies, and many candidates learn them as a single linear sequence; overlay of the two models is a known source of mis-keyed answers.
What to do instead
Draw the two-axis diagram once per study session: process groups (Initiating, Planning, Executing, Monitoring and Controlling, Closing) run across the top, and predictive phases run down the side, with the note that Monitoring and Controlling overlaps every phase. Then classify ten practice stems by asking 'is this a phase or a process group?' before answering.
Selecting the answer that describes the technically best solution rather than the answer that follows the documented process, such as choosing 'escalate to the sponsor' when the correct next step is to consult the risk register or the communications management plan.
Experienced practitioners answer from habit and organizational memory, and exam items are written to reward the process described in the project management plan; the intuitive 'just fix it' answer is usually a distractor.
What to do instead
For every scenario, first ask 'what artifact or plan governs this situation?' and choose the option that references consulting or updating that artifact. Build a one-page map of plan-to-situation pairs (risk register for threats, issue log for realized problems, stakeholder register for engagement, change log for change status) and drill it until recall is automatic.
Treating the critical path as the path with the most activities or the highest cost, and failing to recompute float after a resource leveling or fast-tracking decision changes durations.
Candidates memorize 'longest path' but do not internalize that the critical path is defined by zero total float and can shift; they also forget that leveling can extend duration while fast-tracking can add risk and rework.
What to do instead
Practice forward and backward pass on at least five networks by hand, computing early and late start and finish and total float for every node, then identify the critical path as the chain of zero-float activities. For each leveling or fast-tracking question, explicitly state which durations changed and recompute float before choosing an answer.
Mixing up earned value formulas, particularly confusing cost variance with schedule variance signs, or computing EAC with the wrong formula when the stem states that current variance is atypical.
The formulas look symmetrical and are often memorized as strings rather than as meanings; the 'atypical' versus 'typical' variance condition is a single word that flips the correct EAC formula.
What to do instead
Anchor each metric to a sentence you can say aloud: CV = EV minus AC (positive means under budget), SV = EV minus PV (positive means ahead of schedule), CPI = EV divided by AC, SPI = EV divided by PV. For forecasts, memorize two branches: atypical variance means EAC = AC plus (BAC minus EV); typical variance means EAC = BAC divided by CPI. Work ten numeric items and write the branch condition next to each answer.
Accepting a scope statement that lists deliverables without measurable acceptance criteria, or decomposing a WBS to work packages that are not estimable and assignable, and then answering later schedule and cost questions as if the baseline were sound.
Candidates focus on producing a WBS quickly and treat acceptance criteria as boilerplate; the exam then tests downstream consequences, so an unsound decomposition propagates errors into duration, cost, and control questions.
What to do instead
Apply two tests to every work package: can one person be assigned it, and can its completion be verified against written acceptance criteria? If either fails, the correct answer is to decompose further or return to requirements. Practice by critiquing three sample WBS fragments and writing the missing acceptance criterion for each deliverable.
Answering stakeholder questions with 'communicate more' or 'send a status report' instead of matching the engagement strategy to the stakeholder's power, interest, and current engagement level.
Communication feels like a generic cure-all, and candidates skip the analytical step of classifying the stakeholder and choosing the strategy the plan prescribes for that quadrant.
What to do instead
For each stakeholder stem, state power, interest, and current versus desired engagement level before reading the options, then eliminate any option that does not change the engagement level in the required direction. Memorize the strategy per quadrant: high power and high interest means manage closely; high power and low interest means keep satisfied; low power and high interest means keep informed; low power and low interest means monitor.
Choosing a risk response that does not match the risk owner's authority, such as selecting 'avoid' for a threat that cannot be eliminated, or confusing mitigation with transference when a contract shifts financial consequence but not technical ownership.
The response names sound interchangeable in casual use, and candidates do not check whether the response is feasible given the project constraints stated in the stem.
What to do instead
For each risk item, ask three questions: can the cause be eliminated (avoid), can probability or impact be reduced (mitigate), can the consequence be shifted to a third party (transfer), or is the exposure acceptable with a documented reserve (accept)? For opportunities, use exploit, enhance, share, and accept. Label ten practice risks with the response and the reason it is feasible.
Failing to distinguish contract types by risk allocation, such as recommending a firm-fixed-price contract for a project with poorly defined scope, or assuming a time-and-materials contract caps the buyer's cost exposure.
Candidates remember contract names but not who bears cost risk; the exam tests whether the chosen contract fits the clarity of the scope statement and the buyer's tolerance for overrun.
What to do instead
Build a two-column table: contract type on the left, and on the right who bears cost risk and what scope clarity it requires. Fixed-price suits well-defined scope and shifts risk to the seller; cost-reimbursable suits evolving scope and leaves risk with the buyer; time-and-materials pays for effort and does not cap cost unless a ceiling is written in. Then answer by matching scope clarity in the stem to the table.
In quality scenarios, selecting inspection or rework when the stem describes a process that is producing defects, rather than addressing the process through quality assurance and root-cause analysis.
The instinct is to catch defects at the end, and the words 'control' and 'assurance' are easily swapped; candidates also forget that quality assurance is about the process while quality control is about the output.
What to do instead
Ask whether the stem's problem is a defective deliverable (control: inspect, test, and correct) or a process generating defects (assurance: audit, analyze causes, and adjust the process). If defects recur across units, the answer must change the process, not rework more units. Practice by sorting ten quality scenarios into assurance versus control and naming the artifact each would update.