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.4 Tasks

2.4.6 Select Techniques for Interpret and Reporting Results

Guide to Business Data Analytics

The following is a selection of some commonly used analysis and analytics techniques applicable to the Interpret and Report Results domain. The following list of techniques does not represent a comprehensive set of techniques used by an analyst in the Interpreting and Reporting Results domain but presents a small, but useful, set of techniques that can be used.

Techniques Usage Context for Business Data Analytics BABOK® Guide v3.0 Reference
Interviews Used to understand specific needs and expectations from stakeholders with respect to visualizations and communication. Chapter 10.25
Prototyping Used to systematically walk-through the analytics process to highlight certain conclusions. Prototyping is especially useful in predictive and prescriptive analytics settings. Chapter 10.36
Root Cause Analysis Used to organize various insights in such a way that explains a particular business phenomenon. Chapter 10.40
Stakeholder List, Map, or Personas Used to understand stakeholder needs and determine the visualization and communication requirements. Chapter 10.43
Workshops Used to distill multiple insights generated throughout the analytics life cycle to a set of business-relevant insights. Chapter 10.50
Storyboarding Used to communicate complex visualization or analytics approaches to stakeholders. Chapter 11.1 The Agile Perspective
3-minute Story Used to communicate insights to stakeholders in the form of a short business narrative. N/A
Business Visualizations Used to derive and communicate insights in simple and easy to understand charts, graphs, infographics, audio- visuals, and so forth. Business visualizations are meant to be simple representations for the consumption of stakeholders. N/A
Data Journeys and Orchestration Used to connect the entire data analysis journey and various decision points and analytics steps involved in the discovery process in the form of a visual hierarchy. N/A
The Big Idea Used to communicate the most relevant findings in a succinct manner.
For example, if a visualization shows an S-Curve between marketing expense and the revenue generated by a cohort of customers, the big idea answers the “so -what” question, that is “beyond a certain dollar value marketing expense does not have any impact on revenue.”
N/A
UX Patterns or Frameworks for Data Visualization Used to design the visuals and stories using a distinct UX framework or best practices used in the enterprise. N/A