New Skill Forged: Business Analysis (BABOK v3)
New Skill Forged
A Guide to the Business Analysis Body of Knowledge (BABOK Guide) v3 by IIBA. 512 pages. The professional credential reference for business analysts — denser and more procedural than most books, but comprehensive in a way that matters when you’re actually trying to figure out what someone needs built.
BA is one of those disciplines that looks obvious from the outside (“just ask what they want”) and is genuinely hard in practice. What people say they want, what they actually want, what would actually solve their problem, and what’s technically feasible are four different things. The BABOK’s whole project is a systematic approach to closing those gaps.
What this skill teaches Claude to do:
- Apply the BACCM (Business Analysis Core Concept Model): Change, Need, Solution, Stakeholder, Value, Context — six concepts that must stay consistent with each other throughout an initiative
- Classify requirements correctly: Business (why), Stakeholder (who needs what), Solution-Functional (what the system does), Solution-Non-Functional (how well), and Transition (how to get there)
- Run elicitation like a professional: interviews that extract real information, workshops that build consensus, observation sessions that reveal what people actually do vs. what they say they do
- Build stakeholder matrices using Mendelow’s Power/Influence grid — manage closely, keep satisfied, keep informed, monitor — and construct RACI matrices that don’t collapse into everyone being “R”
- Write requirements that are actually good: atomic, complete, consistent, concise, feasible, unambiguous, testable, prioritized. The SMART++ checklist that catches the requirements that will cause rework at UAT
- Model processes in BPMN, draw context diagrams, build decision tables, and create state diagrams — the whole visual toolkit for communicating what needs to happen
The most useful concept in the book:
MoSCoW prioritization is not a feeling. Must Have means the solution FAILS without this. Should Have means there’s a workaround — painful, but it exists. Could Have is deferred by definition. Won’t Have This Time is an explicit agreement, written down, that prevents scope creep from being framed as “but you said you wanted it.”
The five perspectives:
BABOK v3 added perspective lenses for Agile, Business Intelligence, IT, Business Architecture, and BPM — because the same BA discipline applies differently in each context. A backlog refinement session and a TOGAF capability map use different vocabulary but serve the same purpose: understanding what needs to change and why.
Browse the full skill at /skills/business-analysis
Forged from 4,939 books. This is #3 of the series.