2.

BUSINESS ANALYSIS PLANNING & MONITORING

Task Elements Important topics Techniques Outputs
2.1. Plan 1. Timing BA Work Plan Driven Approach 9.8. Decision Analysis 2.1. BA APPROACH
Business 2. Formality & Level of Detail Deliverables Change Driven Approach 9.21. Process Modeling
Analysis 3. Requirements Prioritization 9.30. Structured Walkthrough • Team Roles
Approach 4. Change Management • Deliverables
5. BA Planning Process • Analysis Techniques
6. Communication with Stakeholder • Timing & Frecuency stakeholders interactions
7. Reqs Analysis & Mgmt Tools
8. Project Complexity
2.2. Conduct 1. Identification 1. GENERAL 2.2. STAKEHOLDERS LIST, ROLES &
Stakeholder 9.1. A&E Criteria Definition RESPONSIBILITIES
Analysis 9.3. Brainstorming
9.14. Interviews • List required roles
2. Complexity of Stakeholder Group Number & variety of directs end users
Number of interfacing Business Processes & Automated Systems 9.19. Organization Modeling • Names titles stakeholders
9.21. Process Modeling • Category stakeholders
3. Attitude & Influence Attitude:
9.23. Requirements Workshop • Locations stakeholders
Influence:
9.24. Risk Analysis • Special needs
On Project
9.26. Scenarios & Use Cases, & 9.33. User • Number stakeholders per role
In Organization
Stories • Description Influence & Unterest
Needed for the good of project
9.27. Scope Modeling • Documentation stakeholder authority levels
With other Stakeholders
9.31. Survey / Questionnaire
4. Authority Level for BA Work
2. RACI Matrix
3. Stakeholder Map
2.3. Plan BA 1. Geographic Distribution of Stakeholders Collocated 9.10. Estimation 2.3. BUSINESS ANALYSIS PLAN
Activities Dispersed 9.12. Functional Decomposition
2. Type of Project or Initiative Type of Project or initiative 9.24. Risk Analysis • Description scope of work
3. BA Deliverables • Deliverables of WBS
4. Determine BA Activities WBS • Activity List
Activity List • Estimates each activity
Unique Number
Activity Description
Assumptions
Dependencies
Milestones
2.4. Plan BA 1. Geography 9.30. Structured Walkthrough 2.4. BUSINESS ANALYSIS COMUNICATION
Communication 2. Culture Relationship to time PLAN
Relationship to task completion
Relationship to contracts • How, when & why BA Works with
Relationship to formal & informal authority stakeholders
3. Project Type • New, customized in-house software development project • Communication Requirements
• Upgrading technology or infrastructure system • Format, Content, Medium, Level of Detail
• Change a business Process or new data for existing app • Responsability for Collection, distributing,
• Purchase software package accessing and updating information
• Short, focused, agile style iterations of software dev
4. Communication Frequency
5. Communication Formality
2.5. Plan 1. Repository 9.8. Decision Analysis 2.5. REQUIREMENTS MANAGEMENT PLAN
Requirement 2. Traceability 9.20. Problem Tracking
Management 3. Select Requirements Attributes CARAS SOUPS: 9.24. Risk Analysis • Approach structure Traceability
Process • Complexity • Reqs attributes to be used
• Absolute Reference • Reqs prioritization Process
• Risk • Reqs change process: how changes will be
• Author requested, analyzed, approved & implemented
• Source
• Status
• Ownership
• Urgency
• Priority
• Stability
4. Requirements Prioritization Process Formality
Establish Process & Technique
Plan The Participation

5. Change Management • Determine process for requesting changes

• Determine who will authorize changes
• Impact Analysis
• Plan Wording of request

• Cost & time estimates of change

6. Tailoring Reqs Mgmt Process
• Benefits & Risk of the change
• Recommended course of actions for change
• Coordinate Prioritization of Change
• Organizational Culture
• Stakeholder Preferences
• Complexity of Project, phase or product-service
• Organizational Maturity
• Availability Resources

2.6. Manage BA 1. Performance Measures 1. GENERAL 2.6. BA PERFORMANCE ASSESSMENT

