The document provides an overview of solution evaluation based on the BABOK guide. It discusses the key activities in solution evaluation, including measuring solution performance, analyzing performance measures, assessing solution limitations, assessing enterprise limitations, and recommending actions to increase solution value. For each activity, it outlines the purpose, inputs, elements, outputs, relevant guidelines/tools, stakeholders, and techniques. The document compares solution evaluation in BABOK v2.0 and v3.0 and presents core concept models used in solution evaluation. It is meant to help business analysts understand and apply the solution evaluation knowledge area of the BABOK.

1. Business Analysis
解決方案評價
Moris, CBAP, PMP, PMI-PBA
2015.06.18
商業分析知識體系 (IIBA BABOK v3)

2. 時程規劃
TopicTopic PagePage DateDate OwnerOwner
Ch1 商業分析概論
Ch2 商業分析主要概念
23 5/7
Ch3 商業分析規劃與監控 32 5/14
Ch4 需求導出與協同合作 23 5/21
Ch5 需求生命週期管理 24 5/28
Ch6 策略分析 33 6/4
Ch7 需求分析與設計定義 30 6/11
Ch8 解決方案評價 22 6/18
Ch11 應用觀點 (Agile, BI, IT) 39/71 6/25
Ch11 應用觀點 (BizArc, BPM) 32/71 7/2
註： Skip Ch9 UC, Ch10 Techniques

3. 8. 解決方案評價
 Measure Solution Performance
 Analyze Performance Measures
 Assess Solution Limitations
 Assess Enterprise Limitations
 Recommend Actions to Increase Solution Value

4. 2.0 與 V3 的差異
BABOK 2.0 BABOK V3
7 Solution Assessment and Validation 8 Solution Evaluation
7.1 Assess Proposed Solution 7.5 Define Design Options
7.6 Analyze Potential Value and Recommend
Solution
7.2 Allocate Requirements 7.5 Define Design Options
7.3 Assess Organizational Readiness 6.4 Define Change Strategy
7.4 Define Transition Requirements 6.4 Define Change Strategy
2.3 Requirements Classification Schema
7.5 Validate Solution 8.3 Assess Solution Limitations
7.6 Evaluate Solution Performance 8.5 Recommend Actions to Increase Solution
Value
N/A 8.1 Measure Solution Performance
N/A 8.2 Analyze Performance Measures
N/A 8.4 Assess Enterprise Limitations

5. 核心概念模型
Core Concept During SA, business analysts...
Change recommend a change to either a solution or the enterprise in
order to realize the potential value of a solution.
Need evaluate how a solution or solution component is fulfilling the
need.
Solution assess the performance of the solution, examine if it is
delivering the potential value, and analyze why value may not
be realized by the solution or solution component.
Stakeholder elicit information from the stakeholders about solution
performance and value delivery.
Value determine if the solution is delivering the potential value and
examine why value may not be being realized.
Context consider the context in determining solution performance
measures and any limitations within the context that may
prohibit value from being realized.

6. RA&DD 投入產出
Input Implemented Solution (external)
6.1 Current State Description
6.2 Business Objectives
6.2 Potential Value
Tasks 8.1 Measure Solution Performance
8.2 Analyze Performance Measures
8.3 Assess Solution Limitations
8.4 Assess Enterprise Limitations
8.5 Recommend Actions to Increase Solution Value
Output 8.1 Solution Performance Measures
8.2 Solution Performance Analysis
8.3 Solution Limitation
8.4 Enterprise Limitation
8.5 Recommend Actions

7. 8.1 衡量方案績效
 Purpose
 to define performance measures and use the data
collected to evaluate the effectiveness of a solution in
relation to the value it brings.
 Measure Solution Performance
 Performance measures determine the value of a
newly deployed or existing solution.
 The measures used depend on the solution itself, the
context, and how the organization defines value.
 When solutions do not have built-in performance
measures, the business analyst works with
stakeholders to determine and collect the measures

8. Input-Element-Output
6.2 Business Objectives
• Implemented Solution (external)
.1 Define Solution Performance Measures
.2 Validate Performance Measures
.3 Collect Performance Measures
• Solution Performance Measures
Inputs
Elements
Outputs

9. Outputs
 Solution Performance Measures
 measures that provide information on how well the
solution is performing or potentially could perform.

10. G&T-Stakeholders-Techniques
• Change Strategy
• Future State Descriptions
• Requirements (validated)
• Solution Scope
• Acceptance and Evaluation Criteria
• Benchmarking and Market Analysis
• Business Cases
• Data Mining
• Decision Analysis
• Focus Groups
• Metrics and KPIs
• Non-functional Requirements Analysis
• Observation
• Prototyping
• Survey or Questionnaire
• Use Cases and Scenarios
• Vendor Assessment
• Customer
• Domain SME
• End User
• Project Manager
• Sponsor
• Regulator
Guideline & Tools
Stakeholders
Techniques

