BABOK® Guide
Traditional FrameworkBest For: Structured enterprise environments, certification preparation
Learn More →Master BABOK, Agile, Design Thinking, and improvement methodologies that guide business analysis practice. These frameworks provide structured approaches to requirements, stakeholder engagement, and solution evaluation across diverse project contexts and organisational environments.
Explore frameworks below to find the right approach for your project context and organisational methodology
Best For: Structured enterprise environments, certification preparation
Learn More →Best For: Fast-paced software projects, iterative development
Learn More →Best For: User-centred design, innovation projects
Learn More →Best For: Regulated industries, fixed-scope projects
Learn More →Best For: Operational efficiency, quality improvement
Learn More →Best For: Large enterprise agile transformations
Learn More →BABOK® Guide v3 remains the definitive reference for business analysis professionals. Rather than releasing a version 4, IIBA has adopted a modular approach with The Business Analysis Standard, KnowledgeHub, and frequently-updated resources designed for specific roles and challenges.
The Business Analysis Body of Knowledge (BABOK® Guide v3) is the globally recognised standard for the practice of business analysis. Published by IIBA, it defines six knowledge areas and provides techniques for requirements elicitation, stakeholder engagement, and solution evaluation.
Rather than releasing BABOK Guide v4, IIBA has evolved to a modular ecosystem ensuring professionals access current, relevant content without waiting for major version releases:
BABOK is descriptive not prescriptive, with tasks performed in any order. The framework scales from small projects to enterprise transformations and adapts to any methodology. Choose BABOK for comprehensive strategic knowledge at enterprise level, particularly in structured enterprise environments and when pursuing CBAP/CCBA certification.
Start by joining IIBA (free membership available) and downloading the BABOK Guide. Focus on one knowledge area at a time, beginning with Elicitation and Collaboration as it's most applicable to daily work. Consider ECBA certification as an entry point before pursuing CCBA or CBAP.
Yes! BABOK is methodology-agnostic. The Agile Extension to BABOK Guide provides specific guidance for applying BA practices in agile environments. Many BABOK techniques (user stories, backlog management, acceptance criteria) directly support agile workflows.
ECBA exam costs approximately $125 (IIBA members), CCBA around $325, and CBAP around $450. Add study materials ($200–500) and training courses (optional, $500–2000). Total investment for CBAP preparation typically ranges from $1,000–3,000.
71% of BAs now practise agile approaches — this is essential knowledge, not optional specialisation.
In Scrum, BAs typically work as Development Team Members participating in all sprint activities while specialising in analysis. In SAFe, BA work is distributed across Product Management and Product Owner roles. With 71% of BAs now practising agile approaches, this has become essential knowledge rather than optional specialisation.
BAs should attend all sprint ceremonies (planning, daily standups, reviews, retrospectives) to maintain context and build team relationships.
Traditional BA work emphasises comprehensive upfront requirements documentation. Agile BA work focuses on continuous collaboration, iterative refinement, and just-in-time requirements through user stories with acceptance criteria. Both require strong analytical skills, but agile demands greater stakeholder availability and tolerance for ambiguity.
Design Thinking complements traditional BA techniques by ensuring solutions address real user pain points, not just stated requirements.
Design Thinking offers human-centred innovation through five stages: Empathize (user research), Define (problem statement), Ideate (brainstorming), Prototype (low-fidelity testing), and Test (gather feedback). Key tools include empathy mapping, personas, and customer journey mapping.
BAs integrate Design Thinking during requirements elicitation to uncover user needs, solution ideation to generate creative options, and prototype validation before full development. This human-centred approach complements traditional BA techniques by ensuring solutions truly address user pain points rather than just stated requirements.
| Framework | Best For | Learning Curve | Certification |
|---|---|---|---|
| BABOK® | Enterprise, Traditional | High | CBAP, CCBA |
| Agile/Scrum | Software, Iterative | Medium | PMI-ACP, CSM |
| Design Thinking | Innovation, UX | Low–Medium | Various |
| Waterfall | Regulated, Fixed Scope | Low | PMP |
| Lean Six Sigma | Process Improvement | Medium–High | LSS Belts |
| SAFe® | Scaled Enterprise Agile | Medium–High | SAFe POPM, SA |
Traditional waterfall methodology remains relevant for projects with stable requirements, regulated environments requiring extensive documentation, or contexts where sequential phases provide appropriate governance. Understanding waterfall principles proves essential even in predominantly Agile organisations.
Many organisations operate hybrid models, applying Agile for development whilst maintaining waterfall governance for portfolio management—requiring BAs comfortable navigating both paradigms.
Lean principles focus on eliminating waste and maximising value delivery, whilst Six Sigma emphasises reducing variation and defects through data-driven process improvement. Business analysts apply these methodologies when analysing process efficiency, identifying improvement opportunities, or leading operational excellence initiatives.
These frameworks prove particularly valuable in manufacturing, healthcare, and financial services where process optimisation directly impacts profitability and compliance.
SAFe extends agile beyond the single team, coordinating multiple teams within an Agile Release Train to deliver value at enterprise scale.
The Scaled Agile Framework (SAFe) applies Lean and Agile principles across large organisations running many teams in parallel. Traditional BA responsibilities are distributed across SAFe roles — most often the Product Owner (team-level backlog and acceptance) and Product Management (programme-level features and roadmap). Many BAs transition naturally into these roles, bringing requirements rigour to a scaled environment.
PI Planning is the heartbeat of SAFe. BAs add the most value here by ensuring features are well-defined, dependencies are visible, and business objectives are clearly understood before the increment begins.
SAFe suits large enterprises coordinating dozens of teams towards shared objectives — common in financial services, government, and telecommunications. It provides the governance and alignment that single-team Scrum lacks, at the cost of additional process overhead, so it is best reserved for genuinely large-scale delivery rather than small product teams.
Explore learning paths and certifications for each framework