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

11. Perspectives

BABOK® Guide

Introduction

Perspectives are used within business analysis work to provide focus to tasks and techniques specific to the context of the initiative. Most initiatives are likely to engage one or more perspectives. The perspectives included in the BABOK® Guide are:

  • Agile,
  • Business Intelligence,
  • Information Technology,
  • Business Architecture, and
  • Business Process Management.

These perspectives do not presume to represent all the possible perspectives from which business analysis is practiced. The perspectives discussed in the BABOK® Guide represent some of the most common views of business analysis at the time of writing.

Any given initiative includes one, many, or all of these perspectives. For example, an initiative may have a technology component (Information Technology Perspective), the technology component may mean business process changes (Business Process Management Perspective), the initiative may decide to do part, or all of the work with an agile approach (Agile Perspective). Another initiative may merge two organizations and need to look at the business capabilities and how the transformation impacts those capabilities (Business Architecture Perspective), and the business leaders need updated information for decision making and analysis (Business Intelligence Perspective). Large or complex initiatives will likely employ all perspectives.

For more information regarding this structure, see Perspectives (p. 9).

While the business analysis tasks detailed in the BABOK® Guide are intended to be applicable across all areas of business analysis, they are also pertinent to each specific business analysis perspective. Perspectives provide ways to approach business analysis work in a more focused manner suitable to the context. The perspectives help interpret and understand the knowledge areas and tasks in the BABOK® Guide from the lens in which one is currently working.

Each perspective follows a common structure:

  • Change Scope,
  • Business Analysis Scope,
  • Methodologies, Approaches, and Techniques,
  • Underlying Competencies, and
  • Impact on Knowledge Areas.