11. 8.2 分析績效指標
 Purpose
 to provide insights into the performance of a solution
in relation to the value it brings.
 Analyze Performance Measures
 Performance measures themselves rarely trigger a
decision about the value of a solution
 business analysts require a thorough understanding
of the potential value that stakeholders hope to
achieve with the solution.
 variables such as the goals and objectives, KPIs, risk
of the solution, risk tolerance of stakeholders and the
enterprise are considered.

12. Input-Element-Output
6.2 Potential Value
8.1 Solution Performance Measures
.1 Solution Performance versus Desired Value
.2 Risks
.3 Trends
.4 Accuracy
.5 Performance Variances
• Solution Performance Analysis
Inputs
Elements
Outputs

13. Output
 Solution Performance Analysis
 results of the analysis of measurements collected and
recommendations to solve performance gaps and
leverage opportunities to improve value.

14. G&T-Stakeholders-Techniques
• Change Strategy
• Future State Descriptions
• Risks Analysis Results
• Solution Scope
• Acceptance and Evaluation Criteria
• Benchmarking and Market Analysis
• Data Mining
• Interviews
• Metrics and KPIs
• Observation
• Risk Analysis and Management
• Root Cause Analysis
• Survey or Questionnaire
• Domain SME
• Project Manager
• Sponsor
Guideline & Tools
Stakeholders
Techniques

15. 8.3 評估方案限制
 Purpose
 to determine the factors internal to the solution that
restrict the full realization of value.
 Assessing solution limitations
 identifies the root causes for under-performing and
ineffective solutions and solution components.
 These tasks may be performed concurrently at any
point during the solution life cycle
 If the solution has not met its potential value,
business analysts determine factors that limiting value

16. Input-Element-Output
• Implemented Solution (external)
8.2 Solution Performance Analysis
.1 Identify Internal Solution Component Dependencies
.2 Investigate Solution Problems
.3 Impact Assessment
• Solution Limitation
Inputs
Elements
Outputs

17. Output
 Solution Limitation
 a description of the current limitations of the solution
including constraints and defects.

18. G&T-Stakeholders-Techniques
• Change Strategy
• Risks Analysis Results
• Solution Scope
• 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
• Customer
• Domain SME
• End User
• Regulator
• Sponsor
• Tester
Guideline & Tools
Stakeholders
Techniques

19. 8.4 評估企業限制
 Purpose
 to determine how factors external to the solution are
restricting value realization.
 Assessing enterprise limitations
 Solutions may operate across organizations, and
have many interactions and interdependencies.
 Assessing enterprise limitations identifies root causes
and describes how enterprise factors limit value
realization.
 This assessment may be performed at any point
during the solution life cycle

20. Input-Element-Output
6.1 Current State Description
• Implemented (or Constructed) Solution (external)
8.2 Solution Performance Analysis
.1 Enterprise Culture Assessment
.2 Stakeholder Impact Analysis
.3 Organizational Structure Changes
.4 Operational Assessment
• Enterprise Limitation
Inputs
Elements
Outputs

21. Output
 Enterprise Limitation
 a description of the current limitations of the
enterprise including how the solution performance is
impacting the enterprise.

22. G&T-Stakeholders-Techniques
• Business Objectives
• Change Strategy
• Future State Descriptions
• Risk Analysis Results
• Solution Scope
• 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
• Customer
• Domain SME
• End User
• Regulator
• Sponsor
Guideline & Tools
Stakeholders
Techniques

23. 8.5 建議方案加值行動
 Purpose
 to understand the factors that create differences
between potential value and actual value, and to
recommend a course of action to align them.
 Recommend Actions
 focuses on understanding the aggregate of the
performed assessments
 identifying alternatives and actions to improve solution
performance and increase value realization.
 Recommendations generally identify how a solution
should be replaced, retired, or enhanced

24. Input-Element-Output
8.4 Enterprise Limitation
8.3 Solution Limitation
.1 Adjust Solution Performance Measures
.2 Recommendations
• Recommended Actions
Inputs
Elements
Outputs

25. Output
 Recommended Actions
 recommendation of what should be done to improve
the value of the solution within the enterprise.

26. G&T-Stakeholders-Techniques
• Business Objectives
• Current State Description
• Solution Scope
• Data Mining
• Decision Analysis
• Financial Analysis
• Focus Groups
• Organizational Modelling
• Prioritization
• Process Analysis
• Risk Analysis and Management
• Survey or Questionnaire
• Customer
• Domain SME
• End User
• Regulator
• Sponsor
Guideline & Tools
Stakeholders
Techniques

27. 感謝您的參與