COPR ACP common mistakes
COPR ACP · Understand the traps and how to avoid them.
When asked what the agile lead should do next in a scenario, the candidate picks the action that maximizes speed or output (add people, skip the retrospective, cut the demo) instead of the action that maximizes delivered value or learning.
Candidates carry traditional delivery instincts into the exam and treat 'faster' as always correct; they miss that value-driven options (slice smaller, validate with the customer, stop low-value work) are the intended answers.
What to do instead
Before answering, ask 'which option changes what the customer receives or learns?' Eliminate options that only increase throughput without validating value, and prefer options that reprioritize, slice, or remove waste. Practice by writing the value rationale for each answer choice.
The candidate answers stakeholder questions with 'send a status report' or 'escalate to the sponsor' rather than choosing direct, frequent, two-way engagement such as a working session, a demo, or a conversation with the affected group.
Reporting feels safe and measurable, so it looks like a professional answer; candidates also default to hierarchy (escalation) when a stakeholder is unhappy or disengaged.
What to do instead
Classify each stakeholder option as push (report), pull (repository), or interactive (conversation), and favor interactive for anything involving ambiguity, conflict, or feedback. When a stakeholder is disengaged, choose the option that increases direct contact and involvement in reviews, not the one that documents more.
The candidate selects a command-and-control response to a team problem: reassign tasks, direct the approach, add approval gates, or tell the team the answer, instead of coaching, removing impediments, or letting the team self-organize.
Scenarios often describe real pressure (missed dates, conflict, junior members), and the directive option reads as decisive leadership; candidates confuse being accountable with making decisions for the team.
What to do instead
In servant-leadership items, prefer the option that asks questions, removes blockers, or builds capability, and reject options that decide technical approach for the team. If two options both seem supportive, pick the one that increases the team's own ability to solve the problem next time.
The candidate treats the retrospective as the only continuous-improvement mechanism and picks 'hold a retrospective' or 'create an action item' when the scenario calls for a change to the work itself, such as limiting work in progress, fixing a definition of done, or addressing a quality defect at its source.
Retrospectives are the most familiar agile ceremony, so they become a default answer; candidates also treat improvement as a meeting output rather than a change to the system of work.
What to do instead
For improvement items, ask whether the problem is in the process (WIP limits, flow, policies), the product (definition of done, test coverage, technical debt), or the team (skills, safety). Choose the option that changes the underlying system, and treat 'schedule a meeting to discuss' as a weak distractor unless the scenario explicitly lacks team input.
The candidate responds to a risk or compliance scenario by ignoring the constraint in favor of pure agility, or by freezing the process in favor of pure control, instead of choosing an adaptive option that satisfies the obligation while preserving inspection and adaptation.
Exam scenarios set up a tension between governance and agility, and candidates pick whichever value they hold more strongly rather than looking for the option that meets the requirement with the least disruption to feedback loops.
What to do instead
For each risk item, name the non-negotiable obligation first (regulatory, contractual, safety), then choose the option that embeds it in the team's routine, such as compliance criteria in the definition of done or a risk-adjusted backlog item, rather than a separate phase or an exemption.
The candidate answers 'add more people', 'work overtime', or 'increase the iteration length' when a team is missing commitments, instead of addressing capacity, work-in-progress, estimation quality, or the scope of the commitment.
These are intuitive remedies for schedule pressure, and the exam's 'adaptive planning' items are designed so that the comfortable remedy is the wrong one; candidates also forget that velocity is a planning input, not a target to be raised.
What to do instead
When throughput is short, prefer options that reduce scope, limit WIP, make the plan transparent, or re-forecast with the team. Reject options that add resources to a late project, extend the timebox to fit the work, or treat velocity as a performance metric.
The candidate spots a problem (a defect trend, a blocked item, a rising cycle time) and chooses to log it, document it, or raise it at the next ceremony instead of choosing the smallest action that resolves or contains it now.
Candidates read the scenario as a process question and answer with a reporting step; they also fear overreacting and pick the most cautious option, which is usually the least effective one.
What to do instead
For problem-detection items, ask 'what stops this from getting worse today?' and choose the option that acts on the cause or contains the impact, with escalation only when authority is genuinely required. Treat 'record and monitor' as a distractor unless the problem is explicitly low-impact and already owned.
The candidate answers definitional items from vague memory, confusing related concepts such as a definition of done versus acceptance criteria, an iteration review versus a retrospective, or a task board versus a kanban system with explicit policies.
These terms are used loosely in practice, so candidates have working definitions that are close but not precise, and the exam offers plausible near-misses as distractors.
What to do instead
Build a one-line contrast for each confusable pair covering purpose, audience, and timing, and test yourself by explaining why the other option is wrong, not just why yours is right. Revisit any pair you cannot contrast in one sentence.
The candidate reads only the last sentence of a scenario and answers the question that was asked there, missing the constraint stated earlier (a fixed regulatory deadline, a distributed team, a stakeholder who refuses to attend reviews).
Scenarios are long and the question stem comes last, so under time pressure candidates skim to the question and pattern-match to a familiar answer.
What to do instead
Read the question stem first, then read the scenario hunting for the constraint that eliminates options. Before selecting, state to yourself which stated fact rules out each rejected option; if you cannot cite one, re-read the scenario.
The candidate chooses the option that sounds most collaborative in every item, including items where the correct answer is to make a decision, escalate a genuine impediment, or say no to a stakeholder request that violates a constraint.
Agile training emphasizes collaboration and consensus, so candidates over-apply it and avoid options that involve conflict, refusal, or authority, even when the scenario requires them.
What to do instead
Distinguish collaboration (working with people to reach a better answer) from avoidance (deferring a decision or pleasing a stakeholder). When a constraint is being violated or an impediment exceeds the team's authority, choose the option that addresses it directly and transparently, and reserve consensual options for genuine ambiguity.