BABOK v3 線上讀書會 CH5 20150528 CH5 需求生命週期管理 時間 20150528(四) pm8:00 工具 YY語音(yy.com/yy7) 頻道 商業分析(76563901)

1. Business Analysis
需求生命週期管理
Moris, CBAP, PMP, PMI-PBA
2015.05.28
商業分析知識體系 (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. 5. 需求生命週期管理
 Trace Requirements
 Maintain Requirements
 Prioritize Requirements
 Assess Requirements Changes
 Approve Requirements

4. 2.0 與 V3 的差異
BABOK 2.0 BABOK V3
4 Requirements Management
and Communication
5 Requirements Life Cycle
Management
4.1 Manage Solution Scope and
Requirements
5.1 Trace Requirements
5.5 Approve Requirements
4.2 Manage Requirements
Traceability
5.1 Trace Requirements
5.4 Assess Requirements Changes
4.3 Maintain Requirements for
Reuse
5.2 Maintain Requirements
4.4 Prepare Requirements
Package
4.4 Communicate BA Information
4.5 Communicate Requirements 4.4 Communicate BA Information
5.3 Prioritize Requirements
n/a 5.5 Approve Requirements

5. 核心概念模型
Core Concept During E&C, business analysts...
Change manage how proposed changes to requirements and designs
are evaluated during an initiative.
Need trace, prioritize and maintain requirements to ensure that the
need is met.
Solution trace requirements and designs to solution components to
ensure that the solution satisfies the need.
Stakeholder work closely with key stakeholders to maintain understanding,
agreement, and approval of requirements and designs.
Value maintain requirements for reuse to extend value beyond the
current initiative.
Context analyze the context to support tracing and prioritization
activities.

6. E&C 投入產出
Input Requirements
Designs
Proposed Change
7.2 Requirements(verified)
Tasks 5.1 Trace Requirements
5.2 Maintain Requirements
5.3 Prioritize Requirements
5.4 Assess Requirements Changes
5.5 Approve Requirements
Output 5.1 Requirements (traced)
5.1 Designs (traced)
5.2 Requirements (maintained)
5.2 Designs (maintained)
5.3 Requirements (prioritized)
5.3 Designs (prioritized)
5.4 Requirements Change
Assessment
5.4 Designs Change Assessment
5.5 Requirements (approved)
5.5 Designs (approved)

7. 5.1 追蹤需求
 Purpose
 to ensure that requirements and designs at different levels are
aligned to one another, and to manage the effects of change to
one level on related requirements.
 Traceability enables
 faster and simpler impact analysis
 more reliable discovery of inconsistencies and gaps in
requirements
 deeper insights into the scope and complexity of a change
 reliable assessment of which requirements have been
addressed and which have not.

8. Input-Element-Output
• Requirements
• Designs
.1 Level of Formality
.2 Relationships
.3 Traceability Repository
• Requirements (traced)
• Designs (traced)
Inputs
Elements
Outputs

9. Outputs
 Requirements (traced)
 have clearly defined relationships to other
requirements, solution components, or releases,
phases, or iterations, within a solution scope, such
that coverage and the effects of change are clearly
identifiable.
 Designs (traced)
 clearly defined relationships to other requirements,
solution components, or releases, phases, or
iterations, within a solution scope, such that coverage
and the effects of change are clearly identifiable.

10. G&T-Stakeholders-Techniques
• Domain Knowledge
• Information Management Approach
• Legal/Regulatory Information
• Requirements Management Tools/
Repository
• Business Rules Analysis
• Functional Decomposition
• Process Modelling
• Scope Modelling
• Customers
• Domain SME
• End User
• Implementation SME
• Operational Support
• Project Manager
• Sponsor
• Suppliers
• Tester
Guideline & Tools
Stakeholders
Techniques

11. 5.2 維護需求
 Purpose
 to retain requirement accuracy and consistency
throughout and beyond the change during the entire
requirements life cycle, and to support reuse of
requirements in other solutions.
 Requirements should be
 consistently represented
 reviewed and approved for maintenance using a
standardized process that defines proper access
rights and ensures quality
 easily accessible and understandable

12. Input-Element-Output
• Requirements
• Designs
.1 Maintain Requirements
.2 Maintain Attributes
.3 Reusing Requirements
• Requirements (Maintained)
• Designs (maintained)
Inputs
Elements
Outputs

13. Output
 Requirements (maintained)
 defined once and available for long-term usage by the
organization.
 may become organizational process assets or be
used in future initiatives.
 Designs (maintained)
 may be reusable once defined. For example, as a
self-contained component that can be made available
for possible future use.

14. G&T-Stakeholders-Techniques
• Information Management Approach
• Business Rules Analysis
• Data Flow Diagrams
• Data Modelling
• Document Analysis
• Functional Decomposition
• Process Modelling
• Use Cases and Scenarios
• User Stories
• Domain SME
• Implementation SME
• Operational Support
• Regulator
• Tester
Guideline & Tools
Stakeholders
Techniques

15. 5.3 排序需求
 Purpose
 to rank requirements in the order of relative
importance.
 Prioritization
 the act of ranking requirements to determine their
relative importance to stakeholders.
 Inter-dependencies between requirements are
identified and may be used as the basis for
prioritization.

16. Input-Element-Output
• Requirements
• Designs
.1 Basis for Prioritization
.2 Challenges of Prioritization
.3 Continual Prioritization
• Requirements (prioritized)
• Designs (prioritized)
Inputs
Elements
Outputs

17. Output
 Requirements (prioritized)
 prioritized or ranked requirements are available for
additional work, ensuring that the highest valued
requirements are addressed first.
 Designs (prioritized)
 prioritized or ranked designs are available for
additional work, ensuring that the highest valued
designs are addressed first.

18. G&T-Stakeholders-Techniques
• Business Constraints
• Change Strategy
• Domain Knowledge
• Governance Approach
• Requirements Architecture
• Requirement Management Tools/
Repository
• Solution Scope
• Backlog Management
• Business Cases
• Decision Analysis
• Estimation
• Financial Analysis
• Interviews
• Item Tracking
• Prioritization
• Risk Analysis and Management
• Workshops
• Customer
• End User
• Implementation SME
• Project Manager
• Regulator
• Sponsor
Guideline & Tools
Stakeholders
Techniques

19. 5.4 評估需求變更
 Purpose
 to evaluate the implications of proposed changes to
requirements and designs.
 Assessing changes should consider
 aligns with the overall strategy
 affects value delivered to the business or stakeholder
groups
 impacts the time to deliver or the resources required
to deliver the value
 alters any risks, opportunities, or constraints
associated with the overall initiative

20. Input-Element-Output
• Proposed Change
• Requirements
• Designs
.1 Assessment Formality
.2 Impact Analysis
.3 Impact Resolution
• Requirements Change Assessment
• Designs Change Assessment
Inputs
Elements
Outputs

21. Output
 Requirements Change Assessment
 the recommendation to approve, modify, or deny a
proposed change to requirements.
 Designs Change Assessment
 the recommendation to approve, modify, or deny a
proposed change to one or more design components.

22. G&T-Stakeholders-Techniques
• Change Strategy
• Domain Knowledge
• Governance Approach
• Legal/Regulatory Information
• Requirements Architecture
• Solution Scope
• Business Cases
• Business Rules Analysis
• Decision Analysis
• Document Analysis
• Estimation
• Financial Analysis
• Interface Analysis
• Interviews
• Item Tracking
• Risk Analysis and Management
• Workshops
• Customer
• Domain SME
• End User
• Operational Support
• Project Manager
• Regulator
• Sponsor
• Tester
Guideline & Tools
Stakeholders
Techniques

23. 5.5 核准需求
 Purpose
 to obtain agreement on and approval of requirements
and designs for business analysis work to continue
and/or solution construction to proceed.
 Description
 Business analysts are responsible for ensuring clear
communication of requirements, designs, and other
business analysis information
 Approval of requirements and designs may be formal
or informal

24. Input-Element-Output
• Requirements (verified)
• Designs
.1 Understand Stakeholder Roles
.2 Conflict and Issue Management
.3 Gain Consensus
.4 Track and Communicate Approval
• Requirements (approved)
• Designs (approved)
Inputs
Elements
Outputs

25. Output
 Requirements (approved)
 requirements which are agreed to by stakeholders
and are ready for use in subsequent business
analysis efforts.
 Designs (approved)
 designs which are agreed to by stakeholders and are
ready for use in subsequent business analysis or
solution development efforts.

26. G&T-Stakeholders-Techniques
• Change Strategy
• Governance Approach
• Legal/Regulatory Information
• Requirement Management Tools/
Repository
• Solution Scope
• Customer
• Domain SME
• End User
• Operational Support
• Project Manager
• Regulator
• Sponsor
• Tester
Guideline & Tools
Stakeholders
Techniques
• Acceptance and Evaluation Criteria
• Decision Analysis
• Item Tracking
• Reviews
• Workshops

27. 感謝您的參與