Many Business Analyst’s who got their CBAP or CCBA certification with the BABOK version 2 would like to know what has changed in BABOK version 3.
BABOK version 3 was released in April 2015, and it included many changes, some of these changes included the addition of 16 new techniques, and five new perspectives on Business Analysis.
Here is a detailed comparison of the differences between the knowledge areas and the tasks in BABOK v2 and BABOK v3.
BABOK Version 2 | BABOK Version 3 |
2.0 BA Planning and Monitoring – v2.0 tasks | 3.0 BA Planning and Monitoring – v3.0 tasks |
2.1 Plan Business Analysis Approach | 3.1 Plan Business Analysis Approach |
2.2 Conduct Stakeholder Analysis | 3.2 Plan Stakeholder Engagement |
2.3 Plan Business Analysis Activities | 3.3 Plan Business Analysis Governance |
2.4 Plan Business Analysis Communication | 3.4 Plan Business Analysis Information Management |
2.5 Plan Requirements Management Process | 3.5 Communicate Requirements |
2.6 Manage Business Analysis Performance | |
3.0 Elicitation – v2.0 tasks | 4.0 Elicitation and Collaboration – v3.0 tasks |
3.1 Prepare for Elicitation | 4.1 Prepare for Elicitation |
3.2 Conduct Elicitation Activity | 4.2 Conduct Elicitation |
3.3 Document Elicitation Results | 4.3 Confirm Elicitation Results |
3.4 Confirm Elicitation Results | 4.4 Communicate Business Analysis Information |
3.5 Communicate Requirements | 4.5 Manage Stakeholder Collaboration |
4.0 Requirements Management and Communication – v2.0 tasks | 5.0 Requirements Life Cycle Management – v.3.0 tasks |
4.1 Manage Solution Scope and Requirements | 5.1 Trace Requirements |
4.2 Manage Requirements | 5.2 Maintain Requirements |
4.3 Maintain Requirements for Re-Use | 5.3 Prioritize Requirements |
4.4 Prepare Requirements Package | 5.4 Assess Requirements Changes |
4.5 Communicate Requirements | 5.5 Approve Requirements |
5.0 Enterprise Analysis – v2.0 tasks | 6.0 Strategy Analysis – v3.0 tasks |
5.1 Define Business Need | 6.1 Analyze Current State |
5.2 Assess Capability Gaps | 6.2 Define Future State |
5.3 Determine Solution Approach | 6.3 Assess Risks |
5.4 Define Solution Scope | 6.4 Define Change Strategy |
5.5 Define Business Case | 6.5 Verify Requirements |
6.6 Validate Requirements | |
6.0 Requirements Analysis – v2.0 tasks | 7.0 Requirements Analysis and Design Definition – v3.0 tasks |
6.1 Prioritize Requirements | 7.1 Specify and Model Requirements |
6.2 Organize Requirements | 7.2 Verify Requirements |
6.3 Specify and Model Requirements | 7.3 Validate Requirements |
6.4 Define Assumptions and Constraints | 7.4 Define Requirements Architecture |
6.5 Verify Requirements | 7.5 Define Design Options |
6.6 Validate Requirements | 7.6 Analyze Potential Value and Recommend Solution |
7.0 Solution Assessment & Validation – v2.0 tasks | 8.0 Solution Evaluation – v3.0 tasks |
7.1 Assess Proposed Solution | 8.1 Measure Solution Performance |
7.2 Allocate Requirements | 8.2 Analyze Performance Measures |
7.3 Assess Organizational Readiness | 8.3 Assess Solution Limitations |
7.4 Define Transition Requirements | 8.4 Assess Enterprise Limitations |
7.5 Validate Solution | 8.5 Recommend Actions to Increase Solution Value |
7.6 Evaluate Solution Performance |