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

7. Techniques

Agile Extension to the BABOK® Guide

The Techniques chapter provides a high-level overview of some techniques commonly used by agile business analysis practitioners.

The techniques described in the Agile Extension to the BABOK® Guide are intended to cover the most common and widespread techniques practiced within agile business analysis. Business analysis practitioners apply their experience and judgment in determining which techniques are appropriate to a given context and how to apply each technique. This may include techniques that are not described in the Agile Extension to the BABOK® Guide. As the practice of agile business analysis evolves, techniques will be added, changed, or removed from future iterations of the Agile Extension to the BABOK® Guide.

It can be challenging to select the right technique for the situation to get the desired outcome. The following chart provides general guidance on when to choose a specific technique. Please note that many techniques can be used successfully in a variety of contexts. An agile business analysis practitioner uses his or her domain knowledge, experience, individual competencies, and creativity when selecting the appropriate technique for the desired outcome. The purpose of this chart is to provide a starting point when determining which technique might be useful in a given context.

A team is a group of people working together for a shared goal – this team could be at the Strategy, Initiative, or Delivery Horizon. Stakeholders outside the team are customers, subject matter experts, or people internal or external to the organization who are invested in the team's success but are not part of the team.

The context identifies when each technique is most useful to get the desired outcome.

  • Communication identifies what techniques facilitate shared understanding, collaboration, and increased communication.

  • Process Analysis is about understanding the process to identify ways to improve.

  • Product Management or Refinement is about what solution the team is delivering.

  • Requirements Management includes techniques specifically helpful in facilitating and improving the requirements life cycle.

  • Understanding Your Customer is about identifying, understanding, and clarifying who the customer is and what they need and value.
Table 7.0.1: Selecting the Right Technique

Some Techniques Commonly Used by Agile Business Analysis Practitioners

7.1 - 7.6

7.7 - 7.12

7.13 - 7.18

7.19 - 7.24