Skip to content
Browse
The Standard
BABOK Guide
BABOK Applied
Agile Extension
Business Data Analytics
Product Ownership Analysis
The Standard
BABOK Guide
BABOK Applied
Agile Extension
Business Data Analytics
Product Ownership Analysis
Business Analysis Task Navigation
Understanding the Task Cards Plan Business Analysis Approach Plan Stakeholder Engagement Plan Business Analysis Governance Plan Business Analysis Information Management Identify Business Analysis Performance Improvements Prepare for Elicitation Conduct Elicitation Confirm Elicitation Results Communicate Business Analysis Information Manage Stakeholder Collaboration Trace Requirements and Designs Maintain Requirements and Designs Prioritize Requirements and Designs Assess Requirements and Designs Changes Approve Requirements and Designs Analyze Current State Define Future State Assess Risks Define Change Strategy Specify and Model Requirements and Designs Verify Requirements and Designs Validate Requirements and Designs Define Requirements Architecture Define Design Options Analyze Potential Value and Recommend Solution Measure Solution Performance Analyze Performance Measures Assess Solution Limitations Assess Enterprise Limitations Recommend Actions to Increase Solution Value
10. Techniques
Introduction 10.1 Acceptance and Evaluation Criteria 10.2 Backlog Management 10.3 Balanced Scorecard 10.4 Benchmarking and Market Analysis 10.5 Brainstorming 10.6 Business Capability Analysis 10.7 Business Cases 10.8 Business Model Canvas 10.9 Business Rules Analysis 10.10 Collaborative Games 10.11 Concept Modelling 10.12 Data Dictionary 10.13 Data Flow Diagrams 10.14 Data Mining 10.15 Data Modelling 10.16 Decision Analysis 10.17 Decision Modelling 10.18 Document Analysis 10.19 Estimation 10.20 Financial Analysis 10.21 Focus Groups 10.22 Functional Decomposition 10.23 Glossary 10.24 Interface Analysis 10.25 Interviews 10.26 Item Tracking 10.27 Lessons Learned 10.28 Metrics and Key Performance Indicators (KPIs) 10.29 Mind Mapping 10.30 Non-Functional Requirements Analysis 10.31 Observation 10.32 Organizational Modelling 10.33 Prioritization 10.34 Process Analysis 10.35 Process Modelling 10.36 Prototyping 10.37 Reviews 10.38 Risk Analysis and Management 10.39 Roles and Permissions Matrix 10.40 Root Cause Analysis 10.41 Scope Modelling 10.42 Sequence Diagrams 10.43 Stakeholder List, Map, or Personas 10.44 State Modelling 10.45 Survey or Questionnaire 10.46 SWOT Analysis 10.47 Use Cases and Scenarios 10.48 User Stories 10.49 Vendor Assessment 10.50 Workshops

2. Understanding Business Analysis

2.2 A Model for Effective Analysis - BACCM™

The Business Analysis Standard

The six core concepts highlighted in the definition of business analysis - Change, Need, Solution, Value, Stakeholder, and Context - form a powerful model for effective business analysis, the Business Analysis Core Concept Model™.

 

baccm-chart_withlogo_600x600.png

The BACCM™ provides essential guidance for business analysis professionals and leaders. To truly understand and apply the foundations of business analysis, it’s important to explore all six concepts and their relationships. Ignoring any concept or their connections can reduce the model’s effectiveness. Viewing business analysis as a system of interrelated concepts is crucial for success.

 

The six core concepts in the BACCM are:

change.png

  • Organizations implement change to stay competitive, foster innovation, improve efficiency, and ensure long-term success in a dynamic and evolving environment
  • These enhancements are managed and completed through business analysis activities


Need_228x228.jpg

  • Needs can cause changes by motivating stakeholders to act
  • Changes can also cause needs by reducing or increasing the value delivered by existing solutions

solution.png

  • A solution satisfies a need by:
    • Resolving a problem faced by stakeholders, or
    • Enabling stakeholders to take advantage of an opportunity
  • A solution can include a combination of components that deliver the desired value, for example:
    • Technology-based initiatives
    • Manual procedures
    • Process changes
    • Business model update
    • Improving organizational capabilities

Stake_228x2281.jpg

  • Stakeholders (both internal and external) are often defined by their interest, impact, and influence over the change
  • Stakeholders are grouped based on their relationship to the needs, changes, and solutions

value.png

  • Value can be:
    • Realized through potential returns, gains, and improvements, or
    • Preserved by mitigating losses, risks, and costs
  • Value can be tangible or intangible:
    • Tangible value is directly measurable and often has a significant monetary component
    • Intangible value is measured indirectly and often has a significant motivational component (e.g., company’s reputation or employee morale)
  • Value can be assessed in absolute or relative terms (e.g., one solution option is more valuable than another from the perspective of a group of stakeholders)

context - Copy.png

Context is everything within the environment relevant to the change which can include:

  • Attitudes
  • Behaviours
  • Beliefs
  • Competitors
  • Culture
  • Demographics
  • Geopolitics
  • Goals
  • History
  • Industry
  • Infrastructure
  • Market trends
  • Processes
  • Products
  • Projects
  • Regulations
  • Sales
  • Seasons
  • Structure
  • Technology
  • Weather

 

The Business Analysis Core Concept Model™ (BACCM™)

The Business Analysis Core Concept Model™ (BACCM™) is composed of six core concepts that provide a common language and guidance for effective business analysis.