EXIN Agile Coach Assessment common mistakes
EXIN Agile Coach Assessment · Understand the traps and how to avoid them.
Answering scenario questions with the mechanics of one named framework (for example reciting Scrum ceremony rules) instead of articulating the underlying agile principle the question is testing.
Candidates prepare by memorising a single method they use at work and read every scenario through that lens, so they treat 'agile' as a synonym for their framework and miss the framework-agnostic intent of the item.
What to do instead
For each practice you know, write down the principle it serves and one alternative way to satisfy that principle outside your framework. Practise restating scenarios in principle language ('this is about limiting work in progress' rather than 'this is about the sprint backlog') before choosing an answer.
Treating 'Agnostic Agile' as meaning 'any process is equally valid', and selecting answers that endorse whatever a team already does.
The word 'agnostic' is misread as 'neutral about outcomes', so candidates pick permissive options that avoid judgement. The exam instead expects principled judgement: methods are context-dependent, but the values and evidence of working software are not negotiable.
What to do instead
Study the distinction between method-agnosticism and value-relativism. When an option says 'whatever the team prefers is fine', check whether it abandons empiricism, customer value, or technical quality; if it does, it is the wrong answer.
Confusing the coach's role with the Scrum Master's or delivery manager's role, and choosing answers where the coach assigns work, owns the backlog, or makes the team's decisions.
Many candidates come from a Scrum Master background where facilitation shades into ownership, and they carry that habit into coaching items that test non-directive stance and client self-determination.
What to do instead
For every scenario, ask 'who should own this decision?'. Eliminate options where the coach decides content, and prefer options where the coach raises awareness, asks powerful questions, or helps the client choose.
Jumping straight to a prescribed solution in scenario items, skipping diagnosis of whether the problem is a practice problem, a systemic/organisational problem, or an interpersonal one.
Candidates want to demonstrate knowledge, so they select the answer containing the most technique. Exam items often reward the option that first gathers data or clarifies the problem before intervening.
What to do instead
Use a mental checklist: what is observed, what is the likely root cause, what is the smallest intervention, how would we know it worked. Reject answers that apply a heavy technique before any assessment.
Describing retrospective or facilitation formats (for example 'run a starfish retrospective') as the answer when the item asks how to handle resistance, conflict, or low psychological safety.
Technique names are easy to recall and feel concrete, so they crowd out the relational and containment skills the item is actually testing. Candidates under-prepare for the human dynamics side of facilitation.
What to do instead
Build a separate revision list of facilitation stances: contracting, holding silence, surfacing conflict, separating person from position, and protecting the container. Match each to the symptom it addresses.
Missing the difference between coaching, mentoring, teaching, and advising, and picking a mentoring answer for a coaching question (or vice versa).
In practice these modes blur, and candidates answer from personal experience rather than from the definitions the exam uses. Items often hinge on whether the coach gives expertise or elicits it.
What to do instead
Learn a one-line test for each mode: coaching elicits the client's own answer, mentoring shares experience, teaching transfers knowledge, advising recommends. Then check the item's cue words ('the client already has expertise', 'the team lacks a skill') before choosing.
Assuming agile transformation is a top-down rollout and choosing answers where leadership mandates practices, teams are reorganised by decree, or maturity is declared by milestone.
Candidates conflate 'management support' with 'management directive' and believe visible sponsorship requires command-style change. The exam tests change that is co-created, incremental, and evidence-led.
What to do instead
For change questions, prefer options that combine explicit leadership sponsorship with voluntary team-level experimentation and feedback loops. Treat any answer that mandates a practice without addressing the system as suspect.
Ignoring organisational system constraints (reward structures, funding models, governance, HR policies) and answering as if a team can change its own context.
Candidates focus on team-level practices because that is where they have direct experience, and they underestimate how incentives and structures determine behaviour. Items about stalled improvement often have a systemic correct answer.
What to do instead
When a scenario shows persistent dysfunction despite good team practices, scan for structural causes: how work is funded, how people are evaluated, who approves releases. Practise naming the system lever before the team-level fix.
Selecting the answer that sounds most collaborative or most agreeable rather than the one that best serves the client's learning, for example avoiding a difficult truth to preserve rapport.
Candidates equate good coaching with being supportive and non-confrontational, so they avoid options involving challenge, direct feedback, or ending an engagement that is not working.
What to do instead
Study ethical coaching: challenge with care, contracting, boundaries, and the duty to raise what the client cannot see. When two options are both respectful, prefer the one that increases the client's awareness over the one that keeps the coach comfortable.
Treating scaling frameworks and metrics as neutral technical choices, and picking answers that add process, dashboards, or more ceremonies without questioning what problem is being solved.
Candidates associate 'deep dive into agile practices' with knowing more frameworks and metrics, so they equate sophistication with more machinery. The exam rewards matching practice to context and measuring outcomes, not activity.
What to do instead
For every practice or metric option, ask what decision it improves and what behaviour it might distort. Prefer answers that tie measurement to customer or flow outcomes and that remove work rather than add it.