Task Elements Important topics Techniques Outputs

2.1. Plan
Business
Analysis
Approach
1. Timing BA Work
2. Formality & Level of Detail Deliverables
3. Requirements Prioritization
4. Change Management
5. BA Planning Process
6. Communication with Stakeholder
7. Reqs Analysis & Mgmt Tools
8. Project Complexity
Plan Driven Approach
Change Driven Approach
9.8. Decision Analysis
9.21. Process Modeling
9.30. Structured Walkthrough
2.1. BA APPROACH
Team Roles
Deliverables
Analysis Techniques
Timing & Frecuency stakeholders interactions
1. Identification
2. Complexity of Stakeholder Group Number & variety of directs end users
Number of interfacing Business Processes & Automated Systems
3. Attitude & Influence Attitude:
Influence:
On Project
In Organization
Needed for the good of project
With other Stakeholders
4. Authority Level for BA Work
1. Geographic Distribution of Stakeholders Collocated
Dispersed
2. Type of Project or Initiative Type of Project or initiative
3. BA Deliverables
4. Determine BA Activities WBS
Activity List
Unique Number
Activity Description
Assumptions
Dependencies
Milestones
1. Geography
2. Culture Relationship to time
Relationship to task completion
Relationship to contracts
Relationship to formal & informal authority
3. Project Type New, customized in-house software development project
Upgrading technology or infrastructure system
Change a business Process or new data for existing app
Purchase software package
Short, focused, agile style iterations of software dev
4. Communication Frequency
5. Communication Formality
1. Repository
2. Traceability
3. Select Requirements Attributes CARAS SOUPS:
Complexity
Absolute Reference
Risk
Author
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
Benefits & Risk of the change
Recommended course of actions for change
Coordinate Prioritization of Change
6. Tailoring Reqs Mgmt Process Organizational Culture
Stakeholder Preferences
Complexity of Project, phase or product-service
Organizational Maturity
Availability Resources
1. Performance Measures
2. Performance Reporting
3. Preventive & Corrective Action
2.6. Manage BA
Performance
1. GENERAL
9.14. Interview
9.15. Lesson Learned Process
9.16. Metrics & Key Perform. Indicators
9.20. Problem Tracking
9.21. Process Modeling
9.25. Root Cause Analysis
9.31. Survey / Questionnaire
2. VARIANCE ANALYSIS
2.6. BA PERFORMANCE ASSESSMENT
Comparison planned vs. Actual performance
Root Cause of variance plan
Level of effort requred to complete
2.6. BA PROCESS ASSETS
Recommnedations for improvement
May be incorporated in OPA
2.4. Plan BA
Communication
9.30. Structured Walkthrough 2.4. BUSINESS ANALYSIS COMUNICATION
PLAN
How, when & why BA Works with stakeholders
Communication Requirements
Format, Content, Medium, Level of Detail
Responsability for Collection, distributing,
accessing and updating information
2.5. Plan
Requirement
Management
Process
2. BUSINESS ANALYSIS PLANNING & MONITORING
9.8. Decision Analysis
9.20. Problem Tracking
9.24. Risk Analysis
2.5. REQUIREMENTS MANAGEMENT PLAN
Approach structure Traceability
Reqs attributes to be used
Reqs prioritization Process
Reqs change process: how changes will be
requested, analyzed, approved & implemented
1. GENERAL
9.1. A&E Criteria Definition
9.3. Brainstorming
9.14. Interviews
9.19. Organization Modeling
9.21. Process Modeling
9.23. Requirements Workshop
9.24. Risk Analysis
9.26. Scenarios & Use Cases, & 9.33. User Stories
9.27. Scope Modeling
9.31. Survey / Questionnaire
2. RACI Matrix
3. Stakeholder Map
2.2. STAKEHOLDERS LIST, ROLES &
RESPONSIBILITIES
List required roles
Names titles stakeholders
Category stakeholders
Locations stakeholders
Special needs
Number stakeholders per role
Description Influence & Unterest
Documentation stakeholder authority levels
2.2. Conduct
Stakeholder
Analysis
2.3. Plan BA
Activities
9.10. Estimation
9.12. Functional Decomposition
9.24. Risk Analysis
2.3. BUSINESS ANALYSIS PLAN
Description scope of work
Deliverables of WBS
Activity List
Estimates each activity
Task Elements Important topics Techniques Outputs
3.1. Prepare for
Elicitation
Clarify specific scope
Schedule all resources (people, facilities, equipment)
Notify appropriate parties of the plan
DIP OF RIBS 3.1. SCHEDULED RESOURCES
Participants
Locations
3.1. SUPPORTING MATERIALS
Any material required to help explain
techniques
3.2. Conduct
Elicitation
Activities
Tracing Requirements
Capturing requirements attributes
Metrics
9.5. Data Dictionary & Glossary
DIP OF RIBS
3.2. ELICITATION RESULTS
Appropiate Docmentation Information from
stakeholder
3.3. Document
Elicitarion
Results
Written Documents
Visual, Audio Recordings
Whiteboards
9.20. Problem Tracking
DIP OF RIBS
3.3. REQUIREMENTS [STATED]
Stated: stakeholder perspective
3.3. STAKEHOLDER CONCERNS
Issues identified by stakeholder, risk,
assumptions, constraints
3.4. Confirm
Elicitation
Results
Relevant Techniques 9.14. Interviews
9.18. Observation
3.4. REQUIREMENTS [STATED, CONFIRMED]
Stated: stakeholder perspective
Including as input to other tasks
3.4. STAKEHOLDER CONCERNS
Issues identified by stakeholder, risk,
assumptions, constraints.
Including as input to other tasks
3. ELICITACION
Task Elements Important topics Techniques Outputs
1. Solution Scope Management
2. Conflict & Issue Management
3. Presenting Reqs for Review
4. Approval
1. Relationships Reasons to create Relationships:
Impact Analysis
Requirements Coverage
Requirements Allocation
Types of Relationships:
Necessity
Effort
Subset
Cover
Value
2. Impact Analysis
3. Configuration Management System
1. Ongoing Requirements
2. Satisfied Requirements
Formal Documentation
Presentation
Models
1. Work Products & Deliverables
2. Format
1. General Communication Enterprise Analysis Tasks
Elicitation Tasks
Requirement Analysis Tasks
Solution Assessment & Validation Tasks
2. Presentations Formal
Informal
4.5.
Communicate
Requirements
9.23. Requirements Workshop
9.30. Structured Walkthrough
4.5. COMMUNICATED REQUIREMENTS
Requirements communicated (and their current
state) to stakeholders
4.2. Manage
Requirements
Traceability
COVERAGE MATRIX 4.2. REQUIREMENTS [TRACED]
Traced Reqs have clearly defined relationship
to other requirements within solution scope
4.3. Maintain
Requirements for
Re-use
4.3. REQUIREMENTS [MAINTAINED &
REUSABLE]
Reqs for long-term usage by organization
4. REQUIREMENTS MANAGEMENT & COMMUNICATION
4.4. Prepare
Requirements
Package
1. REQUIREMENTS DOCUMENTATION
- Business Requirements Documents
- Product Roadmap
- Software/System Reqs Specification
- Supplementary Reqs Specification
- Vision Document
2. REQUIREMENTS FOR VENDORS SELECTION
- RFI
- RFQ
- RFP
4.4. REQUIREMENTS PACKAGE
Documents
Presentations
May be broken into several sub packages
ready to be reviewed by stakeholders
4.1. Define
Solution Scope &
Requirements
1. GENERAL
9.20. Problem Tracking
2. BASELINING
3. SIGN OFF
4.1. REQUIREMENTS [APPROVED]
Are agreed to by stakeholders & ready for use
Task Elements Important topics Techniques Outputs
1. Business Goals & Objectives SMART
2. Business Problem or Opportunity
3. Desired Outcome
1. Current Capability Analysis
2. Assessment of New Capability Requirements
3. Assumptions
1. Alternative Generation
2. Assumptions & Constraints
3. Ranking & Selection of Approaches
1. Solution Scope Definition
2. Implementation Approach
3. Dependencies
1. Benefits
2. Costs
3. Risks Assessment
4. Result Measurement
5.2. Assess
Capability Gaps
9.9. Document Analysis
9.32. SWOT Analysis
5.2. REQUIRED CAPABILITIES
Understanding of current Capabilities
New Capabilites (processes, staff, features
app, etc)
5. ENTERPRISE ANALYSIS
5.5. Define
Business Case
9.8. Decision Analysis
9.10. Estimation
9.16. Metrics & Key Perform. Indicators
9.24. Risk Analysis
9.32. SWOT Analysis
9.34. Vendor Assessment
5.5. BUSINESS CASE
Information to support a GO / NO GO decision
to invest & move forward with proposed project
5.3. Determine
Solution
Approach
1. GENERAL
9.2. Benchmarking
9.3. Brainstorming
9.8. Decision Analysis
9.10. Estimation
9.32. SWOT Analysis
2. FEASIBILITY STUDY
5.3. SOLUTION APPROACH
Approach that will be taken to implement new
capabilities
Solution components that wil be delivered
(processes, software app, etc)
Methodology used to deliver
5.4. Define
Solution Scope
1. GENERAL
9.12. Functional Decomposition
9.13. Interface Analysis
9.27. Scope Modeling
9.33. User Stories
2. PROBLEM OR VISION STATEMENT
Problem
Affects
Impact
Successful Solution
5.4. SOLUTION SCOPE
What must delivered to meet Business Need,
and
The effect of the proposed change initiative
(business & technology operations &
infrastructure)
5.1. Define
Business Need
9.2. Benchmarking
9.3. Brainstorming
9.4. Business Rules Analysis
9.11. Focus Groups
9.12. Functional Decomposition
9.25. Root Cause Analysis
5.1. BUSINESS NEED
Problem organization is facing, or
Opportunity that is not taken
(and desired outcome)
Task Elements Important topics Techniques Outputs
1. Basis for Prioritization Business Value
Business or Technical Risk
Implementation Difficulty
Likelihood of Success
Regulatory or Policy Compliance
Relationship to other requirements
Stakeholder Agreement
Urgency
2. Challenges Non-negotiable Demands
Unrealistic Tradeoff
1. Levels of Abstraction
2. Model Selection PUREE
Processes
User Classes, Profiles or Roles
Rules
Entities (Concepts & Relationships)
Events
1. Text
2. Matrix Documentation
3. Models
4. Capture Requirements Attributes
5. Improvement Opportunities Automate or Simplify the work people perform
Improve Access to Information
Reduce Complexity of Interfaces
Increase Consistency Of Behavior
Eliminate Redundancy
1. Assumptions
2. Business Constraints
3. Technical Constraints
1. Characteristics of Requirements Quality CCCC MUFT
Cohesive
Complete
Consistent
Correct
Modifiable
Unambiguous
Feasible
Testeable
2. Verification Activities
1. Identify Assumptions
2. Define Measurable Evaluation Criteria
3. Determine Business Value
4. Determine Dependencies for Benefits Realizations
5. Evaluate Alignment with Business Case & Opportunity
Cost
9.1. A&E Criteria Definition
9.4. Business Rules Analysis
9.5. Data Dictionary Glossary
9.6. Data Flow Diagrams
9.7. Data Modeling
9.12. Functional Decomposition
9.13. Interface Analysis
9.16. Metrics & Key Performance Indicators
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.3. REQUIREMENTS [ANALIZED]
Modeled & Specified requirements
6.1. Prioritize
Requirements
1. GENERAL
9.8. Decision Analysis
9.24. Risk Analysis
2. MoSCoW ANALYSIS
3. TIMEBOXING / BUDGETING
All in
All out
Selective
4. VOTING
6.1. REQUIREMENTS [PRIORITIZED]
Reqs with assigned priority
6. REQUIREMENTS ANALYSIS
6.6. Validate
Requirements
9.1. A&E Criteria Definition
9.16. Metrics & Key Performance Indicators
9.22. Prototiping
9.24. Risk Analysis
9.30. Structured Walkthrough
6.6. REQUIREMENTS [VALIDATED]
Reqs can demostrate to deliver value to
stakeholder
Are aligned with business goal & objectives
6.4. Define
Assumptions &
Constraints
9.20. Problem Tracking
9.24. Risk Analysis
6.4. ASSUMPTIONS & CONSTRAINTS
Both will limit potential solution options
Will be monitored for potential changes
6.5. Verify
Requirements
1. GENERAL
9.1. A&E Criteria Definition
9.20. Problem Tracking
9.30. Structured Walkthrough
2. CHECKLIST
6.5. REQUIREMENTS [VERIFIED]
Reqs have sufficient quality to allow further
work
6.2. Organize
Requirements
9.4. Business Rules Analysis
9.6. Data Flow Diagrams
9.7. Data Modeling
9.12. Functional Decomposition
9.19. Organization Modeling
9.21. Process Modeling
9.26. Scenarios & Use Cases
9.27. Scope Modeling
9.33. User Stories
6.2. REQUIREMENTS STRUCTURE
NO TRACING STRUCTURE
Organized structure for reqs.
Documented set of relationships between them
6.3. Specify &
Model
Requirements
Task Elements Important topics Techniques Outputs
1. Rank fo Solution Options
2. Identification of Additional Potential Capabilities
1. Solution Components Available Resources
Constraints on the solution
Dependencies between requirements
2. Release Planning
1. Cultural Assessment
2. Operational or technical Assessment
3. Stakeholder Impact Analysis Functions
Location
Tasks
Concerns
1. Data
2. Ongoing Work
3. Organizational Change
1. Investigate Defective Solution Outputs
2. Assess Defect & Issues
1. Understand Valued Delivered By Solution
2. Validate Solution Metrics
3. Solution Replacement or Elimination Ongoing Cost versus Initial Investment
Opportunity Cost
Necessity
Sunk Cost
7.3. Assess
Organizational
Readiness
1. GENERAL
9.1. A&E Criteria Definition
9.6. Data Flow Diagrams, & 9.21. Process Models
9.11. Focus Groups, 9.14. Interviews & 9.31. Survey /
Questionnaire
9.19. Organization Modeling
9.20. Problem Tracking
9.24. Risk Analysis
9.32. SWOT Analysis
2. FORCE FIELD ANALYSIS
7.3. ORGANIZATIONAL READINESS
ASSESSMENT
Description if stakeholders are preparated to
accept the change associated with a solution
7.1. Assess
Proposed
Solution
9.1. A&E Criteria Definition
9.8. Decision Analysis
9.34. Vendor Assessment
7.1. ASSESSMENT PROPOSED SOLUTION
Assess the value delivered by each proposed
solution
If there are multiple solutions, choose the best
7.6. Evaluate
Solution
Performance
9.8. Decision Analysis
9.11. Focus Groups
9.18. Observation
9.31. Survey / Questionnaire
7.6. SOLUTION PERFORMANCE
ASSESSMENT
How solution is performing in relation to
business goals & objectives
7. SOLUTION ASSESSMENT & VALIDATION
7.4. Define
Transition
Requirements
9.4. Business Rules Analysis
9.6. Data Flow Diagrams, & 9.21. Process Models
9.7. Data Modeling
7.4. TRANSITION REQUIREMENTS
Capabilities that must be developed for
organization successfully transition between
solution
They are Analized, and must be verified,
validated, managed & communicated
7.5. Validate
Solution
9.1. A&E Criteria Definition
9.20. Problem Tracking
9.25. Root Cause Analysis
7.5. IDENTIFIED DEFECTS
Knows problems that exists in a solution
7.5. MITIGATING ACTIONS
Steps or processes to reduce or eliminate the
effect of defect
7.5. SOLUTION VALIDATION ASSESSMENT
Assessment if solution is able to meet business
need, or has acceptable level of quality
7.2. Allocate
Requirements
9.1. A&E Criteria Definition
9.4. Business Rules Analysis
9.8. Decision Analysis
9.12. Functional Decomposition
9.21. Process Modeling
9.26. Scenarios & Use Cases
7.2. REQUIREMENTS [ALLOCATED]
Are associated with solution component that
will implement them