Performance 9.14. Interview • Comparison planned vs. Actual performance
9.15. Lesson Learned Process • Root Cause of variance plan
9.16. Metrics & Key Perform. Indicators • Level of effort requred to complete
2. Performance Reporting
9.20. Problem Tracking
9.21. Process Modeling 2.6. BA PROCESS ASSETS
9.25. Root Cause Analysis • Recommnedations for improvement
3. Preventive & Corrective Action 9.31. Survey / Questionnaire • May be incorporated in OPA

2. VARIANCE ANALYSIS
 3. ELICITACION
Task Elements Important topics Techniques Outputs
3.1. Prepare for • Clarify specific scope DIP OF RIBS 3.1. SCHEDULED RESOURCES
Elicitation • Schedule all resources (people, facilities, equipment) • Participants
• Notify appropriate parties of the plan • Locations

3.1. SUPPORTING MATERIALS

• Any material required to help
explain techniques
3.2. Conduct • Tracing Requirements 9.5. Data Dictionary & Glossary 3.2. ELICITATION RESULTS
Elicitation • Capturing requirements attributes DIP OF RIBS
Activities • Metrics • Appropiate Docmentation Information from
stakeholder

3.3. Document Written Documents 9.20. Problem Tracking 3.3. REQUIREMENTS [STATED]
Elicitarion Visual, Audio Recordings DIP OF RIBS • Stated: stakeholder perspective
Results Whiteboards
3.3. STAKEHOLDER CONCERNS
• Issues identified by stakeholder,
risk, assumptions, constraints

3.4. Confirm Relevant Techniques 9.14. Interviews 3.4. REQUIREMENTS [STATED, CONFIRMED]
Elicitation 9.18. Observation • Stated: stakeholder perspective
Results • Including as input to other tasks

3.4. STAKEHOLDER CONCERNS

• Issues identified by stakeholder,
risk, assumptions, constraints.
• Including as input to other tasks
 4. REQUIREMENTS MANAGEMENT & COMMUNICATION
Task Elements Important topics Techniques Outputs
4.1. Define 1. Solution Scope Management 1. GENERAL 4.1. REQUIREMENTS [APPROVED]
Solution Scope 2. Conflict & Issue Management 9.20. Problem Tracking
& Requirements 3. Presenting Reqs for Review • Are agreed to by stakeholders & ready for
2. BASELINING use
3. SIGN OFF
4. Approval
4.2. Manage 1. Relationships Reasons to create Relationships: COVERAGE MATRIX 4.2. REQUIREMENTS [TRACED]
Requirements • Impact Analysis
Traceability • Requirements Coverage • Traced Reqs have clearly defined
• Requirements Allocation relationship to other requirements within
solution scope
Types of Relationships:
• Necessity
• Effort
• Subset
• Cover
• Value
2. Impact Analysis
3. Configuration Management System
4.3. Maintain 1. Ongoing Requirements 4.3. REQUIREMENTS [MAINTAINED &
Requirements for 2. Satisfied Requirements REUSABLE]
Re-use
• Reqs for long-term usage by organization

4.4. Prepare • Formal Documentation 1. REQUIREMENTS DOCUMENTATION 4.4. REQUIREMENTS PACKAGE

Requirements • Presentation - Business Requirements Documents
Package • Models - Product Roadmap • Documents
- Software/System Reqs Specification • Presentations
1. Work Products & Deliverables - Supplementary Reqs Specification • May be broken into several sub packages
2. Format - Vision Document • ready to be reviewed by stakeholders

2. REQUIREMENTS FOR VENDORS SELECTION

- RFI
- RFQ
- RFP

4.5. 1. General Communication • Enterprise Analysis Tasks 9.23. Requirements Workshop 4.5. COMMUNICATED REQUIREMENTS
Communicate • Elicitation Tasks 9.30. Structured Walkthrough
Requirements • Requirement Analysis Tasks • Requirements communicated (and their current
• Solution Assessment & Validation Tasks state) to stakeholders

2. Presentations • Formal
• Informal
 5. ENTERPRISE ANALYSIS
