1 PMI-PBA ITTOs

Business Analysis Process Groups

Knowledge Areas Defining and Initiating Monitoring and

Executing Process Releasing Process
Aligning Process Process Planning Process Group Controlling Process
Group Group
Group Group Group
4.1 Identify Problem or Opportunity 4.7 Support
4.2 Assess Current State Charter
4. Needs 4.3 Determine Future State Development
4.4 Determine Viable Options and Provide
Assessment Recommendation
4.5 Facilitate Product Roadmap
4.6 Development Assemble Business Case
5.1 Identify Stakeholders 5.2 Conduct Stakeholder Analysis 5.5 Prepare for Transition 5.6 Manage Stakeholder
5. Stakeholder 5.3 Determine Stakeholder to Future State Engagement and
Engagement and Communication Communication
Engagement Approach 5.7 Assess Business Analysis
5.4 Conduct Business Analysis Performance
Planning
6.1 Determine Elicitation 6.2 Prepare for Elicitation
6. Elicitation Approach 6.3 Conduct Elicitation
6.4 Confirm Elicitation
Results
7.1 Determine Analysis 7.2 Create and Analyze
Approach Models
7.3 Define and Elaborate
Requirements
7.4 Define Acceptance
Criteria
7. Analysis 7.5 Verify Requirements
7.6 Validate Requirements
7.7 Prioritize Requirements
and Other Product
Information
7.8 Identify and Analyze
Product Risks
7.9 Assess Product
Design Options
8. Traceability and 8.1 Determine Traceability and 8.2 Establish Relationships 8.4 Manage Changes to
Monitoring Approach and Dependencies Requirements and Other
8.3 Select and Approve Product Information
Monitoring Requirements

9. Solution 9.1 Evaluate Solution 9.2 Determine Solution 9.3 Evaluate 9.4 Obtain Solution
Performance Evaluation Approach Acceptance Results and Acceptance for Release
Evaluation Address Defects
2 PMI-PBA ITTOs

Business Analysis Book mapping

Knowledge Areas
BUSINESS ANALYSIS FOR PRACTITIONERS The PMI Guide to BUSINESS ANALYSIS

2.3 Identify Problem or Opportunity 4.1 Identify Problem or Opportunity, 5.1 Identify Stakeholders
2. Needs 2.4 Assess Current State of the Organization 4.2 Assess Current State, 4.3 Determine Future State
2.5 Recommend Action to Address Business Needs 4.4 Determine Viable Options and Provide Recommendation
Assessment 4.6 Development Assemble Business Case
2.6 Assemble the Business Case
3.3 Conduct or Refine the Stakeholder Analysis 5.2 Conduct Stakeholder Analysis,
3. Business 3.4 Create the Business Analysis Plan 5.3 Determine Stakeholder Engagement and Communication Approach, 8.1 Determine Traceability and
Analysis Planning 3.5 Plan the Business Analysis Work Monitoring Approach
5.4 Conduct Business Analysis Planning
4.3 Plan for Elicitation 6.1 Determine Elicitation Approach
4.4 Prepare for Elicitation 6.2 Prepare for Elicitation
4.5 Conduct Elicitation Activities 6.3 Conduct Elicitation
6.4 Confirm Elicitation Results
4.6 Document Outputs from Elicitation Activities
4.7 Complete Elicitation
4. Requirements
4.8 Elicitation Issues and Challenges
Elicitation and 4.9 Analyze Requirements 7.1 Determine Analysis Approach,
4.10 Model and Refine Requirements 7.2 Create and Analyze Models,
analysis
4.11 Document the Solution Requirements 7.3 Define and Elaborate Requirements, 7.7 Prioritize Requirements and Other Product Information
4.12 Validate Requirements 7.6 Validate Requirements, 6.4 Confirm Elicitation Results
4.13 Verify Requirements 7.5 Verify Requirements
4.14 Approval Sessions 8.3 Select and Approve Requirements
4.15 Resolve Requirements-Related Conflicts
5.3 Relationships and Dependencies 8.2 Establish Relationships and Dependencies
5.4 Approving Requirements 8.3 Select and Approve Requirements
5. Traceability and 5.5 Baselining Approved Requirements
Monitoring 5.6 Monitoring Requirements Using a Traceability Matrix
5.7 The Requirements Life Cycle 8.4 Manage Changes to Requirements and Other Product Information
5.8 Managing Changes to Requirements
6.4 Plan for Evaluation of the Solution 9.2 Determine Solution Evaluation Approach
6.5 Determine What to Evaluate
6.6 When and How to Validate Solution Results
9.3 Evaluate Acceptance Results and Address Defects
6. Solution 6.7 Evaluate Acceptance Criteria and Address Defects
6.8 Facilitate the Go/No-Go Decision
Evaluation 6.9 Obtain Signoff of the Solution 9.4 Obtain Solution Acceptance for Release
6.10 Evaluate the Long-Term Performance of the
Solution
6.11 Solution Replacement/Phase out
3 PMI-PBA ITTOs

Knowledge
Processes Subset More Tools and Techniques
Areas

Identify Stakeholders

Investigate the Problem or Opportunity

Evaluate the Situation

2.3 Identify Problem or Opportunity

Draft the Situation Statement

Obtain Stakeholder Approval for the Situation Statement

SMART Goals and Objectives

SWOT Analysis
2. Needs
Assessment
Relevant Criteria

Perform Root Cause Analysis

2.4 Assess Current State of the Organization
Determine Required Capabilities

Assess Current Capabilities

