BABOK® Guide v. 3, Task by Knowledge Area
Presented here are the business analysis tasks identified in the BABOK® Guide v. 3 by knowledge area. It is important to understand that these are not linear processes; rather, they are iterative and ongoing. Use this list as a checklist to make sure that all BA tasks have been considered in BA planning. This does not mean that every task will apply to every project. Consciously deciding not to perform a task is far better than forgetting and needing to make changes in order to accommodate it in the plan later.
The final column shows examples of activities the business analyst is planning based on one fictional project in order to demonstrate how this list can aid in business analysis planning. It serves as a checklist of sorts.
BABOK® Guide Chapter |
Knowledge Area/Task |
Sample Activity for Proposed Project |
3 |
Planning & Monitoring |
|
3.1 |
Plan Business Analysis Approach |
Meet with PM to discuss, create BA Plan for stakeholder review |
3.2 |
Plan Stakeholder Engagement |
Series of interviews/surveys to identify and analyze |
3.3 |
Plan Business Analysis Governance |
Work with project leadership and stakeholders to define and recommend BA processes and governance for decision making. Get approval |
3.4 |
Plan Business Analysis Information Management |
Revisit plan for XYZ project, adjust as necessary |
3.5 |
Identify Business Analysis Performance Improvements |
Review status with PM monthly, reach out for feedback from stakeholders as needed |
Elicitation and Collaboration |
||
4.1 |
Plan for Elicitation |
Use Stakeholder Analysis and Scope Diagram to determine needs |
4.2 |
Conduct Elicitation |
Per 4.1 |
4.3 |
Confirm Elicitation Results |
Per 4.1 |
4.4 |
Communicate Business Analysis Information |
Included in 3.1, 3.2, and 4.1 |
4.5 |
Management Stakeholder Collaboration |
Included in 3.2 and 4.1 |
5 |
Requirements Life Cycle Management |
|
5.1 |
Trace Requirements |
Per 3.1 and 3.4 |
5.2 |
Maintain Requirements |
Per 3.1 and 3.4 |
5.3 |
Prioritize Requirements |
Use MoSCoW, capture in 5.1, see also 3.1 |
5.4 |
Assess Requirements Changes |
Per 6.4 |
5.5 |
Approve Requirements |
Per 3.1, 3.3, 4.5, and 4.4 |
6 |
Strategy Analysis |
|
6.1 |
Analyze Current State |
Completed |
6.2 |
Define Future State |
Completed |
6.3 |
Assess Risks |
Initial complete, frequent review of risk register |
6.4 |
Define Change Strategy |
Create Change Control Plan with PM, see also 3.3 |
7 |
Requirements Analysis and Design Definition |
|
7.1 |
Specify and Model Requirements |
Per 3.1 |
7.2 |
Verify Requirements |
Per 3.1 |
Validate Requirements |
Per 3.1 |
|
7.4 |
Define Requirements Architecture |
Per 3.1 |
7.5 |
Define Design Options |
Work with UX Design |
7.6 |
Analyze Potential Value and Recommend Solution |
Requirements review, walkthrough UX Design with business |
8 |
Solution Evaluation |
|
8.1 |
Measure Solution Performance |
Create postimplementation review plan |
8.2 |
Analyze Performance Measures |
Per 8.1 |
8.3 |
Assess Solution Limitations |
Per 8.1 |
8.4 |
Assess Enterprise Limitations |
Per 8.1 |
8.5 |
Recommend Actions to Increase Solution Value |
Per 8.1 |