Task Elements Important topics Techniques Outputs
5.1. Define 1. Business Goals & Objectives SMART 9.2. Benchmarking 5.1. BUSINESS NEED
Business Need 9.3. Brainstorming
2. Business Problem or Opportunity 9.4. Business Rules Analysis • Problem organization is facing, or
9.11. Focus Groups • Opportunity that is not taken
3. Desired Outcome 9.12. Functional Decomposition • (and desired outcome)
9.25. Root Cause Analysis
5.2. Assess 1. Current Capability Analysis 9.9. Document Analysis 5.2. REQUIRED CAPABILITIES
Capability Gaps 9.32. SWOT Analysis
2. Assessment of New Capability Requirements • Understanding of current Capabilities
• New Capabilites (processes, staff,
features app, etc)
3. Assumptions

5.3. Determine 1. Alternative Generation 1. GENERAL 5.3. SOLUTION APPROACH

Solution 9.2. Benchmarking
Approach 9.3. Brainstorming • Approach that will be taken to implement
2. Assumptions & Constraints 9.8. Decision Analysis new capabilities
9.10. Estimation • Solution components that wil be
9.32. SWOT Analysis delivered (processes, software app,
3. Ranking & Selection of Approaches
etc)
2. FEASIBILITY STUDY • Methodology used to deliver
5.4. Define 1. Solution Scope Definition 1. GENERAL 5.4. SOLUTION SCOPE
Solution Scope 9.12. Functional Decomposition
9.13. Interface Analysis • What must delivered to meet Business
9.27. Scope Modeling Need, and
2. Implementation Approach 9.33. User Stories • The effect of the proposed change
initiative (business & technology
2. PROBLEM OR VISION STATEMENT operations & infrastructure)
• Problem
3. Dependencies • Affects
• Impact
• Successful Solution

5.5. Define 1. Benefits 9.8. Decision Analysis 5.5. BUSINESS CASE

Business Case 9.10. Estimation
2. Costs 9.16. Metrics & Key Perform. Indicators • Information to support a GO / NO GO
9.24. Risk Analysis decision to invest & move forward with
3. Risks Assessment 9.32. SWOT Analysis proposed project
9.34. Vendor Assessment
4. Result Measurement
 6. REQUIREMENTS ANALYSIS
Task Elements Important topics Techniques Outputs
6.1. Prioritize 1. Basis for Prioritization • Business Value 1. GENERAL 6.1. REQUIREMENTS [PRIORITIZED]
Requirements • Business or Technical Risk 9.8. Decision Analysis
• Implementation Difficulty 9.24. Risk Analysis • Reqs with assigned priority
• Likelihood of Success
• Regulatory or Policy Compliance 2. MoSCoW ANALYSIS
• Relationship to other requirements 3. TIMEBOXING / BUDGETING
• Stakeholder Agreement • All in
• Urgency • All out
2. Challenges • Non-negotiable Demands • Selective
• Unrealistic Tradeoff 4. VOTING

6.2. Organize 1. Levels of Abstraction 9.4. Business Rules Analysis 6.2. REQUIREMENTS STRUCTURE
Requirements 2. Model Selection PUREE 9.6.Data Flow Diagrams
• Processes 9.7.Data Modeling • NO TRACING STRUCTURE
• User Classes, Profiles or Roles 9.12. Functional Decomposition • Organized structure for reqs.
• Rules 9.19. Organization Modeling • Documented set of relationships between
• Entities (Concepts & Relationships) 9.21. Process Modeling them
• Events 9.26. Scenarios & Use Cases
9.27. Scope Modeling
9.33. User Stories
6.3. Specify & 1. Text 9.1. A&E Criteria Definition 6.3. REQUIREMENTS [ANALIZED]
Model 2. Matrix Documentation 9.4.Business Rules Analysis
Requirements 3. Models 9.5.Data Dictionary Glossary • Modeled & Specified requirements
4. Capture Requirements Attributes
9.6.Data Flow Diagrams
5. Improvement Opportunities • Automate or Simplify the work people
9.7.Data Modeling
perform
9.12. Functional Decomposition
• Improve Access to Information
9.13. Interface Analysis
• Reduce Complexity of Interfaces
9.16. Metrics & Key Performance
• Increase Consistency Of Behavior
Indicators
• Eliminate Redundancy
9.17. Non-functional Requirements
9.19. Organization Modeling
9.21. Process Modeling
9.22. Prototiping
9.26. Scenarios & Use Cases
9.28. Sequence Diagrams
9.29. State Diagrams
9.33. User Stories
6.4. Define 1. Assumptions 9.20. Problem Tracking 6.4. ASSUMPTIONS & CONSTRAINTS
Assumptions & 2. Business Constraints 9.24. Risk Analysis
Constraints 3. Technical Constraints • Both will limit potential solution options
• Will be monitored for potential changes

