Mind Map Gallery Babok Guide 3.0
- 223
- 2
Babok Guide 3.0
This is the mind map about the Babok Guide and sees more mind maps in my profile.
Edited at 2020-10-08 08:45:36
- Recommended to you
- Outline
Babok-Guide-3.0
BA Planning & Monitoring
3.1 Plan BA Approach
Purpose
Is to define an appropriatemethod to conduct business analysisactivities.
Description
Input
Needs
Elements
Planning Approach
Formality & Level of Details of BA deliverables
BA Activities
Timing of BA work
Complexity & Risks
Acceptance
Guidelines & Tools
BA Performance Assessment
Business Policies
Expert Judgment
Methodologies & Frameworks
Stakeholder Engagement Approach
Techniques
Brainstorming
Business Case
Document Analysis
Estimation
Financial Analysis
Functional Decomposition
Interview
Item Tracking
Lessons Learned
Process Modeling
Reviews
Risk Analysis & Management
Scope Modeling
Survey & Questionnaire
Workshops
Stakeholders
Domain Subject Matter Expert
Project Manager
Regulator
Sponsor
Output
BA Approach
3.2 Plan Stakeholder Engagement
Purpose
is to plan an approach for establishing and maintaining effective working relationships with the stakeholders.
Description
Input
Needs
BA approach
Elements
Perform stakeholder analysis
Roles
Attitudes
Decision Making Authority
Level of power or influence
Define stakeholder collaboration
Stakeholder communication needs
Guidelines & Tools
BA Performance Assessment
Change Strategy
Current State Description
Techniques
Brainstorming
Business Rules Analysis
Document Analysis
Interviews
Lessons Learned
Mind Mapping
Organizational Modelling
Process Modeling
Risk Analysis and Management
Scope Modelling
Stakeholder List, Map or Personas
Survey or Questionaire
Workshops
Stakeholders
Customers
Domain SME
End User
Project Manager
Regulator
Sponsor
Supplier
Output
Stakeholder Engagement Approach
3.3 Plan Business Analysis Governance
Purpose
to define how decisions are made aboutrequirements and designs, including reviews,change controle, approvals and prioritization
Inputs
BA Approach
Stakeholder Engagement Approach
Elements
Decision Making
Change Controll Process
Determine the process forrequesting changes
Determine the elements of thechange request
Determine how changes will be prioritizes
Determine how changes will be documented
Determine how changes willbe communicated
Determine who will performthe impact analysis
Determine who will authorize changes
Plan Prioritization Approach
Guidelines & Tools
BA Performance Assessment
Business Policies
Current State Description
Legal/Regulatory Information
Techniques
Brainstorming
Document Analysis
Interviews
Item Tracking
Lessons Learned
Organizational Modelling
Process Modelling
Reviews
Survey or Questionaire
Workshops
Stakehgolders
Domain SME
Project Manager
Regulator
Sponsor
Ouputs
Governance Approach
3.4 Plan Business AnalysisInformation Management
Purpose
to develop an approach for how BAinformation will be stored andaccessed
Inputs
BA Approach
Governance Approach
Stakeholder Engagement Approach
Elements
Organization of BA Information
Level of Abstraction
Plan Traceability Approach
Plan for Requirements Reuse
Storage and Access
Requirements Attributes
Guidelines & Tools
BA Performance Assessment
Business Policies
Information Management Tools
Legal/Regulatory Information
Techniques
Brainstorming
Interviews
Item Tracking
Lessons Learned
Mind Mapping
Process Modelling
Survey or Questionaire
Workshops
Stakeholders
Domain SME
Regulator
Sponsor
Outputs
Information Management Approach
3.5 Identify Business AnalysisPerformance Improvements
Purpose
to assess BA work and to plan toimprove processes whererequired
Inputs
BA Approach
Performance Objectives (external)
Elements
Performance Analysis
Assessment Measures
Accuracy and Completeness
Knowledge
Effectiveness
Organizational Support
Significance
Strategic
Timeliness
Analyze Results
Recommend Actions for Improvement
Preventive
Corrective
Improvement
Guidelines & Tools
Organizational Performance Standards
Techniques
Brainstorming
Interviews
Item Tracking
Lessons Learned
Metrics and KPIs
Observation
Process Analysis
Process Modelling
Reviews
Risk Analysis & Management
Root Cause Analysis
Survey or Questionaire
Workshops
Stakeholders
Domain SME
Project Manager
Sponsor
Outputs
BA Performance Assessment
Elicitation and Collaboration
4.1 Prepare for Elicitation
Purpose
to understand the scope or the elicitationactivity. Select appropriate techniques and planfor appropriate supporting materials andresources
Inputs
Needs
Stakeholder Engagement Approach
Elements
Understand the Scope of Elicitation
Select Elicitation Techniques
Set up Logistics
Secure Supporting Material
Prepare Stakeholders
Guidelines & Tools
BA Approach
Business Objectives
Existing BA Information
Potential Value
Techniques
Brainstorming
Data Mining
Document Analysis
Estimation
Interviews
Mind Mapping
Risk Analysis & Management
Stakeholder List, Map or Personas
Stakeholders
Domain SME
Project Manager
Sponsor
Outputs
Elicitaion Activity Plan
4.2 Conduct Elicitation
Purpose
to draw out, explore, and identifyinformation relevant to thechange
Description
Collaborative
Research
Experiments
Inputs
Elicitation Activity Plan
Elements
Guide Elicitation Activity
Capture Elicitation Outcomes
Guidelines & Tools
BA Approach
Existing BA Information
Stakeholder Engagement Approach
Supporting Materials
Techniques
Benchmarking and Market Analysis
Brainstorming
Business Rules Analysis
Collaborative Games
Concept Modelling
Data Mining
Data Modelling
Document Analysis
Focus Groups
Interface Analysis
Interviews
Mind Mapping
Observation
Process Analysis
Process Modeling
Prototyping
Survey or Questionaire
Workshops
Stakeholders
Customer
Domain SME
End User
Implementation SME
Sponsor
Any Stakeholders
Outputs
Elicitation Results (unconfirmed)
4.3 Confirm Elicitation Results
Purpose
to check the information gathered during anelicitation session for accuracy and consistencywith other information
Inputs
Elicitation Results (unconfirmed)
Elements
Compare Elicitation ResultsAgainst Source Information
Compare Elicitation ResultsAgainst Other ElicitationResults
Guidelines & Tools
Elicitation Activity Plan
Existing BA Information
Techniques
Document Analysis
Interviews
Reviews
Workshops
Stakeholders
Domain SME
Any Stakeholder
Outputs
Elicitation Results (confirmed)
4.4 Communicate BA Information
Purpose
to ensure stakeholders have ashared understanding of BAinformation
Inputs
BA Information
Stakeholder Engagement Approach
Elements
Determine Objectives andFormat of Communication
Formal Documentation
Informal Documentation
Preseentations
Communicate BA Package
Group collaboration
Individual collaboration
Email or other nonverbal methods
Guideline & Tools
BA Approach
Information Management Approach
Techniques
Intervies
Reviews
Workshops
Stakeholders
End User
Customer
Domain SME
Implementation SME
Tester
Any Stakeholder
Outputs
BA Information (communicated)
4.5 Manage Stakeholder Collaboration
Purpose
to encourage stakeholders towork towards a common goal
Inputs
Stakeholder Engagement Approach
BA Performance Assessment
Elements
Gain Agreement on Commitments
Monitor Stakeholder Engagement
Collaboration
Guidelines & Tools
BA Approach
Business Objectives
Future State Description
Recommended Actions
Risk Analysis Results
Techniques
Collaborative Games
Lessons Learned
Risk Analysis and Management
Stakeholder List, Map or Personas
Stakeholders
All stakeholders
Outputs
Stakeholder Engagement
Requirements Life Cycle Management
5.1 Trace Requirements
Purpose
to ensure that requirements and designs at differentlevels are aligned to one another, and to manage theeffects of change to one level on relatedrequirements
Description
Process Traceability
Inputs
Requirements
Designs
Elements
Level of Formality
Relationships
Derive
Depends
Necessity
Effort
Satisfy
Validate
Traceability Repository
Guidelines & Tools
Domain Knowledge
Information Management Approach
Legal/Regulatory Information
Requirements Management Tools/Repository
Techniques
Business Rules Analysis
Functional Decomposition
Process Modelling
Scope Modelling
Stakeholders
Customers
Domain SME
End User
Implementation SME
Operational Support
Project Manager
Sponsor
Suppliers
Tester
Outputs
Requirements (traced)
Designs (traced)
5.2 Maintain Requirements
Purpose
to retain requirement accuracy and consistency throughoutand beyound the change during the entire requirements lifecycle, and to support reuse of requirements in othersolutions
Inputs
Requirements
Designs
Elements
Maintain Requirements
Maintain Attributes
Reusing Requirements
Guidelines & Tools
Information Management Approach
Techniques
Business Rules Analysis
Data Flow Diagrams
Data Modelling
Document Analysis
Functional Decomposition
Process Modelling
Use Cases and Scenarios
User Stories
Stakeholders
Domain SME
Implementation SME
Operational Support
Regulator
Tester
Outputs
Requirements (maintained)
Designs (maintained)
5.3 Prioritize Requirements
Purpose
to rank requirements in theorder of relative importance
Inputs
Requirements
Designs
Elements
Basis for Prioritization
Benefit
Penalty
Cost
Risk
Dependencies
Time Sensitivity
Stability
Regulatory or Poilicy Compliance
Challenges of Prioritization
Continual Prioritization
Guidelines & Tools
Business Constraints
Change Strategy
Domain Knowledge
Governance Approach
Requirements Architecture
Requirements Management Tools/Repository
Solution Scope
Techniques
Backlog Management
Business Cases
Decision Analysis
Estimation
Financial Analysis
Interviews
Item Tracking
Priotization
Risk Analysis and Management
Workshops
Stakeholders
Customer
End User
Implementation SME
Project Manager
Regulator
Sponsor
Outputs
Requirements (prioritized)
Design (prioritized)
5.4 Assess Requirements Changes
Purpose
to evaluate the implications ofproposed changes to requirementsand designs
Inputs
Proposed Change
Requirements
Designs
Elements
Assessment Formality
Impact Analysis
Benefit
Cost
Impact
Schedule
Urgency
Impact Resolution
Guidelines & Tools
Change Strategy
Domain Knowledge
Governance Approach
Legal/Regulatory Information
Requirements Architecture
Solution Scope
Techniques
Business Cases
Business Rules Analysis
Decision Analysis
Document Analysis
Estimation
Financial Analysis
Interface Analysis
Interviews
Item Tracking
Risk Analysis and Management
Workshops
Stakeholders
Customer
Domain SME
End User
Operational Support
Project Manager
Regulator
Sponsor
Tester
Outputs
Requirements Change Assessment
Designs Change Assessment
5.5 Approve Requirements
Purpose
to obtain agreement on and approval ofrequirements and designs for BA work tocontinue and/or solution construction toproceed
Inputs
Requirements (verified)
Designs
Elements
Understand Stakeholder Roles
Conflict and Issue Management
Gain Consensus
Track and Communicate Approval
Guidelines & Tools
Change Strategy
Governance Approach
Legal/Regulatory Information
Requirement Management Tools/Repository
Solution Scope
Techniques
Acceptance and Evaluation Criteria
Decision Analysis
Item Tracking
Reviews
Workshops
Stakeholders
Customer
Domain SME
End User
Operational Support
Project Manager
Regulator
Sponsor
Tester
Outputs
Requirements (approved)
Designs (approved)
Strategy Analysis
6.1 Analyze Current State
Purpose
to understand the reasons why an enterprise needsto change some aspect of how it operates and whatwould be directly or indirectly affected by thechange
Inputs
Elicitation Results
Needs
Elements
Business Needs
From the topdown
From the bottomup
From middle management
From external drivers
Organizational Structure & Culture
Capabilities & Processes
capabilitycentric view
processcentric view
Technology & Infrastructure
Plicies
Business Architecture
Internal Assets
External Influencers
Industry Structure
Competitors
Customers
Suppliers
Political & Regulatory Environment
Technology
Macroeconomic Factors
Guidelines & Tools
BA Approach
Enterprise Limitation
Organizational Strategy
Solution Limitation
Solution Performance Goals
Solution Performance Measures
Stakeholder Analysis Results
Techniques
Benchmarking & Market Analysis
Business Capability Analysis
Business Model Canvas
Business Cases
Concept Modelling
Data Mining
Document Analysis
Financial Analysis
Focus Groups
Functional Decomposition
Interviews
Item Tracking
Lessons Learned
Metrics & KPIs
Mind Mapping
Observation
Organizational Modelling
Process Analysis
Process Modelling
Risk Analysis and Management
Root Cause Analysis
Scope Modelling
Survey or Questionaire
SWOT Analysis
Vendor Assessment
Workshops
Stakeholders
Customer
Domain SME
End User
Implementation SME
Operational Support
Project Manager
Regulator
Sponsor
Supplier
Tester
Outputs
Current State Description
Business Requirements
6.2 Define Future State
Purpose
to determine the set of necessaryconditions to meet the businessneed
Description
business processes
functions
lines of business
organization structures
staff competencies
knowledge and skills
training
facilities
desktop tools
organization locations
data and information
application systems
technology infrastructure
Inputs
Business Requirements
Elements
Business Goals and Objectives
Scope of Solution Space
Constraints
budgetary restrictions
time restrictions
technology
infrastructure
policies
resources
skills of the team and stakeholders
certain stakeholders not beaffected by the solution
compliance with regulations
Organizational Structure & Culture
Capabilities & Processes
Technology and Infrastructure
Policies
Business Architecture
Internal Assets
Identify Assumptions
Potential Value
Guidelines & Tools
Current State Description
Metrics & KPIs
Organizational Strategy
Techniques
Acceptance and Evaluation Criteria
Balanced Scorecard
Benchmarking and Market Analysis
Brainstorming
Business Capability Analysis
Business Cases
Business Model Canvas
Decision Analysis
Decision Modelling
Financial Analysis
Functional Decomposition
Interviews
Lessons Learned
Metrics & KPIs
Mind Mapping
Organizational Modelling
Process Modelling
Prototyping
Scope Modelling
Survey or Questionaire
SWOT Analysis
Vendor Assessment
Workshops
Stakeholders
Customer
Domain SME
End User
Implementation SME
Operational Support
Project Manager
Regulator
Sponsor
Supplier
Tester
Outputs
Business Objectives
Future State Description
Potential Value
6.3 Assess Risks
Purpose
to understand the undesirable consequences ofinternal and external forces on the enterpriseduring a transition to, or once in, the futurestate.
Description
possible consequences if the risk occurs
impact of those consequences
likelihood of the risk
potential time frame when therisk might occur
Inputs
Business Objectives
Elicitation Results (confirmed)
Influences
Potential Value
Requirements (prioritized)
Elements
Unknowns
Constraints, Assumptions & Dependencies
Negative Impact to Value
Risk Tolerance
Riskaversion
Neutrality
Riskseeking
Recommendation
Guidelines & Tools
BA Approach
Business Policies
Change Strategy
Current State Description
Future State Description
Identified Risks
Stakeholder Engagement Approach
Techniques
Brainstorming
Business Cases
Decision Analysis
Financial Analysis
Interviews
Lessons Learned
Mind Mapping
Risk Analysis and Management
Root Cause Analysis
Survey or Questionaire
Workshops
Stakeholders
Domain SME
Implementation SME
Operational Support
Project Manager
Regulator
Sponsor
Supplier
Tester
Outputs
Risk Analysis Results
6.4 Define Change Strategy
Purpose
to develop and assess alternative approachesto the change, and then select therecommended approach
Inputs
Current State Description
Future State Description
Risk Analysis Results
Stakeholder Engagement Approach
Elements
Solution Scope
Gap Analysis
processes
functions
lines of business
organizational structures
staff competencies
knowledge and skills
training
facilities
locations
data and information
application systems
technology infrastructure
Enterprise Readiness Assessment
Change Strategy
Transition States & Release Planning
Guidelines & Tools
BA Approach
Design Options
Solution Recommendations
Techniques
Balanced Scorecard
Benchmarking and Market Analysis
Brainstorming
Business Capability Analysis
Business Cases
Business Model Canvas
Decision Analysis
Estimation
Financial Analysis
Focus Groups
Functional Decomposition
Interviews
Lessons Learned
Mind Mapping
Organizational Modelling
Process Modelling
Scope Modelling
SWOT Analysis
Vendor Assessment
Workshops
Stakeholders
Customer
Domain SME
End User
Implementation SME
Operational Support
Project Manager
Regulator
Sponsor
Supplier
Tester
Outputs
Change Strategy
Solution Scope
Requirements Analysis and Design Definition
7.1 Specify and Model Requirements
Purpose
to analyze, synthesize, and refine elicitationresults into requirements and designs.
Inputs
Elicitation Results
Elements
Model Requirements
Matrices
Diagrams
Categories
People & Roles
Rationale
Activity Flow
Capability
Data & Information
Analyze Requirements
Represent Requirements & Attributes
Implement the Appropriate Levels ofAbstraction
Guideline & Tools
Modelling Notations/Standards
Modelling Tools
Requirements Architecture
Requirements Life Cycle Management Tools
Solution Scope
Techniques
Acceptance and Evaluation Criteria
Business Capability Analysis
Business Model Canvas
Business Rules Analysis
Concept Modelling
Data Dictionary
Data Flow Diagrams
Data Modelling
Decision Modelling
Functional Decomposition
Glossary
Interface Analysis
NonFunctional Requirements Analysis
Organizational Modelling
Process Modelling
Prototyping
Roles and Permissions Matrix
Root Cause Analysis
Scope Modelling
Sequence Diagrams
Stakeholder List, Map, or Personas
State Modelling
Use Cases and Scenarios
User Stories
Outputs
Requirements (specified & modeled)
7.2 Verify Requirements
Purpose
to ensure that requirements and designsspecifications and models meet qualitystandards and are usable for the purpose theyserve
Inputs
Requirements (specified and modelled)
Elements
Characteristics of Requirements & DesignsQuality
Atomic
Complete
Consistent
Concise
Feasible
Unambiguous
Testable
Prioritized
Understandable
Verification Activities
Checklists
Guidelines & Tools
Requirements Life Cycle Management Tools
Techniques
Acceptance and Evaluation Criteria
Item Tracking
Metrics and Key Performance Indicators (KPIs)
Reviews
Outputs
Requirements (verified)
7.3 Validate Requirements
Purpose
to ensure that all requirements and designsalign to the business requirements and supportthe delivery of needed value.
Inputs
Requirements (specified and modelled)
Elements
Identify Assumptions
Define Measurable Evaluation Criteria
Evaluate Alignment with Solution Scope
Guidelines & Tools
Business Objectives
Future State Description
Potential Value
Solution Scope
Techniques
Acceptance and Evaluation Criteria
Document Analysis
Financial Analysis
Item Tracking
Metrics and Key Performance Indicators (KPIs)
Reviews
Risk Analysis and Management
Output
Requirements (validated)
7.4 Define Requirements Architecture
Purpose
to ensure that the requirements collectivelysupport one another to fully achieve theobjectives
Inputs
Information Management Approach
Requirements (any state)
Solution Scope
Elements
Requirements Viewpoints and Views
Business Models
Business Process Models
Data models and information
User interactions, including Use Cases and/orUser Experience
Audit and security
Template Architectures
Completeness
Relate and Verify Requirements Relationships
Defined
Necessary
Correct
Unanbiguous
Consistent
Business Analysis Information Architecture
Guidelines & Tools
Architecture Management Software
Legal/Regulatory Information
Methodologies & Frameworks
Techniques
Data Modelling
Functional Decomposition
Interviews
Organizational Modelling
Scope Modelling
Workshops
Output
Requirements Architecture
7.5 Define Design Options
Purpose
to define the solution approach, identifyopportunities to improve the business, allocaterequirements across solution components, andrepresent design options that achieve thedesired future state
Inputs
Requirements (validated, prioritized)
Change Strategy
Requirements Architecture
Elements
Define Solution Approaches
Create
Purchase
Combination of both
Identify Improvement Opportunities
Increase Efficiencies
Improve Access to Information
Identify Additional Capabilities
Requirements Allocation
Describe Design Options
Guidelines & Tools
Existing Solutions
Future State Description
Requirements (traced)
Solution Scope
Techniques
Benchmarking and Market Analysis
Brainstorming
Document Analysis
Interviews
Lessons Learned
Mind Mapping
Root Cause Analysis
Survey or Questionnaire
Vendor Assessment
Workshops
Output
Design Options
7.6 Analyze Potential Value & RecommendSolution
Purpose
to estimate the potential value for each designoption and to establish which one is mostappropriate to meet the enterprise’srequirements
Inputs
Potential Value
Design Options
Elements
Expected Benefits
Expected Costs
timeline
effort
operating costs
purchase and/or implementation costs
maintenance costs
physical resources
information resources
human resources
Determine Value
Assess Design Options and RecommendSolution
Available Resources
Constraints on the Solution
Dependencies between requirements
Guidelines & Tools
Business Objectives
Current State Description
Future State Description
Risk Analysis Results
Solution Scope
Techniques
Acceptance and Evaluation Criteria
Backlog Management
Brainstorming
Business Cases
Business Model Canvas
Decision Analysis
Estimation
Financial Analysis
Focus Groups
Interviews
Metrics and Key Performance Indicators (KPIs)
Risk Analysis and Management
Survey or Questionnaire
SWOT Analysis
Workshops
Output
Solution Recommendation
Solution Evaluation
8.1 Measure Solution Performance
Purpose
to define performance measures and use thedata collected to evaluate the effectiveness of asolution in relation to the value it brings.
Inputs
Business Objectives
Implemented Solution (external)
Elements
Define Solution Performance Measures
Quantitative Measures
Qualitative Measures
Validate Performance Measures
Collect Performance Measures
Volume or Sample Size
Frequency and Timing
Currency
Guidelines & Tools
Change Strategy
Future State Description
Requirements (validated)
Solution Scope
Techniques
Acceptance and Evaluation Criteria
Benchmarking and Market Analysis
Business Cases
Data Mining
Decision Analysis
Focus Groups
Metrics and Key Performance Indicators (KPIs)
NonFunctional Requirements Analysis
Observation
Prototyping
Survey or Questionnaire
Use Cases and Scenarios
Vendor Assessment
Output
Solution Performance Measures
8.2 Analyze Performance Measures
Purpose
to provide insights into the performance of asolution in relation to the value it brings
Inputs
Potential Value
Solution Performance Measures
Elements
Solution Performance versus Desired Value
Risks
Trends
Accuracy
Performance Variances
Guidelines & Tools
Change Strategy
Future State Description
Risk Analysis Results
Solution Scope
Techniques
Acceptance and Evaluation Criteria
Benchmarking and Market Analysis
Data Mining
Interviews
Metrics and Key Performance Indicators (KPIs)
Observation
Risk Analysis and Management
Root Cause Analysis
Survey or Questionnaire
Output
Solution Performance Analysis
8.3 Assess Solution Limitations
Purpose
to determine the factors internal to the solutionthat restrict the full realization of value
Inputs
Implemented Solution (external)
Solution Performance Analysis
Elements
Identify Internal Solution ComponentDependencies
Investigate Solution Problems
Impact Assessment
severity
probability
impact
capacity to absorb the impact
Guidelines & Tools
Change Strategy
Risks Analysis Results
Solution Scope
Techniques
Acceptance and Evaluation Criteria
Benchmarking and Market Analysis
Business Rules Analysis
Data Mining
Decision Analysis
Interviews
Item Tracking
Lessons Learned
Risk Analysis and Management
Root Cause Analysis
Survey or Questionnaire
Output
Solution Limitation
8.4 Assess Enterprise Limitations
Purpose
to determine how factors external to thesolution are restricting value realization
Inputs
Current State Description
Implemented (or Constructed) Solution(external)
Solution Performance Analysis
Elements
Enterprise Culture Assessment
Stakeholder Impact Analysis
Functions
Locations
Concerns
Organizational Structure Changes
Operational Assessment
policies and procedures
capabilities and processes that enable othercapabilities
skill and training needs
human resources practices
risk tolerance and management approaches
tools and technology that support a solution
Guidelines & Tools
Business Objectives
Change Strategy
Future State Descriptions
Risk Analysis Results
Solution Scope
Techniques
Benchmarking and Market Analysis
Brainstorming
Data Mining
Decision Analysis
Document Analysis
Interviews
Item Tracking
Lessons Learned
Observation
Organizational Modelling
Process Analysis
Process Modelling
Risk Analysis and Management
Roles and Permissions Matrix
Root Cause Analysis
Survey or Questionnaire
SWOT Analysis
Workshops
Stakeholders
Customer
Domain Subject Matter Expert
End User
Regulator
Sponsor
Output
Enterprise Limitation
8.5 Recommend Actions to Increase SolutionValue
Purpose
to understand the factors that create differencesbetween potential value and actual value, andto recommend a course of action to align them
Inputs
Solution Limitation
Enterprise Limitation
Elements
Adjust Solution Performance Measures
Recommendations
Do Nothing
Organizational Change
Reduce Complexity of Interfaces
Eliminate Redundancy
Avoid Waste
Identify Additional Capabilities
Retire the Solution
additional factors
ongoing cost versus initial investment
opportunity cost
necessity
sunk cost
Guidelines & Tools
Business Objectives
Current State Description
Solution Scope
Techniques
Data Mining
Decision Analysis
Financial Analysis
Focus Groups
Organizational Modelling
Prioritization
Process Analysis
Risk Analysis and Management
Survey or Questionnaire
Stakeholders
Customer
Domain Subject Matter Expert
End User
Regulator
Sponsor
Output
Recommended Actions