Project Management o organising planning and scheduling software

計畫管理 (Project Management) o 對軟體計畫的組織、規劃及排程 (organising, planning and scheduling software projects)

主題 o o 管理活動(management activities) 計畫規劃(project planning) 計畫排程(project scheduling) 風險管理(risk management)

軟體計畫 (Software Projects) o 影響結果的因素 n n n n 程式大小(size) 成品繳交時間(delivery deadline) 預算及成本(budgets and costs) 應用領域(application domain) 實作技術(technology to be implemented) 系統限制(system constraints) 使用者需求(user requirements) 可用資源(available resources)

計畫管理注意事項 (Project Management Concerns)

計畫失敗原因 o 不切實際的截止日(an unrealistic deadline is established) o 客戶需求持續改變(changing customer requirements) o 低估 作量(underestimate of effort) o 可預期及不可預期風險 (predictable and/or unpredictable risks) o 技術性困難(technical difficulties) o 計畫參與者溝通上的誤解 (miscommunication among project staff) o 計畫管理失敗(failure in project management)

團隊組織 (Team Organization) o 中央集權式團隊組織(chief-programmer team organization) o 分散式團隊組織(decentralized team organization) o 混合式團隊組織(mixed-control team organization )

團隊結構 (Team Structure)

管理活動 (Management Activities) o o o 計畫撰寫(proposal writing) 計畫規劃及排程(project planning and scheduling) 計畫成本估算(project costing) 計畫監督及檢討(project monitoring and reviews) 人力挑選及評估(personnel selection and evaluation) o 報告撰寫及發表(report writing and presentations)

程計畫的類型 (Types of Project Plan)

計畫規劃行程 ( Project Planning Process )

把它寫下� Project Scope Estimates Risks Schedule Control strategy Software Project Plan

瞭解範疇… (To Understand Scope …) o瞭解客戶需求(understand the customers needs) o瞭解商業內涵(understand the business context) o瞭解計畫範疇(understand the project boundaries) o瞭解客戶動機(understand the customer’s motivation) o瞭解可能改變路徑(understand the likely paths for change) o瞭解…(understand that). . . o即便你能瞭解上述各項，也不能做任何保證�

計畫規劃結構 (Project Plan Structure) o o 簡介(introduction) 設計組織(project organisation) 風險分析(risk analysis) 硬體和軟體資源需求 (hardware and software resource requirements) o 作分 (work breakdown) o 程時程(project schedule) o 監控和報告機制(monitoring and reporting mechanisms)

需求行程的里程碑 (Milestones in the RE Process)

o 計畫參與人員(project staff)間因溝通 上的誤解(miscommunication)所造成的延 誤 o 在計畫管理(project management)上因錯 誤的認知導致雖計畫進度已落後(fall behind schedule)卻缺乏行動以改正問題 (action to correct the problem)

計畫排程行程 (Project Scheduling Process)

作期間與相依性 (Task Durations and Dependencies)

活動網路 (Activity Timeline)

活動時間表 (Activity Timeline)

人力分配 (Staff Allocation)

計畫風險 (Project Risks) What can go wrong? What is the likelihood? What will the damage be? What can we do about it?

軟體風險 (Software Risks)

風險管理模式 (Risk Management Paradigm) Control Track RISK Plan Analyze Identify

風險管理程序 (Risk Management Process)

風險識別 (Risk Identification) o o o 技術風險(technology risks) 人力風險(people risks) 組織風險(organisational risks) 需求風險(requirements risks) 評估風險(estimation risks)

風險和風險類型 (Risks and Risk Types)

產品規模的風險 (Risk due to Product Size) o 以LOC (Line of Code)或FP (Function Point) 估計產品規模的大小 o 以程式(programs)、檔案(files)及交易 (transactions)的數量估計產品規模大小 o 與之前產品之平均大小的百分比偏差 (percentage deviation in size of product from average for previous products)

商業衝擊的風險 (Risk due to Business Impact) o 該產品對公司盈收的影響 o 該產品對資深管理的能見度(visibility of this product by senior management) o 交付期限(delivery deadline)的合理性 o 將使用該產品的用戶數量 o 互通性的限制條件(interoperability constraints) o 終端用戶的複雜性(sophistication of end users)

o 需產生和交付給客戶之產品文件(product documentation)的量和質(amount and quality) o 政府的限制條件(governmental constraints) o 延遲交付的相關成本(cost) o 瑕疵產品(defect product)的相關成本(cost)

o 是否使用非傳統(unconventional)的軟體開發 方法? 如正規方法(formal methods)，人 智 慧方法(AI-based approaches)及類神經網路 (artificial neural networks)? o 有重要的效能限制條件嗎(significant performance constraints)?

風險分析 (Risk Analysis) o 評估每個風險的機率(probability)和嚴重性 (seriousness) o 機率可能是 n 非常低(very low) n 低(low) n 適度(moderate) n 高(high) n 非常高(very high)

o 風險的影響可能是 n 災難性(catastrophic) n 嚴重(serious) n 可容忍(tolerable) n 不重要(insignificant)

風險分析(I) (Risk Analysis)

風險分析(II) (Risk Analysis )

風險管理策略(I) (Risk Management Strategies)

風險管理策略(II) (Risk Management Strategies)

風險指標 (Risk Indicators)

參考資料 o Ian Sommerville, Software Engineering, 7 th ed. , Addison-Wesley, 2004.