There are many techniques that Business Analyst’s employ to do their job. With different techniques being available for different purposes in different situations.  The goal of this section of the wiki is to eventually provide:

  • A fairly comprehensive list of techniques of use to Business Analysts
  • A brief description for each of those techniques (the more info the better, but starting small)
  • Tips for when, how, and why to use each technique
  • Links to other resources on the web (blog posts, articles, papers, etc) where you can find out more about the technique

The amount of content for different entries may vary significantly, depending on whether users add to the wiki entry for that technique, and whether it is a commonly used technique.


What do I mean by “Technique”?

For purposes of this wiki, I am defining a “Technique” as a specific action or set of actions that is used by a Business Analyst to help deal with issues of scope, elicitation, documentation, analysis, and verification.

I want to try and separate Techniques from Skills which I see as more general capabilities or knowledge sets of the Business Analyst.  As an example, I would say that facilitation is a Skill, while Brainstorming or running Joint Application Development (JAD) sessions are specific Techniques that supplement the Skill.  Because Skills are more generic to BA’s in general, I have them in the Career section of the wiki.


Technique Categories and List

Each technique has it’s own page, but I have attempted to group them below by usage. Any technique that is not a link below is a placeholder for a future page.

General Analysis Techniques

Class Modelling
Mind Mapping

Data Analysis Techniques

Data Dictionary
Data Flow Diagrams

Decision and Rules Techniques

Business Rule Analysis
Decision Models
Decision Tables
Decision Trees

Elicitation Techniques

Concept Map
Document Analysis
Feature Tree
Focus Groups
Interface Analysis
JAD Sessions
Problem Statements
Requirements Workshops
Surveys and Questionnaires
Use Cases
Use Case Diagrams
User Stories

Enterprise Analysis Techniques

Concept Map
Context Diagrams
Feasibility Analysis
Force Field Analysis
Futures Wheel
Organizational Modeling
PEST Analysis
SWOT Analysis
Value Stream Mapping
VMOST Analysis

Features and Functional Analysis Techniques

Decomposition – Functional and Otherwise
Feature Tree

Prioritization Techniques

Category Assignment Prioritization
Cumulative Voting Prioritization
Hierarchical Cumulative Voting Prioritization
Hierarchical MoSCoW Prioritization
Kano Model Prioritization
Matrix Prioritization
MoSCoW Prioritization

Problem Solving and Ideation Techniques

Affinity Diagram

Process Analysis Techniques

Activity Diagram
Business Process Modeling
Sequence Diagram

Project Analysis and Scoping Techniques

Context Diagrams
Feature Tree
In/Out List
Investment Logic Mapping
Problem Statements
Scope Analysis
Use Case Diagrams

Root Cause Analysis

Fishbone Diagram
Five Why’s

Stakeholder Management Techniques

Responsibility Matrices: RACI, RASCI, and More
Stakeholder Communications Matrix
Stakeholder Maps
Stakeholder Onion Diagram
Stakeholder Radar Diagram
Stakeholder Role Matrix
Stakeholder Salience Diagram

2 thoughts on “Techniques

  1. Kari Longman

    Hi there

    This looks like an absolutely great reference site for business analysts, and am likely to refer to it often now I’ve found it. But please, oh please, remove the typo from your heading, as it kind of spoils the impact? It should be “A Reference and Blog for Business Analysts” without the apostrophe in Analysts.


    Kari (Senior Business Analyst Consultant, Saratoga Professional Services)

    1. Dave Post author

      Thanks. I will admit that there are probably quite a few grammar and punctuation errors on the site. I try to find them but there always seems to be more. And for those who need a good reminder on when to use apostrophes, the Oatmeal has some tips.


Leave a Reply

Your email address will not be published. Required fields are marked *