Business Analysis Core Concept Model6 September 2020
Business Analysis Planning and Monitoring22 September 2020
BABOK V3 Business Analysis Framework
To fully understand the BABOK V3 business analysis framework, we have to go back to the previous version of the BABOK® Guide – version 2. At that time, IIBA® used a slightly different definition of business analysis:
“Business analysis is a set of tasks and techniques used to work as a liaison among stakeholders to understand the structure, policies, and operations of an organization, and to recommend solutions that enable the organization to achieve its goals.”
In the previous post, I mentioned that the BABOK® Guide was created by professionals for professionals; it is based on the experience of experts in the business analysis field. The experts first identified all the tasks that a business analyst is responsible for. Next, they grouped them into the following six key knowledge areas:
-Business Analysis Planning and Monitoring,
-Elicitation and Collaboration
-Requirements Life Cycle Management
-Requirements Analysis and Design Definition
Figure 1 Business Analysis Framework
Strategy analysis, requirements analysis and design definition, and solution evaluation (depicted as an inner circle in Figure 1) form the core of the business analysis work. To perform these activities effectively, the outer circle activities are required: business analysis planning and monitoring, elicitation and collaboration, and requirements life cycle management.
Anatomy of a BABOK® knowledge area
To successfully execute tasks, a Business Analyst can use multiple techniques. Each task in BABOK® lists many techniques that Business Analysts consider when performing a task.
Also, the skill set of a Business Analyst is important. The BABOK® Guide has developed a competency scheme that addresses the essential skills for this field. The competencies listed by the BABOK® Guide help in performing the task efficiently and effectively.
We can illustrate the above-mentioned aspects in the following model:
Figure 2 Dependency between knowledge area, task, technique, and competency.
Each task within a knowledge area is defined in more detail in terms of:
-Main activities that can take place when executing a task and help to transform inputs to outputs,
-Stakeholders involved in the task,
-Guidelines and tools that a Business Analyst should consider when performing a task, and
-Techniques that may be used.
Short description of knowledge areas
Business analysis planning and monitoring
This knowledge area focuses on preparing and monitoring the execution of business analysis work. The old proverb says: “Proper preparation prevents poor performance”; in this knowledge area, we plan how to approach our activities, how to involve stakeholders, understand and document roles and responsibilities and define how to structure the information that we will obtain throughout the business analysis assignment. Additionally, knowing that we will have setbacks, we also plan how to track business analysis activities and improve them or take corrective actions when necessary.
Elicitation and collaboration
Business Analysts collaborate with stakeholders and obtain/elicit the information required to understand needs and the organizational context to develop valuable solutions. In this knowledge area, we prepare for elicitation, conduct it, and communicate results with stakeholders. We also try to keep our stakeholders involved in the initiative.
Requirements life cycle management
Requirements are rarely a one-off activity. Therefore, we have to manage requirements. The reasons are diverse, e.g., an internal/external audit, a maintenance contract with the supplier. The tasks belonging to this knowledge area are requirements prioritization and approval, setting up traceability, requirements maintenance, and change control process.
This knowledge area focuses on defining the true business need that aligns with its mission and objectives. It is about understanding what the required future situation is from the perspective of the key stakeholders. Knowing the current situation and the future situation allows us to define actions that have to occur to achieve the required future state successfully. In this area, we also perform risk management.
Requirements analysis and design definition
This knowledge area is concerned with the processing of the business analysis information we receive through the elicitation efforts. This information can be diverse; therefore, we may use models to cross-check the input and obtain sharpness on what’s required. In this knowledge area, we define the requirements, verify them, and validate them. Requirements feasibility is checked, and we also start thinking about possible solutions. Solution analysis helps us to select one with the greatest value for the stakeholders and organizations.
As we develop a solution, we must also check whether what we deliver matches the stakeholders’ expectations. In this knowledge area, we define relevant solution performance measures, execute them, and analyze the results to determine what stands in the way to make the solution valuable to the organization. We recommend actions to remove these barriers either from the solution itself or the organization to ensure maximum business value is delivered.
In this post, you have gained basic knowledge of the BABOK® business analysis framework and its six knowledge areas. You will understand the relationship between knowledge area, task, competence, and technique. The next post will provide you with a deep insight into the first knowledge area: Business Analysis Planning and Monitoring.
If you wish to get more in-depth information about these knowledge areas, competencies, or techniques, please consider buying the BABOK® Guide or become a member of the International Institute of Business Analysis. As an IIBA® member, you receive your own (electronic) copy of the BABOK® Guide for further study.
BA Coach also provides online workshops about BABOK®.
– BABOK Guide V3
– Photo by Mirko Blicke on Unsplash