20. Projects and the SDLC
Product Scope
Requirements
Design
Test
Release
Plan
Monitor &
Control
Implement
Close
Build
PMI Project
Management Process Waterfall Development
Initiate
21. IIBA Business Analysis
and the BABOK
https://www.youtube.com/watch?v=We1VW8MDn_k&list=PLjF-BzEQNIVNMO3RM1zjPwCkNiNduKABv
22. Plan Do Check Act
Test
Release
Close
Build
Etc.
PMI Project
SIX Sigma
Rational
Etc.
Management Process Waterfall Development
23. Project Failures
There are many reasons why projects fail.
Poor strategic
alignment
Lack of handover
(people change management)
Long time to
delivery
Poor or wrong
requirements
Poor risk
management
Poor
planning
Lack of sponsor
involvement
Ineffective
communication
Poorly defined
objectives/scope
Team skills
(esp. interpersonal skills)
Lack of formal pm
processes
Poor requirements management is consistently
in the top 3 reasons, regardless of the source
24. The cost of bad requirements
The following are a few key findings and data from the study:
1. Companies with poor business analysis capability will have three
times as many project failures as successes.
2. 68% of companies are more likely to have a marginal project or outright
failure than a success due to the way they approach business
analysis. In fact, 50% of this group’s projects were “runaways” which had
any 2 of:
• Taking over 180% of target time to deliver.
• Consuming in excess of 160% of estimated budget.
• Delivering under 70% of the target required functionality.
3. Companies pay a premium of as much as 60% on time and budget when
they use poor requirements practices on their projects.
4. Over 41% of the IT development budget for software, staff and external
professional services will be consumed by poor requirements at the
average company using average analysts versus the optimal organization.
5. The vast majority of projects surveyed did not utilize sufficient
business analysis skill to consistently bring projects in on time and
budget. The level of competency required is higher than that employed
within projects for 70% of the companies surveyed.
25. Swim lanes
Actor 4 Actor 3 Actor 2 Actor 1
Verb/noun
Binary
decisions
Activity level
participants
Boundaries
Hand-over
Begin and end
in same lane
84. 風險-報酬泡泡圖
84
泡泡圖形式X軸Y軸企業使用比例
風險與報酬回收報酬方案成功率44.4%
新穎度科技新穎度市場新穎度11.1%
難度與吸引力科技可行性市場吸引力11.1%
Auto
Seal
Top
Floor
Grade A
Sealant
U.V. Seal
D-50
Bread and Butter
$10 M 8 6 4 2 0
First
Coat
T-400
SPL
Edge
Coat
Solvent 1
White Elephants
TP-40
Pearls
Deck
Coat
Top
Seal
Solvent
800
Top
Coat A
Oysters
Circle size = resources (annual)
Reward (NPV)
High
Low
90. 後續
異業合作
商業模式
設計
新產品開
發六大知
識領域
三年七萬,學習不斷
Face Book 社群
主題:
新產品開發/ 專案管理/ 行銷策畫
目的:
資訊分享/ 異業合作
91. Project
Impact
Portfolio Screen /
Investment
Commitment
Criteria
Deliverables Proceed To
Gate 3
Stage-Gate Framework
Facilitation
by Process
Manager
Research & Technology
Incremental / Development & Enhancements
NPD Stage-Gate Framework
Proceed
Champion
CONCEPT
FEASIBILITY
ASSESSMENT
Risk Profile
Criteria
Gate 1 Stage 1
Commercialization
Feasibility Criteria
Deliverables Proceed
Gate 2
Terminate Terminate
BUSINESS CASE
ANALYSIS
Basis for
decision
Post-
Mortem
Post-
Mortem
Terminate
Basis for
decision
Post-
Mortem
Stage 2
Basis for
decision
Full
Development
Organizational
Learning
--------------------
Cont-i-nuous
Improvement
TEAM
FORMATION
/PROJECT
RISK REVIEW
Stage 0
BMT BMT BMT
SPT
Cross Functional
Team
Selected
New Concept
Recycle Recycle Recycle
Cross Functional
Team
Cross Functional
Team
May be completed in Front end
Terminate