Skip to content
Browse
BABOK Guide
BABOK Guide
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. The Agile Mindset

2.5 The Business Analysis Core Concept Model ™

Agile Extension to the BABOK® Guide

IIBA.org KnowledgeHub Agile Extension 2. The Agile Mindset 2.5 The Business Analysis Core Concept Model ™

The Business Analysis Core Concept Model™ (BACCM™) provides a conceptual framework for business analysis that is comprised of six terms that have a common meaning to all business analysis practitioners. Refer to A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide ) version 3 for more information regarding the Business Analysis Core Concept Model™.

Figure 2.5.1: The BACCM

image.png

 

The six concepts of the model are:

  • Change: The act of transformation in response to a need.
  • Need: A problem or opportunity to be addressed.
  • Solution: A specific way of satisfying one or more needs in a context.
  • Stakeholder: A group or individual with a relationship to the change, the need, or the solution.
  • Value: The worth, importance, or usefulness of something to a stakeholder within a context.
  • Context: The circumstances that influence, are influenced by, and provide understanding of the change.

These concepts are common to all business analysis practitioners, and they can apply to any domain and any level in the organization. They provide a universal language to describe how to approach business analysis with an agile mindset.