IIBA-AAC common mistakes
IIBA-AAC · Understand the traps and how to avoid them.
Treating the BACCM (Business Analysis Core Concept Model) as a memorized list of six nouns and writing definitions of each, instead of using the concepts to reason about a specific change.
The six core concepts (change, need, solution, stakeholder, value, context) are easy to recall and candidates assume recall equals competence, so they answer with textbook definitions rather than applying the model to the situation in the question.
What to do instead
For every scenario question, explicitly ask which core concept the question is probing (is it about the need, the solution, the value, the stakeholders, the context, or the change?) and choose the answer that shows the six concepts are interdependent. Practice writing one sentence per concept about a real change you know, then explain how changing one concept forces a change in the others.
Answering with a predictive, plan-first behaviour (produce a complete requirements specification, then hand off) when the question describes a volatile, high-uncertainty context.
Many candidates come from a traditional business analysis background and default to their habitual workflow; the exam rewards choosing the approach that fits the context, not the approach the candidate is most comfortable with.
What to do instead
Before choosing, scan the stem for context signals: rate of change, regulatory constraints, team size, access to stakeholders, consequence of failure. Then deliberately rank the candidate answers from most to least adaptive and pick the one that matches the signals. If the stem shows high uncertainty and frequent feedback, the answer that shortens the feedback loop is almost always correct.
Confusing the product backlog, the solution backlog, and the change backlog, and treating them as interchangeable lists of user stories.
The terminology overlaps with Scrum and Kanban vocabulary the candidate already knows, so they map new terms onto familiar ones and lose the distinction between work that delivers a solution and work that changes the enterprise itself.
What to do instead
Build a one-page comparison of the backlog types in this exam's language: what each contains, who owns it, and what 'done' means for each. When a question names a backlog, ask 'is this about changing the enterprise or about building a solution?' and eliminate answers that mix the two purposes.
Choosing the answer that maximizes documentation or ceremony (full traceability matrix, formal sign-off on every increment) regardless of the value the activity adds.
Candidates equate thoroughness with correctness and assume more artefacts means more rigorous analysis; the exam instead tests whether the analyst can select the lightest sufficient set of practices for the context.
What to do instead
For each practice you are tempted to choose, ask 'what decision does this artefact enable, and who makes it?' If no one can name the decision, the practice is overhead. Practice eliminating answers that add artefacts without naming the decision they support or the risk they reduce.
Ignoring the stakeholder dimension and picking a technically sound answer that no one has agreed to, or that bypasses a group whose buy-in is required.
Analysts are trained to solve the problem, and the satisfaction of a clean technical answer crowds out the political and social reality that the exam repeatedly tests through stakeholder questions.
What to do instead
Before selecting, list every stakeholder named or implied in the stem and ask 'does this answer require anyone's agreement, and does it get it?' Eliminate answers that impose a solution, skip a decision-maker, or assume consensus that the stem has not shown.
Treating 'value' as revenue only and rejecting answers that describe learning, risk reduction, or option value as the primary benefit.
Value is often reduced to financial return in candidates' minds, so answers that frame an early increment as buying information or reducing uncertainty look weaker than they are.
What to do instead
Write out the several ways value can show up: revenue, cost avoidance, risk reduction, compliance, learning that changes future decisions, and optionality. When two answers both deliver value, prefer the one that also reduces uncertainty earliest, and check whether the stem's context makes learning the dominant value.
Answering 'the analyst writes the user stories and the team estimates them' as a fixed division of labour, rather than choosing the collaboration pattern the context calls for.
Candidates carry role assumptions from their own organizations and mistake a common practice for a rule the exam endorses.
What to do instead
Frame backlog refinement as a conversation whose participants depend on the context: who holds the domain knowledge, who holds the technical knowledge, and what decision is being made. Select answers that put the people with the relevant knowledge in the conversation at the moment the decision is made, and be suspicious of any answer that hard-codes a single role.
Failing to distinguish 'doing agile' from 'being agile' and endorsing answers that add a ceremony (daily standup, retrospective) as the fix for a behavioural problem.
Ceremonies are concrete and easy to select, so candidates reach for a visible practice when the stem describes a deeper issue such as misaligned priorities or missing trust.
What to do instead
When a stem describes a symptom (slow decisions, low trust, unclear priorities), ask what underlying behaviour would have to change and whether the proposed ceremony changes it. Prefer answers that alter how decisions are made, how information flows, or how feedback is used over answers that add a meeting.
Reading the answer choices before forming a view of the situation, then rationalizing the most familiar-sounding option.
Answer choices in this exam are written to be plausible, and familiarity is a strong distractor; the candidate who reads options first anchors on one and stops reasoning.
What to do instead
Cover the options, state in one sentence what the situation requires and why, then uncover and eliminate. If two options survive, re-read the stem for the constraint you missed (a deadline, a regulator, a stakeholder who has not been consulted) rather than flipping a coin.
Skipping practice on the exam's scenario style and studying only definitions, so the candidate knows the vocabulary but cannot reason through a multi-sentence case.
Definition lists feel productive and are easy to self-test, while scenario reasoning is uncomfortable and hard to grade alone, so preparation drifts toward the comfortable activity.
What to do instead
Spend most study time writing short justifications for scenario answers and comparing them against the reasoning the exam rewards: context first, then the concept being tested, then the option that best fits. Keep a log of every question you got wrong, recording the reasoning error rather than the topic, and review the log weekly.