ACPV common mistakes
ACPV · Understand the traps and how to avoid them.
Treating value engineering as a cost-cutting exercise and selecting the option with the lowest first cost rather than the best ratio of function to whole-life resource use.
Candidates carry over a procurement mindset where 'value' is synonymous with 'cheapest', and the exam deliberately offers a low-cost option that degrades required function.
What to do instead
Before answering, restate the function in measurable terms and test each option against it; eliminate any option that fails the function, then compare surviving options on cost per unit of function delivered over the full life cycle.
Confusing value engineering with value analysis timing, and applying VE at the wrong phase of the asset or project life cycle.
The two terms are often used interchangeably in practice, and candidates do not anchor each to its typical trigger point (early design/creation versus review of an existing asset).
What to do instead
Memorise the trigger logic: VE is applied proactively during concept and design when change is cheap; value analysis is applied to existing products, processes, or assets. Match the scenario's timing cue to the correct term.
Computing earned value metrics from the wrong baseline or mixing units, then reporting a favourable cost variance when the schedule is actually slipping.
Candidates grab the first numbers in the stem and apply formulas mechanically without checking whether the figures are cumulative, period-based, or expressed in different currencies or labour hours.
What to do instead
Write the three base quantities (PV, EV, AC) explicitly with their units and as-of date before calculating; verify all three refer to the same scope baseline and same reporting date; sanity-check that CPI and SPI direction matches the narrative.
Using the critical path as the only schedule risk indicator and ignoring near-critical paths and float consumption.
Critical path method is the most rehearsed technique, so candidates default to it and overlook that a near-critical path with small total float can become critical after a modest delay.
What to do instead
In schedule-risk questions, list total float for all paths, identify paths within the risk threshold of zero float, and evaluate delay scenarios against those paths, not only the longest one.
Selecting a risk response that does not match the risk's location on the probability-impact matrix, such as accepting a high-severity threat with no contingency plan.
Candidates pick the response that sounds most proactive (usually 'mitigate') without checking whether the residual exposure after the response is acceptable or whether the response is even within the project's authority.
What to do instead
For each risk, state the pre-response rating, name the response strategy, then state the expected post-response rating and the owner; reject options that leave a high rating with no transfer, avoidance, or funded contingency.
Treating qualitative risk scoring as a substitute for quantitative analysis when the decision involves significant financial exposure, and answering as if a heat map alone justifies the choice.
Heat maps are quick and visually familiar, so candidates stop there and do not recognise stems that describe monetary thresholds, confidence levels, or expected monetary value.
What to do instead
Look for decision cues: if the stem gives probabilities and monetary outcomes, compute expected monetary value or a decision-tree rollback; if it gives a confidence target, expect Monte Carlo or a contingency reserve derived from a percentile.
Answering stakeholder questions by choosing the communication action that is most frequent rather than the one matched to the stakeholder's influence, interest, and information needs.
Candidates equate good engagement with maximum communication, and the exam offers plausible 'communicate more often' distractors.
What to do instead
Classify the stakeholder on influence and interest first, then choose the engagement level and channel that classification warrants; prefer options that tailor content and cadence to the identified need over blanket frequency.
Resolving a team conflict by escalating to the sponsor or imposing a decision when the situation calls for the team to resolve it collaboratively.
Escalation feels decisive and safe under exam time pressure, and candidates underestimate how often the correct answer is collaborative problem-solving or confronting the issue directly.
What to do instead
Rank conflict approaches by the durability of the outcome for the described situation; choose forcing or escalation only when there is a safety, legal, or irreversible-deadline constraint stated in the stem.
Applying the law or a regulator's rule as the sole ethical test and missing that a proposed action is legal but still conflicts with the professional code of conduct.
Candidates conflate compliance with ethics, and the exam presents scenarios where the action is permitted but involves undisclosed conflicts of interest or misleading reporting.
What to do instead
Run two tests on every option: is it lawful, and is it consistent with honesty, objectivity, confidentiality, and competence obligations? Reject any option that passes only the legal test.
Handling a suspected conflict of interest or a request to alter reported data by choosing silence or informal verbal pushback instead of a documented disclosure and escalation through the proper channel.
Candidates want to appear cooperative and avoid confrontation, so they select the low-friction option, which the exam treats as a failure of professional conduct.
What to do instead
Default to the sequence: disclose in writing to the appropriate authority, recuse where objectivity is compromised, and preserve a record; choose the option that protects the integrity of the reported information even if it is uncomfortable.
Mixing governance roles, such as assigning accountability for benefits realisation to the project manager rather than the business owner or sponsor.
Candidates map all accountability onto the project manager because that is the role they know best, and they overlook the separation between delivery and benefits ownership.
What to do instead
Anchor roles explicitly: the project manager is accountable for delivery within constraints, the sponsor or business owner for benefits realisation and continued business justification; reject options that blur these.
Treating the project charter and the business case as interchangeable, and answering as if the charter alone authorises continued investment after a stage gate.
Both documents are created early and both mention objectives, so candidates conflate authorisation to proceed with justification of the investment.
What to do instead
Distinguish purpose: the business case justifies the investment and is revisited at gates; the charter authorises the project and names the project manager. Match the stem's question to the document whose purpose it describes.