GAQM APM common mistakes
GAQM APM · Understand the traps and how to avoid them.
Treating the project charter as a detailed plan and answering questions as though the charter should contain the WBS, activity durations, and a full budget breakdown, rather than accepting that the charter is a high-level authorizing document.
Candidates confuse the charter's authorizing and boundary-setting purpose with the planning artifacts that come later, often because they have seen charters in their own workplace that were overloaded with detail.
What to do instead
Memorize the charter's core contents-purpose, high-level scope, objectives, success criteria, high-level risks, summary milestones, budget authority, and the project manager's assigned authority-and practice rejecting options that place detailed schedules or the WBS inside it.
Selecting the 'do nothing' or 'escalate to the sponsor' option on situational questions about a risk or issue that the project manager has authority to handle, instead of choosing the option that applies the standard process first.
Exam questions reward process discipline; candidates who have worked in weak governance environments learn to escalate reflexively, and they misread escalation as the 'safe' answer.
What to do instead
Apply a decision rule: first identify whether the scenario is a risk (future, uncertain) or an issue (current), then pick the option that follows the documented process-log it, assess it, plan a response, communicate-and reserve escalation for authority or scope/budget thresholds the stem explicitly states.
Confusing the critical path with the longest-duration activity or with the path containing the most activities, and then computing float incorrectly on network-diagram questions.
Candidates memorize 'critical path = longest path' but do not practice forward and backward pass arithmetic, so under time pressure they substitute intuition for calculation.
What to do instead
Drill forward pass (early start/finish) and backward pass (late start/finish) on small networks until float = LS − ES = LF − EF is automatic; verify that total float on the critical path is zero and that a near-critical path with small float is not mislabeled critical.
Answering scope-control questions by choosing 'reject the change' or 'approve the change' outright instead of choosing the perform integrated change control step: assess impact on scope, schedule, cost, quality, and risk, then route to the change control board.
The exam tests the change-control process, but candidates react to the change request itself rather than to the process the project manager should follow.
What to do instead
For any change scenario, look first for the option that documents the request and evaluates its impact across the triple constraint; only then consider approval or rejection, and remember that approved changes update the baseline while unapproved work is not performed.
Mixing up quality assurance and quality control, for example selecting 'inspect the deliverables' when the question asks how to prevent defects, or selecting 'audit the process' when the question asks how to verify a completed deliverable.
Both terms sit under quality management and candidates learn them as a pair without anchoring each to its process group: assurance is executing/process-focused and preventive; control is monitoring/deliverable-focused and detective.
What to do instead
Anchor each with a one-line mnemonic: QA = audit the process, prevent defects, executing process group; QC = inspect the product, detect defects, monitoring and controlling process group. Apply the mnemonic to every quality stem before reading the options.
Treating the project management plan as a single static document rather than as an integrated, progressively elaborated plan that is baselined and then updated only through change control.
Candidates reduce the plan to a schedule or a Gantt chart and miss that subsidiary plans (scope, schedule, cost, quality, risk, communications, resources, procurement, stakeholders) must be consistent with one another.
What to do instead
Study the plan as a set of subsidiary plans plus baselines (scope, schedule, cost); on integration questions, prefer the option that reconciles subsidiary plans or follows the change-control route over one that edits a baseline directly.
Confusing the WBS with a task list or an organizational chart, and answering decomposition questions by choosing options that assign owners or sequence activities rather than break deliverables into work packages.
In practice many teams build schedules directly, so candidates never internalize that the WBS is deliverable-oriented, not activity-oriented, and that the lowest level is the work package.
What to do instead
Remember the WBS is deliverable-oriented and hierarchical, decomposed to work packages that can be estimated and assigned; sequencing and ownership belong to the schedule and the RAM/RACI, not the WBS. Reject options that mix activities or people into WBS structure.
Choosing 'accept' as the risk response whenever the risk is outside the project manager's control, without distinguishing active acceptance (contingency reserve) from passive acceptance (no action until the risk occurs) and without considering transfer via contract or insurance.
Acceptance is the default real-world response, so candidates over-apply it and ignore that the exam distinguishes acceptance subtypes and expects the most appropriate strategy given the stem's specifics.
What to do instead
Learn the negative-risk strategies (avoid, transfer, mitigate, accept) and positive-risk strategies (exploit, share, enhance, accept); for acceptance stems, check whether the option mentions a contingency reserve (active) or explicitly no action (passive), and prefer transfer when a third party can bear the financial exposure.
Skipping earned value management calculations or misapplying the formulas, for example computing CPI as EV/AC but then interpreting CPI greater than 1 as over budget, or confusing SV with SPI.
Candidates avoid the arithmetic under time pressure and rely on remembering that 'bigger is better' without checking which index or variance they are reading.
What to do instead
Memorize the core set-CV = EV − AC, SV = EV − PV, CPI = EV/AC, SPI = EV/PV, EAC = BAC/CPI when variance is atypical-and practice interpreting signs and magnitudes: positive CV and CPI above 1 mean under budget; negative SV and SPI below 1 mean behind schedule.
Treating project closure as an administrative formality and selecting options that skip lessons learned, final product verification, or formal acceptance, or that release the team before closure activities are complete.
Closure receives little attention in day-to-day delivery work, so candidates default to the fastest-sounding ending rather than the process-complete one.
What to do instead
Memorize the closure sequence: verify deliverables meet acceptance criteria, obtain formal sign-off, transfer the product or hand off to operations, archive records, capture lessons learned, release resources, and close contracts. On closure stems, prefer the option that completes verification and acceptance before releasing the team or closing contracts.