®

BABOK FRAMEWORK OVERVIEW

BA Plans Stakeholder list
Identified Needs Conduct Stakeholder Plan, Monitor & Report Plan Requirements Plan, Report & Monitor Stakeholder roles/responsibility
Plan BA Approach Plan BA Activities BA communication plan
Stakeholders List
Analysis on Performance Management BA Communication
IN

OUT
Organisational Standards Requirements management plan
Actual Performance Metrics Identify/document team roles Define/create requirements process BA performance assessment
Where the BA work occurs Identify BA deliverables Define metrics Identify communication needs
Requirements Management Plan Assist in identifying stakeholders Plan requirements traceability Process improvement
Formality/level of details of BA Define scope of work for BA Collect metrics Assess communication formats
Organisational Performance Standards Categorise stakeholders Structure requirements traceability Recommendations
Requirements prioritisation Define tasks for BA in KAs Report on BA work progress Determine appropriate content
Stakeholder Roles/Responsibility Analyze stakeholder influence Determine requirements attributes Lessons learned
How change is handled Develop estimates for BA work Take preventive/corrective actions Determine frequency
Define authority levels for BA work Plan requirements prioritisation BA Plan
Communication with stakeholders Plan requirements prioritisation Assess the formality
Business Analyst SelectIon of BA approach Select BA approach Plan a process for handling changes Plan a process for handling changes
Expert judgement
Domain Subject Matter Expert Stakeholder analysis
End User
Customer BA Planning & Monitoring Data collection methods
Estimating techniques
Implementation Subject Matter Expert Communications Requirements Analysis
Operational Support Performance measurement
Project Manager Configuration management
Regulator Traceability System
Quality Assurance Documentation Based on Technique Time & Cost Reporting
Business Goals
Sponsor Stated Requirements Process analysis
Business Objectives

IN

OUT
Enterprise Architecture Validated Stated Requirements Variance Analysis
Business Analysis Plans Supporting Materials Re-planning
Assumptions, Constraints, Risks, Issues Change Control System
Business Analyst
Elicitation Analysis Results Lessons Learned
Business Analyst
Prepare for Elicitation Domain Subject Matter Expert
Implementation Subject Matter Expert
Domain Subject Matter Expert
Business Users
Clarify scope for techniques used Confirm Results Customer/User
Gather supporting materials Business Case
Operational Support
Technical Team Schedule all resources Confirm results of interviews Project Manager
Quality Assurance Solution Scope
Notify appropriate parties Confirm results of observations Regulator

IN
BA Plan
Quality Assurance
Business Need/ Problem/ Opportunity Stakeholder Analysis
Sponsor Solution & Added Value
Brainstorming Conduct Elicitation Document Results Stated Requirements
Document Analysis
Focus Group Trace requirements Document stated requirements
Capture requirement attributes Prioritise
Interface Identification
Use glossary of domain terms Validate Requirements
Interview Requirements
Observation
Prototyping
Use performance metrics
Requirements Basis for prioritisation Define desired outcomes
Business Goals Identify assumptions Business Requirements
Business Objectives Requirements Workshop Elicitation Identify challenges (risks)
Define evaluation criteria Organisational RFI/RFQ/RFP Standards
IN

Enterprise Architecture Reverse Engineering Deployed Solution Performance Metrics

Define dependencies for benefit
Survey/Questionnaire
Business Analysis Plans Organise realisation Prioritised Approved Business Requirements

