24
軟體專案風險管理 Andy Liu 劉安瑋 思辨顧問股份有限公司 1

Software Project Risk Management

Embed Size (px)

DESCRIPTION

軟體開發工作是生產線還是電影工作室?軟體專案管理是工程或經濟學?如何將風險管理變成組織文化?要克服軟體專案成功比例偏低問題,必須著重軟體開發以人為核心的特性,不然會重蹈覆轍。

Citation preview

Page 1: Software Project Risk Management

軟體專案風險管理�Andy Liu 劉安瑋 思辨顧問股份有限公司�

1

Page 2: Software Project Risk Management

Agenda�!   軟體專案的特性

!   軟體專案風險管理原則

!   有效降低風險的模式

!   持續改善

!   小結

Page 3: Software Project Risk Management

您流程改善旅程中的夥伴�

教育訓練�

流程評鑑�

顧問諮詢�

工具導入�

Page 4: Software Project Risk Management

Andy Liu 劉安瑋�

CMMI�

Project Management�

Lead Appraiser�

Scrum Master�Instructor�

Consultant� Software Product Lines�

Software Development�

Page 5: Software Project Risk Management

軟體專案不像是蓋房子�

Scope� Scope�

Page 6: Software Project Risk Management

避免專案失敗的早期預警指標�

Page 7: Software Project Risk Management

前12項重要預警指標 - 1�

高階主管� 專案經理� 利害關係人� 主題專家�專案成員� 專案成員�

不支持� 能力不足� 缺少技能� 缺少承諾� 不參與� 過於忙碌�

PEOPLE-RELATED�Leon A. Kappelman, EARLY WARNING SIGNS OF IT PROJECT FAILURE: THE DOMINANT DOZEN�

Page 8: Software Project Risk Management

前12項重要預警指標 - 2�

需求文件�

不完整�

變更管理�

沒有流程�

時程規劃�

沒有成效�

利害關係人�

溝通不良�

資源調度�

過於理想�

商業效益分析�

不存在�

PROCESS-RELATED�Leon A. Kappelman, EARLY WARNING SIGNS OF IT PROJECT FAILURE: THE DOMINANT DOZEN�

Page 9: Software Project Risk Management

生產線 or 電影創作�

Page 10: Software Project Risk Management

軟體工程經濟學�

工作量�

團隊能力與經驗�

流程自動化� 軟體複雜度與規模�

流程成熟度�

經濟學:以最少的資源 創造最大的價值 �

Walker Royce, The Economics of Iterative Software Development �

Page 11: Software Project Risk Management

軟體專案風險管理 – 核心原則�

知情�不報�

射殺�信差�

缺乏�信任�

隱藏的議程�

都是他的問題�

我不要聽問題�

先射箭再畫靶�

開放的溝通�

溝通的障礙�溝通的障礙�溝通的障礙�

Dorofee, A. Continuous Risk Management Guidebook�

Page 12: Software Project Risk Management

軟體專案風險管理 – 制度化原則�

Integrated Management�

整合管理�

Teamwork�

團隊合作�

Continuous Process�

持續關注�

Ronald P. Higuera, Yacov Y. Haimes, Software Risk Management, Technical Report CMU/SEI-96-TR-012�

Page 13: Software Project Risk Management

軟體專案風險管理 – 定義風險原則�

前瞻性的觀點�

關照�全局�

共同的願景�

Ronald P. Higuera, Yacov Y. Haimes, Software Risk Management, Technical Report CMU/SEI-96-TR-012�

Page 14: Software Project Risk Management

團隊合作�

持續關注�

整合管理�

開放的溝通�

共同的願景� 前瞻的觀點�

關照全局�

Ronald P. Higuera, Yacov Y. Haimes, Software Risk Management, Technical Report CMU/SEI-96-TR-012�

Page 15: Software Project Risk Management

軟體生命週期模式類型�

可預測的 (Predictive)�

反覆與漸進的 (Iterative and Incremental)�

適應的 (Adaptive)�

較長的階段期間� 中等的階段期間� 較短的階段期間�

線性順序流程� 反覆式流程� 高度反覆式流程�

嚴格的需求控管� 需求控管具有彈性� 需求於專案進展中突現(Emerge)�

Waterfall� Unified Process� Scrum�

Highly Predictive�

Predictive� Iterative & Incremental�

Adaptive�Highly

Adaptive�

Exposure Draft, Software Extension to the PMBOK® Guide – Fifth Edition�

Page 16: Software Project Risk Management

專案時程�

開發進度�

程式完成比率

最初規劃的�完成日期�

驗收交付�

持續性整合�

開始整合�

補足設計或�需求缺失�

專案時程�

開發進度�

程式完成比率

最初規劃的�完成日期�

Waterfall�

Unified Process�

Walker Royce, The Economics of Iterative Software Development �

Page 17: Software Project Risk Management

專案風險度�

軟體生命週期�低�

高�

風險�出現期�

風險控管期�

規劃� 設計� 開發�

循環模式�風險曲線�

交付�

風險�排除期�

傳統模式�風險曲線�

風險模式�

Walker Royce, The Economics of Iterative Software Development �

Page 18: Software Project Risk Management

適應式生命週期�

Risk�

Risk�

Risk�

Build�

Test�

Demo�

Refine�

Design�

Frequent Iterations�

Increment�

Working Software�

Iteration Backlog�

Feature Backlog�

Product Vision�

Product Planning�

Iteration Planning� Demo &

Review�

� Yesterday�

Today�

Risks�

Impediments�

Daily standup meeting�

Exposure Draft, Software Extension to the PMBOK® Guide – Fifth Edition�

Page 19: Software Project Risk Management

適應式生命週期�

Developer�

Select Next Feature�

Specify Requirement

s�

Write Test Scenarios�

Refactor, add New Features

and Test�

Demo Capabilities�

Increment�

Exposure Draft, Software Extension to the PMBOK® Guide – Fifth Edition�

Page 20: Software Project Risk Management

效益�

任務類型� � �

管理� � �

環境� � �

需求� � �

設計� � �

實作� � �

整合與測試� � �

部署� � �

總計� � �

工作量分佈比較�

� �

成功� � �

挑戰的� � �

失敗� � �

總計� � �

專案結果分佈比較�The Standish Group CHAOS Database,

2002 ~ 2010�

Walker Royce, The Economics of Iterative Software Development �

Page 21: Software Project Risk Management

挑戰�

組織�

技術�

人員�

Page 22: Software Project Risk Management

持續改善的框架�ML/ Category

Project Management

Process Management

Engineering Support

5 Organizational Performance Management (OPM)

Causal Analysis and Resolution (CAR)

4 Quantitative Project Management (QPM)

Organizational Process Performance (OPP)

3

Integrated Project Management (IPM) Risk Management (RSKM)

Organizational Process Definition (OPD) Organizational Process Focus (OPF) Organizational Training (OT)

Requirements Development (RD) Technical Solution (TS) Product Integration (PI) Verification (VER) Validation (VAL)

Decision Analysis and Resolution (DAR)

2

Requirements Management (REQM) Project Planning (PP) Project Monitoring and Control (PMC) Supplier Agreement Management (SAM)

Configuration Management (CM) Process and Product Quality Assurance (PPQA) Measurement and Analysis (MA)

Page 23: Software Project Risk Management

我們的作法還可以更好嗎?�

評鑑�

��

��

��

�����

Page 24: Software Project Risk Management

小結�!   管理軟體專案的風險,人是核心

!   以明確的開發成果為中心,促進利害關係人溝通

!   持續改善流程,透過流程合理化降低專案風險