6.5. Verify 1. Characteristics of Requirements Quality CCCC MUFT 1. GENERAL 6.5. REQUIREMENTS [VERIFIED]
Requirements • Cohesive 9.1. A&E Criteria Definition
• Complete 9.20. Problem Tracking • Reqs have sufficient quality to allow
• Consistent 9.30. Structured Walkthrough further work
• Correct
• Modifiable 2. CHECKLIST
• Unambiguous
• Feasible
• Testeable

2. Verification Activities
6.6. Validate 1. Identify Assumptions 9.1. A&E Criteria Definition 6.6. REQUIREMENTS [VALIDATED]
Requirements 2. Define Measurable Evaluation Criteria 9.16. Metrics & Key Performance Indicators
3. Determine Business Value 9.22. Prototiping • Reqs can demostrate to deliver value
4. Determine Dependencies for Benefits Realizations
9.24. Risk Analysis to stakeholder
5. Evaluate Alignment with Business Case & • Are aligned with business goal & objectives
9.30. Structured Walkthrough
Opportunity Cost
 7. SOLUTION ASSESSMENT & VALIDATION
Task Elements Important topics Techniques Outputs
7.1. Assess 1. Rank fo Solution Options 9.1. A&E Criteria Definition 7.1. ASSESSMENT PROPOSED SOLUTION
Proposed 9.8. Decision Analysis
Solution 2. Identification of Additional Potential 9.34. Vendor Assessment • Assess the value delivered by each
Capabilities proposed solution
• If there are multiple solutions, choose the
best
7.2. Allocate 1. Solution Components • Available Resources 9.1. A&E Criteria Definition 7.2. REQUIREMENTS [ALLOCATED]
Requirements • Constraints on the solution 9.4. Business Rules Analysis
• Dependencies between requirements 9.8. Decision Analysis • Are associated with solution component that
9.12. Functional Decomposition will implement them
2. Release Planning 9.21. Process Modeling
9.26. Scenarios & Use Cases

7.3. Assess 1. Cultural Assessment 1. GENERAL 7.3. ORGANIZATIONAL READINESS

Organizational 9.1. A&E Criteria Definition ASSESSMENT
Readiness 9.6. Data Flow Diagrams, & 9.21. Process Models
2. Operational or technical Assessment 9.11. Focus Groups, 9.14. Interviews & 9.31. • Description if stakeholders are preparated to
Survey / Questionnaire accept the change associated with a
3. Stakeholder Impact Analysis • Functions 9.19. Organization Modeling solution
• Location 9.20. Problem Tracking
• Tasks 9.24. Risk Analysis
• Concerns 9.32. SWOT Analysis

2. FORCE FIELD ANALYSIS

7.4. Define 1. Data 9.4. Business Rules Analysis 7.4. TRANSITION REQUIREMENTS
Transition 9.6.Data Flow Diagrams, & 9.21. Process Models
Requirements 9.7.Data Modeling • Capabilities that must be developed
2. Ongoing Work for organization successfully transition
between solution
3. Organizational Change • They are Analized, and must be
verified, validated, managed &
communicated
7.5. Validate 1. Investigate Defective Solution Outputs 9.1. A&E Criteria Definition 7.5. IDENTIFIED DEFECTS
Solution 9.20. Problem Tracking • Knows problems that exists in a solution
9.25. Root Cause Analysis
7.5. MITIGATING ACTIONS
• Steps or processes to reduce or eliminate
the effect of defect
2. Assess Defect & Issues
7.5. SOLUTION VALIDATION ASSESSMENT
• Assessment if solution is able to meet
business need, or has acceptable level of
quality
7.6. Evaluate 1. Understand Valued Delivered By Solution 9.8. Decision Analysis 7.6. SOLUTION PERFORMANCE
Solution 9.11. Focus Groups ASSESSMENT
2. Validate Solution Metrics
Performance 9.18. Observation • How solution is performing in relation
3. Solution Replacement or Elimination • Ongoing Cost versus Initial 9.31. Survey / Questionnaire to business goals & objectives
Investment
• Opportunity Cost
• Necessity
• Sunk Cost