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

4. Performing Business Analysis

4.2 Approaches to Your Work

The Business Analysis Standard

Business analysis professionals can perform their work in different enterprises, organizations, and environments. Each may require different policies and procedures, methodologies, and standards.

In addition to intentionally developing a mindset that empowers their approach to work, business analysis professionals begin most initiatives with the intentional selection of the approach that best applies to the outcome that needs to be produced.

There are three approaches to enable change in an enterprise:

  • Predictive
  • Adaptive
  • Hybrid

Each approach can be valuable depending on the context for the change. It is important to understand how to create value with any of these approaches.

Waterfall.jpg

Step-by-step

4.2.1 Predictive Approach

Predictive approaches start with a plan. They are considered predictive because they try to identify all the information needed to create the desired value.

  • Plan all the work up front and then work your plan
  • Consider everything that needs to be done
  • Create documents and models to describe what will be built, including:
    • Scope statement
    • Requirements documents
    • Design documents
    • Schedule baseline
    • Cost baseline
    • Test plans
  • Track progress against the plan

 

Agile.jpg

Learn and adapt

4.2.2 Adaptive Approach

Adaptive or iterative approaches focus on delivering value in small, prioritized increments.

  • Prioritize high-value outcomes or deliverables
  • Plan for the upcoming iterations first
  • Create the outcome defined for each increment (just enough and just-in-time documentation)
  • Focus on:
    • Value creation
    • Workable solutions
    • Speed of delivery
    • The time it takes to create the desired value
  • Share what is created with stakeholders to elicit feedback

Refer to the BABOK Guide: Perspectives — Agile Perspective — Approaches for information on various Agile approaches.

Hybrid.jpg

Use what works best

4.2.3 Hybrid Approach

Hybrid approaches describe work in an organization where:

  • Some initiatives use a predictive approach and others use an adaptive approach
  • Parts of an initiative use a predictive approach and parts of the same initiative use an adaptive approach


In some cases, an approach will be imposed on the team. Whenever the business analysis professionals can choose the approach, they should consider:

  • Using a predictive approach where the work is:
    • Well-defined
    • Heavily regulated
    • Relatively straightforward, or
    • Can be completed sequentially
  • Using an adaptive approach when a solution is being built to:
    • Address business needs that are complex
    • Find solutions for poorly defined challenges
    • Deal with uncertainty, or
    • Manage emerging needs as the solution is being built
  • Learning how to create value using any of the approaches
Refer to “How do I…Identify What Needs to Be Done.” This provides additional information about both predictive and adaptive approaches, including case study examples.