You are on page 1of 1


BA Plans Stakeholder List

Identified Needs Conduct Stakeholder Plan, Monitor & Report Plan Requirements Plan, Report & Monitor Stakeholder Roles/Responsibilities
Stakeholders List Plan BA Approach Plan BA Activities BA Communication Plan

Organisational Standards Analysis on Performance Management BA Communication Requirements Management Plan
Actual Performance Metrics Identify/document team roles Define/create requirements process BA PErformance Evaluation
Domain where the BA work occurs Identify BA deliverables Define metrics Identify communication needs
Requirements Management Plan Identify stakeholders Plan requirements traceability Process Improvements
Formality/Granularity of analysis Define scope of work for BA Collect metrics Assess communication formats
Organisational Performance Standards Classify 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 power Determine requirements attributes Lessons Learned
Change control 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 communication formality
Business Analyst SelectIon of BA approach Create stakeholder matrix Plan a process for handling changes Plan a process for handling changes
Expert Judgement
Domain Subject Matter Expert Stakeholder Analysis
End User
Customer Analysis Planning & Performance 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


Enterprise Architecture Validated Stated Requirements Variance Analysis
Business Analysis Plans Supporting Materials/Documentation 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

Technical Team
Explore available documentation
Schedule all analysis activities Confirm results of interviews
Business Case
Operational Support
Project Manager
Quality Assurance Solution Scope

Notify appropriate parties Confirm results of observations Regulator
BA Plan
Quality Assurance
Stakeholder Analysis
Business Need/Problem/Opportunity Stated Requirements
Sponsor Solution & Added Value
Brainstorming Conduct Elicitation Document Results
Document Analysis
Focus Group Trace requirements Document stated requirements
Interface Identification Capture requirement metadata Prioritise
Create glossary of domain terms Validate Requirements
Use performance metrics Requirements
Requirements Basis for prioritisation Define desired outcomes Market/Industry Rules
Business Goals Identify assumptions Business Requirements
Business Objectives Requirements Workshop Elicitation Identify challenges (risks) Organisational RFI/RFQ/RFP Standards

Define evaluation criteria

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

Estimating techniques Kano Analysis Verified Requirements RFI, RFQ, RFP
Identify possible solution approaches Validated Requirements Readiness
Feasibility Studies/Analysis Timeboxing/Budgeting (constraints) Determine Transition Root Cause Analysis
Gap Analysis
Conduct option analysis
Determine/justify solution approach
Enterprise Voting Assumptions Dependencies
Stakeholder Impact Analysis
Interface Identification Constraints Sequencing Survey
Integration Analysis
Prepare options analysis report
Analysis External considerations Data migration
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

Recommended Solution Approach Allocated Requirements Solution Assessment & Validation

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

Approved Changes to Requirements
Implementation Subject Matter Expert Approved Changes to Solution/Scope
Requirements Manage Solution Scope & Manage Requirements Maintain Requirements Communicate Requirements
Security Personnel Reusable Requirements
Solution components Prepare Requirements Package Governing Agencies/bodies Requirements PackageS
IN Inputs Communication format/style Requirements Traceability for Re-Use Technical Team Solution Releases

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

You might also like