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

1. Introduction

1.1 Purpose of the Agile Extension to the BABOK® Guide

Agile Extension to the BABOK® Guide

IIBA.org KnowledgeHub Agile Extension 1. Introduction 1.1 Purpose of the Agile Extension to the BABOK® Guide

Agile methods and approaches have become prevalent in recent years. The ideas which were identified in the realm of software product development have spread beyond software development into many other areas that are impacted by business analysis. This means that the practice of business analysis has to evolve to support the new ways of working, not just in software development but in any area of the business where change is happening rapidly. In this context, the term agile refers to a mindset or way of thinking about work. Agile is not a specific set of practices or techniques.

The Agile Extension to the BABOK® Guide (Agile Extension) version 2 is the leading guide for describing the benefits, activities, tasks, skills, and practices required for effective business analysis with an agile mindset which has a constant focus on delivering business value. It also describes how techniques and concepts commonly used in agile approaches can be applied to business analysis practices. The Agile Extension version 2 provides practitioners, teams, and organizations a base of knowledge to enable effective agile business analysis in order to generate successful business outcomes that add real business and customer value.

 

Since version 1 of the Agile Extension was released, the state of practice has advanced. Version 2 of the Agile Extension taps into the latest thinking and presents ideas and techniques representing good agile business analysis practices.

The primary purpose of the Agile Extension version 2 is to describe the link between business analysis practices applied with an agile mindset, defined here as agile business analysis, and A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide ) version 3. BABOK® Guide version 3 reflects the evolution of the business analysis discipline and its most common practices, and this Agile Extension version 2 demonstrates the evolution of agile business analysis practices and common techniques.

The Agile Extension introduces a multi-level, rolling planning model to help practitioners, teams, and organizations manage business analysis work, so they can quickly leverage learning and discover what provides the most actual value. This rolling wave planning model is presented using three horizons which provide context and scope for lower levels. The three horizons are: the Strategy Horizon, the Initiative Horizon, and the Delivery Horizon.

There are a wide variety of techniques, processes, and tools that can be applied to agile business analysis. There is no single approach that should be applied to every context, and part of the skill of the agile business analysis practitioner is to select the most effective techniques for the specific context; the Agile Extension does provide some advice for practitioners on the applicability of different techniques to different contexts.

Contributors

IIBA® and The Agile Alliance® would like to thank the following contributors to the Agile Extension to the BABOK® Guide. Without their efforts and commitment, the Agile Extension to the BABOK® Guide version 2.0 would not be possible.

  • James King
  • Jas Phul, Product Owner, IIBA
  • Kent J. McDonald
  • Paul Stapleton, Editor, IIBA
  • Ryland Leyton
  • Shane Hastie, Team Facilitator, The Agile Alliance
  • Stephanie Vineyard
  • Steve Adolph
The following industry experts generously provided IIBA® and The Agile Alliance® with advice and guidance on the scope and content of version 2.0 of the Agile Extension to the BABOK® Guide during its planning and development, and helped to shape the content and direction of this release.

  • Ellan Young
  • Linda Cook
  • Angela Wick
  • Mary Gorman
  • Chirs Matts
  • Ali Mazer
  • Luiz Claudio Parzianello
  • Zoya Royblat
  • Tim Coventry
  • Mindy Bohannon
  • Ellen Gottesdiener
  • Ali Mazer
  • Brian Hemker
  • Carol Scalice
  • Chris Matts
  • David C. Cook
  • David Morris
  • Dennis Stevens
  • Ellen Gottesdiener
  • Kevin Brennan
  • Luiz Claudio Parzianello
  • Marsha Hughes
  • Pascal Van Cauwenberghe
  • Paul Stapleton, Editor
  • Peter Gordon
  • Shane Hastie
  • Steve Erlank
  • Susan Block
  • Irena Duniskvaric: Technical illustrations
  • Lynda Sydney, Ignite Writing Services: Copy editing
  • Vic Bhai, Technical Writer/Editor, IIBA: Layout and design
The Agile Extension to the BABOK® Guide (Agile Extension) has be entirely re- thought and re-architected for version 2. There is no direct mapping of changes for Agile Extension version 1 to Agile Extension version 2. This appendix provides details into the rational for the changes and results of these changes.

The Agile Extension to the BABOK® Guide (Agile Extension) version 2 describes the benefits, activities, tasks, skills, and practices required for effective agile business analysis with a constant focus on delivering business value.

The Agile Extension version 2:

  • positions agile business analysis beyond software development. The thinking and practices found in Agile Extension version 2 can be applied in any domain operating in an agile context.

  • places a increased focus on agile business analysis practices and thinking as a means to helping business analysis practitioners and organizations realize the value delivered by effective agile business analysis.
  • embraces and incorporates the

  • Business Analysis Core Concept Model™ (BACCM™).

  • builds on values established in the Manifesto for Agile Software Development by describing and ingraining the seven principles for agile business analysis.

  • introduces the concept of rolling planning horizons that, from an agile perspective, represent a view of work within an organization with a level of granularity appropriate to the planning time frame and the nature of the feedback loops.
  • places increased emphasis on the importance of feedback and learning to the continuous delivery of value.
  • rethinks, updates, adds, and removes techniques that support agile business analysis practices. Some techniques found in


Agile Extension version 1 have be included in BABOK® Guide. Unless there is a significant difference to the technique in an agile context, these techniques are not included in the Agile Extension version 2..

Agile Extension version 1 Technique

Agile Extension version 2 Technique

Change

Backlog Management

 

Moved to BABOK® Guide

 

Backlog Refinement

New

Behaviour Driven Development

Behaviour Driven Development

Updated

Business Capability Analysis

 

Moved to BABOK® Guide

Business Value Definition

 

Removed

Collaborative Games

 

Moved to BABOK® Guide

 

Impact Mapping

New

 

Job Stories

New

Kano Analysis

Kano Analysis

Updated

Lightweight Documentation

 

Removed

MoSCoW Prioritization

 

Removed

 

Minimal Viable Product

New

Personas

Personas

Updated

Planning Workshop

Planning Workshop

Updated

 

Portfolio Kanban

New

 

Product Roadmap

New

Purpose Alignment Model

Purpose Alignment Model

Updated

Real Options

Real Options

Updated

Relative Estimation

Relative Estimation

Updated

Retrospectives

Retrospectives

Updated

 

Reviews

New

 

Spikes

New

Storyboarding

Storyboarding

Updated

Story Decomposition

Story Decomposition

Updated

Story Elaboration

Story Elaboration

Updated

Story Mapping

Story Mapping

Updated

User Story

User Stories

Updated

Value Stream Mapping

Value Stream Mapping

Updated

 

Visioning

New