Traditional business analysis assumes a document-heavy handoff: gather requirements, write them up, hand them to development. Agile teams don’t work that way, and the AAC certification exists because analysis skill doesn’t disappear in agile delivery — it just changes shape.
What Changes in Agile Analysis
Instead of a complete requirements document up front, analysis happens continuously — refining a backlog, clarifying acceptance criteria just before a story is built, adjusting based on what a sprint review reveals. The skill is the same; the timing and format are completely different.
Who This Actually Suits
- BAs whose organization has moved to Scrum, Kanban, or a hybrid delivery model
- Product owners who need structured analysis skills, not just backlog prioritization
- CBAP or CCBA holders adding agile credibility to a traditional BA background
Not a Replacement for the Core Credentials
AAC is a specialization layered on top of core BA competency, not a substitute for it — the exam assumes you already understand fundamental analysis techniques and tests how you’d apply them in an iterative, agile context.
Where to Start Instead
If you haven’t earned a core certification yet, see our breakdown of ECBA, CCBA, and CBAP before pursuing this specialization.
Full Details
Eligibility and exam content are on the official IIBA website.