IN
Report on BA work progress QA Plans
Requirements Confirm alignment with Business Case Solution (Constructed/Deployed)
Business Analyst
Domain Subject Matter Expert
Domain Subject Matter Expert Solution Design
Follow organisational standards Technical Subject Matter Expert
Business Users (line management) Solution Options
Business Process Owners Define Business Need Define level of granularity Operational Support
Business Unit Managers
Develop Business Case Use simple, consistent definitions Verify Requirements Validated Requirements
Project Manager
Confirm strategic intent Document relationships Quality Assurance
IT Managers
Define problem/opportunity Business Rules Document dependencies Determine requirements quality Regulator
End Users Identify & qualify Benefits
Customers/Suppliers Identify & quantify Costs
Data Analysis Specify verification activity Assess Proposed Validate Solution Sponsor
Hierarchical Decomposition Specify & Model Performance
Security Personnel
Determine Gap in Conduct initial risk assessment Networks Solution
Stakeholders with Governing Authority Set metrics for Costs & Benefits Requirements Determine Assumptions
Project & Operational Teams Capabilities Compile results
Event and State Modeling Solution selection Assess benefits delivered Business Rules
Government/Regulatory Bodies Present results to Project Sponsor
Metrics and Reporting Specify using natural language & Constraints Solution recommendations Assess solution metrics Cost/Benefit Analysis
Sponsor Conduct internal Gap analysis Acceptance Criteria Models Assess solution providers Solution replacement or elimination Coverage Matrix
Non-Functional Requirements Modelling formats Business constraints Data Model
Conduct external Gap analysis
Develop target state of EA Define Solution Scope Organisational Modeling Improvement opportunities Technical constraints Allocate Defect and Issue Reporting
Brainstorming Conduct Gap analysis Process Modeling Capture requirement metadata Assumptions
Requirements Validate Solution Focus Group
Competitive Analysis Matrix Documentation Force Field Analysis
Draft the Solution scope statement
Stakeholders
Benchmark Studies
Decisions Analysis Determine Solution Identify deliverables
Describe Project approach
Decision Tables/Trees
Checklists Requirements Analysis Solution components
Define user acceptance criteria
Investigate defective solution outputs
Observation
Organisational Model
Decomposition Approach Define assumptions Structured Walkthrough Solution releases Assess business impact of defects Prioritization Techniques
Process Model
Document analysis Define constraints & dependencies Scenarios and Use Cases Recommend measures to mitigate impact
Prioritised Requirements
Enterprise Architecture Development
Validate drivers for Feasibility Analysis
MoSCoW Analysis (Must, Should, Could, Won’t)
Verified Requirements
Assess Org. Retrospective
RFI, RFQ, RFP

OUT
Estimating techniques Kano Analysis
Feasibility Studies/Analysis
Identify possible solution approaches
Timeboxing/Budgeting (constraints) Validated Requirements Readiness Determine Transition Root Cause Analysis
Gap Analysis
Conduct Feasibility option analysis
Determine Solution approach
Enterprise Voting Assumptions Dependencies
Requirements
Stakeholder Impact Analysis
Interface Identification Constraints Sequencing Survey
Integration Analysis
Prepare Feasibility study report
Analysis External considerations Data migration
Traceability
Interviewing Key user training UAT
Organisational change
Opportunity Analysis (potential benefits) End user training Structured Walkthrough
Transition support
Problem Analysis (causes of problems) Solution support
Business Need Retirement of legacy components
Scope Models (envision of deployment)
SWOT Analysis Gaps in Capabilities vs Business Need Assessment of proposed solution
OUT

Recommended Solution Approach Allocated Requirements Solution Assessment & Validation

OUT
Solution Scope Transition Requirements
Business Case Solution Performance Assessment
Identified Defects
Organisational Readiness Assessment Business Analyst
Mitigating Actions Domain Subject Matter Expert Approved Requirements
Business Users Decisions Made
Customers/Suppliers

OUT
Modified Requirements
Implementation Subject Matter Expert Approved change to Solution/Scope
Requirements Manage Solution Scope & Manage Requirements Maintain Requirements Communicate Requirements
Security Personnel List of actions for a BA
Solution components Prepare Requirements Package Governing Agencies/bodies
Communication format/style Requirements Traceability for Re-Use Technical Team
Maintained-Reusable Requirements
IN Inputs Communicate requirements Requirements Presentation/Package
IN

Test Cases/Procedures Define requirements management system Identify formatting options for communicating requirements Quality Assurance
Define traceability structure Select requirements to be re-used Communicate solution scope Communicated Requirements
OUT Outputs Implemented Requirements
Stakeholder List
(store, track, update, sign-off)
Determine approval workflow & procedure
Create traceability matrix Define the responsible party Identify communication format options
Communicate Business Case
Sponsor Incomplete Requirements
Maintain traceability Facilitate ongoing use of requirements Determine appropriate content Traced Requirements
Stakeholder Analysis Resolve conflicts & issues Communicate with technical partners
Facilitate re-use of requirements on Determine frequency of communication Manage Requirements Conflicts
Communicate issues and risks
Stakeholders Stakeholder Roles/Responsibilities
Requirements Management Plan
Communicate BA issues to PM
Baseline approved requirements
similar projects Determine level of formality in communication
Communicate with Quality Assurance Requirements Presentation
Select communication style per stakeholder group Requirements Review
BA Communication Plan Control changes of requirements Communicate with business users
Techniques Formal Requirements Approval/Sign-off
Baselining
Requirements Management & Communication Traceability System
Configuration Management/Repository
RFI, RFQ, RFP