Identify Gaps in Organizational Capabilities

4 PMI-PBA ITTOs

Include a High-Level Approach for Adding Capabilities.

Provide Alternative Options

Identify Constraints, Assumptions, and Risks

2.5 Recommend Action to Address Business Needs

Assess Feasibility and Organizational Impacts

Recommend the Most Viable Option

Conduct Cost-Benefit Analysis

Value of the Business Case

2.6 Assemble the Business Case
5 PMI-PBA ITTOs

Knowledge
Processes Subset More Tools and Techniques
Areas
Brainstorming

Organizational Charts

Determine Stakeholder Characteristics

3.3 Conduct or Refine the Stakeholder Analysis

Job Analysis

Persona Analysis

Assemble the Stakeholder Analysis Results

Business Analysis Plan vs. Requirements Management Plan

What to Include

Project Life Cycle

3. Business
Analysis Plan for Elicitation
Planning
Plan for Analysis

Requirements Prioritization Process

3.4 Create the Business Analysis Plan
Traceability Approach

Communication Approach

Decision-Making Process

Requirements Verification and Validation Processes

Requirements Change Process

Solution Evaluation Process

6 PMI-PBA ITTOs

Build the Business Analysis Work Plan

Assemble the Business Analysis Work Plan

3.5 Plan the Business Analysis Work
Document the Rationale for the Business Analysis Approach

Review the Business Analysis Plan with Key Stakeholders

Obtain Approval of the Business Analysis Plan

Knowledge
Processes Subset More Tools and Techniques
Areas

4.3 Plan for Elicitation Finding Information

Techniques for Eliciting Information

Sequencing the Elicitation Activities

4.
Requirements 4.4 Prepare for Elicitation Determine the Objectives
Elicitation and
Determine the Participants
analysis
Identify the resources

Determine the Questions for the Session

Set agenda

Schedule the elicitation

7 PMI-PBA ITTOs

4.5 Conduct Elicitation Activities Introduction

Body

Close

Elicitation Techniques

4.6 Document Outputs from Elicitation Activities Follow-Up

4.7 Complete Elicitation

4.8 Elicitation Issues and Challenges

Plan for Analysis

4.9 Analyze Requirements

Categories of Models

Selection of Models

4.10 Model and Refine Requirements Modeling Languages

Scope Models
■ Goal and business objectives model
8 PMI-PBA ITTOs

■ Ecosystem map

■ Context diagram

■ Feature model

■ Use case diagram

■ Organizational chart
■ Decomposition model
■ Fishbone diagram
■ Interrelationship diagram
■ SWOT diagram
■ Event list

Process Models
■ Process flow

■ Use case

■ User story

Rule Models
■ Business rules catalog

■ Decision tree & Decision table

Data Models
■ Entity relationship diagram

■ Data flow diagram

■ Data dictionary
9 PMI-PBA ITTOs

■ State table & State diagram

Interface Models
■ Report table

■ System interface table

■ User interface flow

■ Wireframes & Display-action-response

The Solution Documentation

Requirements Specification

Guidelines for Writing Requirements

4.11 Document the Solution Requirements

Prioritizing Requirements

Use Cases & User Stories

Requirements Walkthrough
4.12 Validate Requirements
10 PMI-PBA ITTOs

Peer Review

4.13 Verify Requirements

Inspection

4.14 Approval Sessions

Delphi.

4.15 Resolve Requirements-Related Conflicts Multivoting

Weighted Ranking

Knowledge
Processes Subset More Tools and Techniques
Areas

Subsets

Implementation Dependency
5.3 Relationships and Dependencies

Benefit or Value Dependency

5. Traceability
and Monitoring

Work Authorization System

5.4 Approving Requirements

Approval Levels
11 PMI-PBA ITTOs

Relationship of Requirements Baseline, Product Scope,

and Project Scope

5.5 Baselining Approved Requirements Maintaining the Product Backlog

Traceability Matrix
5.6 Monitoring Requirements Using a Traceability
Matrix

5.7 The Requirements Life Cycle

Configuration Management System (CMS)

Version Control System (VCS)

5.8 Managing Changes to Requirements
Impact Analysis

Controlling Changes Related to Defects

Knowledge
Processes Subset More Tools and Techniques
Areas

Consider the Business Goals and Objectives

6. Solution 6.4 Plan for Evaluation of the Solution Consider Key Performance Indicators
Evaluation 6.5 Determine What to Evaluate Consider Additional Evaluation Acceptance Criteria

Confirm that the Organization Can Continue with Evaluation

12 PMI-PBA ITTOs

Surveys and Focus Groups

Results from Exploratory Testing and User Acceptance

Testing

Results from Day-in-the-Life (DITL) Testing

Results from Integration Testing

6.6 When and How to Validate Solution Results

Expected vs. Actual Results for Functionality

Expected vs. Actual Results for Nonfunctional Requirements

Outcome Measurements and Financial Calculation of Benefits

Comparison of Expected vs. Actual Results

6.7 Evaluate Acceptance Criteria and Address Examine Tolerance Ranges and Exact Numbers
Defects
Log and Address Defects
6.8 Facilitate the Go/No-Go Decision

6.9 Obtain Signoff of the Solution

Determine Metrics

Obtain Metrics/Measure Performance

Analyze Results
6.10 Evaluate the Long-Term Performance of the
Solution

Assess Limitations of the Solution and Organization

Recommend Approach to Improve Solution Performance

13 PMI-PBA ITTOs

6.11 Solution Replacement/Phase out