ACP Corporate common mistakes
ACP Corporate · Understand the traps and how to avoid them.
Answering questions about 'the agile mindset' by choosing the option that describes a specific ceremony or tool (daily standup, burndown chart, Jira board) rather than the underlying principle or value.
Candidates trained on framework mechanics default to the most concrete-sounding option, and corporate-context questions deliberately offer a plausible ceremony as a distractor for a mindset question.
What to do instead
Before answering, classify the stem: if it asks about mindset, culture, or behaviour, eliminate any option that names an artefact, event, or tool, then choose among the remaining options the one that describes a belief, value, or leadership behaviour. Practise by rewriting each ceremony you know as the principle it serves.
Treating corporate culture questions as generic 'agile transformation' questions and selecting the answer that says 'get executive buy-in and run a pilot', ignoring the specific cultural constraint described in the stem.
Popular transformation narratives are over-learned and feel safe, so candidates stop reading the scenario's actual constraint (e.g. a compliance-driven approval culture, a unionised workforce, a matrixed reporting line).
What to do instead
Underline the named constraint in the stem and reject any option that does not directly address it. If two options both sound transformational, prefer the one that works within the described constraint rather than the one that requires the constraint to disappear.
Choosing the highest-value or most innovative backlog item when the stem describes a dependency, a regulatory deadline, or a capacity limit that makes a lower-value item the correct next choice.
Candidates memorise 'highest value first' as a rule and apply it mechanically, missing that value-driven prioritisation in corporate settings is constrained by risk, dependencies, and compliance dates.
What to do instead
Run every prioritisation question through a three-part check: value, risk/uncertainty reduction, and hard constraints (deadline, dependency, capacity). If a hard constraint exists, it outranks raw value. Answer the question the stem asks, not the general principle.
Confusing output metrics (velocity, story points delivered, features shipped) with outcome metrics (customer behaviour change, revenue, cost avoided) when the stem asks how to demonstrate value.
Velocity and points are the most visible numbers in day-to-day agile practice, so they surface first under exam pressure even when the question is explicitly about value realisation.
What to do instead
Build a two-column mental list: output measures vs outcome measures. When a stem mentions 'demonstrate value', 'justify investment', or 'benefit realisation', eliminate every option that is an internal productivity measure. Prefer options that tie delivery to a measurable change for the customer or the business case.
Responding to a stakeholder-engagement scenario by escalating to a sponsor or adding a communication plan document, when the stem shows the real issue is an unaddressed interest or unspoken expectation of a specific stakeholder group.
Escalation and documentation are low-risk answers that feel professional, and candidates reach for them when they cannot identify the stakeholder's actual concern.
What to do instead
For each stakeholder question, first name the stakeholder's interest and influence from the stem. Then choose the option that directly engages that stakeholder (conversation, demonstration, co-design) before any option that routes around them through a plan or an escalation.
Selecting 'send a status report' or 'update the wiki' as the fix for a communication breakdown that the stem describes as a shared-understanding or feedback-timeliness problem.
Written communication is easy to prescribe and easy to grade, so it appears as a tempting distractor; candidates conflate information distribution with communication effectiveness.
What to do instead
Ask what the stem says is missing: information, shared understanding, or timely feedback. Distribution artefacts fix only the first. For shared understanding choose dialogue, visualisation, or joint review; for feedback choose shorter cycles or direct access to the decision-maker.
Answering facilitation questions by choosing the option where the Scrum Master or agile coach solves the team's problem for them, rather than the option that helps the team solve it themselves.
Candidates project the behaviour of a traditional project manager onto the role, and 'take ownership and resolve' reads as decisive and therefore correct.
What to do instead
Apply a servanthood test to every team-performance option: does it build the team's capability, or substitute for it? Prefer coaching, questioning, and creating conditions over directing. Reserve directive answers for genuine safety or compliance emergencies named in the stem.
Treating a conflict or a low-performing team member as a process problem to be fixed with a retrospective action, when the stem describes an interpersonal or capability issue requiring a direct conversation.
Retrospectives are the default improvement lever taught in agile courses, so candidates apply them to every problem, including ones a retrospective cannot reach.
What to do instead
Sort the problem type first: process, technical, interpersonal, or capability. Retrospectives address process and technical. Interpersonal issues need direct, private conversation; capability gaps need coaching or training. Choose the intervention that matches the problem class.
Producing detailed up-front estimates and a fixed plan when the stem explicitly describes high uncertainty, or conversely refusing to estimate at all when the stem describes a fixed-price contractual need.
Candidates hold a single preferred stance on estimation (either 'plan everything' or 'no estimates') and apply it regardless of the context the question supplies.
What to do instead
Match the estimation approach to the uncertainty and commitment described: range-based and progressively refined for high uncertainty, sufficient up-front sizing where a contractual commitment exists, with explicit assumptions and a re-forecast cadence. Choose the option that names the technique appropriate to the stated uncertainty level.
Missing governance and compliance cues: choosing 'self-organising team decides' when the stem involves regulatory sign-off, audit evidence, or a mandatory control, and choosing 'escalate to the PMO' when the stem involves a team-level decision within its authority.
Agile training emphasises team autonomy so strongly that candidates override it only when the word 'compliance' appears, and they miss the subtler cues (audit trail, segregation of duties, contractual acceptance criteria).
What to do instead
Scan every governance stem for named obligations before reading options. If a mandatory external obligation exists, the correct answer preserves the obligation while keeping delivery adaptive; if no obligation is named, prefer the option that keeps the decision at the lowest capable level. Never trade a named control for speed.