Business Analysis Core Concept Model (BACCM)

BACCM is a conceptual framework for the business analysis profession. This model carries details of what business analysis is and what it means to those who per perform business analysis tasks regardless the industry.

The model contains 6 core concepts - Need, Solution, Stakeholder, Context, Value and Change.
Each core concept is fundamental to the business analysis practice and are equally important. 

Below is the BACCM -

(Source: BABOC)

To begin with let me explain what each concept means -

1. Need - This is the problem or the opportunity that need to be addressed. Need motivates the stakeholders to think of a solution which adds value to the organization by solving the problem or benefit the opportunity.
2. Solution - This is the specific way(s) of addressing or satisfying one or more needs. Solution should solve the problem or help the stakeholders to achieve the benefit of the opportunity.
3. Stakeholder - Stakeholder is defined as individual or group of individuals who are interested in, influenced or impacted by the change. Stakeholders have a relationship to the need, solution and change. 
4. Context - This is where the change happens. The context is everything relevant to the change that is within the environment. Context may include attitudes, behaviors, beliefs, competitors, culture, demographics, goals, governments, infrastructure, languages, losses, processes, products, projects, sales, seasons, terminology, technology, weather, and any other element meeting the definition. (Source: BABOC)
5. Value - The importance or usefulness of something to a stakeholder within a context. Value can be tangible or intangible. Tangible value is directly measurable. Tangible value often has a significant monetary component. Intangible value is measured indirectly. Intangible value often has a significant motivational component, such as a company's reputation or employee morale. (Source: BABOC)
6. Change - The act of transformation in response to a need.

Now let me talk to you how BAs should apply the above said 6 core concepts in to business analysis practice.

1. Need - The BA should first understand the need which the organization want to satisfy by building this solution. Further BA should understand the problems which he/she may encounter while satisfying this need.
2. Solution - What are the existing solutions in the market? What products do the competitors use to solve the same problem? Should we build a product from the scratch or can we make a change to the existing solution and satisfy the need? What’s the justification for the final decision which the BA take on the solution?
3. Stakeholder - Who are the stakeholders who are interested in, influenced by or infected by the change? In what capacity are they involved?
4. Value - What is the expectation of the stakeholders and why do they want to achieve it? How would the BA could present the value (delivered or yet to deliver) to the stakeholders in an understandable format?
5. Change - What are the changed required to achieve the need of the stakeholders? What the process of achieving the change? When do the business require this change - Is it an urgent change?
6. Context -  What is the context(s) in which the solution function? Different geo locations/ cultures/ terminologies/ processors etc.

This article would be useful for anyone interested in business analysis practice. Further this model is a part of the IIBA exams scnedule.

So let me know your thoughts.

06 Types of Business Analysts

To begin with who is a Business Analyst? A Business Analyst is any individual who perform business analysis tasks as mentioned in the BABOK guide. 

However, based on the behaviors showcased while attending to business analysis tasks, business analysts can be categorized in to several types-

1. Note Taker Business Analyst
2. Brick Wall Business Analyst
3. Technical Business Analyst
4. Librarian Business Analyst
5. Professor Business Analyst
6. Specialist Business Analyst

Note Taker Business Analyst

This is normally the business analyst who just entered to the arena of business analysts.  They write down everything people ask them to write down. They do not evaluate what the stakeholders mention or say no to anything they say.

However, we all start right there but along with time and experience moved forward.

Brick Wall Business Analyst

This type of analysts is must concerned about the SCOPE and the BUDGET of the project. Yes, exactly she/he is playing more of the role of a Project Manager. Such individuals are do not try to analyst the need of the stakeholders with the intention of creating VALUE which is the core responsibility of a Business Analyst.

However, such business analysts much useful when it comes to managing the stakeholders who need everything starting from the sun to the moon and universe because delivering some value to the stakeholders within a year is better than trying to understand all the needs and delivering value in another 10 years.

Technical Business Analyst

This type of business analysts starts analyzing the technology and design before understanding the core need of the stakeholders. This mostly happen to the software engineers who change their track to Business Analyst at a later point in their career. They try to solutionism before eliciting the requirement and end up developing a complex solution which is not required by anyone. For example, they will write requirements to implement a mansion when the requirement is a hut or a rocket to travel 10 KMs when the requirement is a bicycle.

These individuals should get in to the technical track and become solution architects. 

Librarian Business Analyst

This type of business analysts creates very accurate documents which are very clear and carry every little detail. The only pain is reading those documents as they are mini bibles which takes much time to read. In certain project environments such business analysts become bottleneck to the project as the documents are not ready for review and sign off for the initiation of the project.
These analysts hate Agile Project Management Methodology as it requires minimal documentation.

Professor Business Analyst

These individuals love building theories around the requirements discussions. They are visionary and much passionate about the solution. However, this type of business analysts should be controlled by another Business Analyst or Project Manager as unless properly managed a complex theory shall be documents which doesn't add much value to the stakeholders or business.

  

Specialist Business Analyst

This type of business consultants are the best to work with as they add much value to the project. Some business analysts are Business Process Model and Notation (BPMN) specialists and they work hard to do the process flows for the entire project. Some analysts are data specialists and they work towards perfecting the inflow and out flow of data. These business analysts create value to the business.

I am an intersection of librarian business analyst and specialist business analyst. 

What about you?