項目管理計劃書-太平洋

1、精選優(yōu)質文檔-傾情為你奉上Co. Lt有限公司Product version 產品版本Confidentiality level密級Project ID 項目IDTotal pages：共28頁XX Project PlanXX項目計劃 Prepared by 擬制Date日期yyyy-mm-ddReviewed by 審核Date日期yyyy-mm-ddApproved by批準Date日期yyyy-mm-ddRevision record 修訂記錄Date日期Revision version修訂版本修訂記錄的修訂版本請按1.00、1.01、1.02.進行填寫 Revised release

2、 should be logged as 1.00, 1.01, 1.02Description描述每次修訂的詳細內容，例如在哪個地方有過修訂，都要有明確說明。Describe detailed contents of each modification, e.g. Where was revised. 描述Author作者2001-06-081.00initial 初稿完成name 作者名yyyy-mm-dd1.01revised xxx 修改XXXname 作者名yyyy-mm-dd1.02revised xxx 修改XXXname 作者名yyyy-mm-dd2.00revised xxx

3、 修改XXXname 作者名Distribution LIST 分發(fā)記錄Copy No.Holder's Name & Role 持有者和角色Issue Date 分發(fā)日期1< RDPDT >yyyy-mm-dd2<Project Manager>yyyy-mm-dd3<Team members>yyyy-mm-dd4<Customer Representative>yyyy-mm-dd5<Others>yyyy-mm-ddCatalog目 錄1 1 Introduction 簡介7.1 1.1Purpose 目的7.

4、2 1.2Scope 范圍7.3 1.3References 參考資料72 2Resource Summary資源概述73 3Project specific software Processes 項目特定的軟件過程84 4 Project Scope項目范圍85 5 Deliverables交付件8.4 5.1 Customer Deliverables給客戶的交付件8.5 5.2 Internal Deliverables內部交付件86 6 Organization and Responsibilities組織和職責87 7 Estimated Size /Effort/schedule規(guī)

5、模/工作量/進度的估計10.6 7.1Estimated size估計的規(guī)模10.7 7.2Estimated effort估計的工作量10.8 7.3Estimated schedule估計的進度118 8 Project resource required 項目所需資源11.9 8.1Equipment Requirement 設備需求11.10 8.2Software tools 軟件工具11.11 8.3Documents 文檔資料12.12 8.4Customer Supplied Products 需要客戶提供的產品12.13 8.5Staffing 人員需求12.14 8.6Tr

6、avel 差旅129 9 Project Schedule 項目進度1310 10 Work Products工作產品1311 11 Outsourced Task外包任務14.15 11.1 Subcontractor Profile子承包商資料14.16 11.2 Scope of the Outsourced task 外包任務的范圍14.17 11.3 Milestone, Receivables & Deliverables 里程碑、交付件1412 12 Acceptance Criteria驗收標準1413 13 Quality Plan 質量計劃15.18 13.1 Pr

7、ocess Deviation 過程偏差15.19 13.2 Quality Goal質量目標15.20 13.3 Plan to achieve the Quality Targets & Contingency達到質量目標的計劃及應急措施16.1 13.3.1 Plan to achieve the Quality Targets達成質量目標的計劃16.2 13.3.2Contingency Plan應急計劃17.21 13.4 Quality Assurance Activities 質量保證活動17.22 13.5 Quality Control Activities 質量控制

8、活動1814 14 Defect Prevention 缺陷預防 18.23 14.1 Defect Prevention Plan 缺陷預防計劃1815 15 Project Control 項目控制19.24 15.1 Project Reports 項目報告19.25 15.2 Project Team Meeting 項目組會議1916 16 Reuse Component Management 重用構件管理20.26 16.1 Existing components 現(xiàn)有構件20.27 16.2 New components 新增構件2017 17 Configuration Man

9、agement 配置管理2018 18 Criteria for updating Project plan 項目計劃的修訂2019 19 Assumptions 假定2120 20Dependencies 依賴關系2121 21 Issues問題2222 22 Customer involvement客戶的參與2223 23 Risk Management風險管理2224 24 Training 培訓22Table of contents for the table表目錄Table 1 XX 表1 XX6Table of contents for the figure圖目錄Figure 1

10、XX 圖 1 XX7XX Project PlanXX項目計劃 Keywords 關鍵詞：Abstract 摘 要：List of abbreviations 縮略語清單：Acronym術語Definition定義SOWStatement Of Work 工作任務書QAQuality Assurance Engineer QARATRisk Analysis Tool風險分析工具1 Introduction 簡介1.1 Purpose 目的This section should state the purpose of the document. It could also specify t

11、he intended audience. 這部分要描述文檔的目的，應該指明讀者。1.2 Scope 范圍< Describe the scope of the this Project Plan . Identify the various items this document addresses. ><描述項目計劃的范圍，明確文檔涉及的各項內容>< This document addresses本文檔解決以下問題：The project planning activities to be done and its objective項目的計劃完成的活動及其目

12、標The quality plan adopted for the project項目采用的質量計劃Deliverables of the project項目的交付件Roles and responsibilities of people involved所有相關的角色和職責Schedule of the project項目進度Configuration Management for the project項目的配置管理Risk Management for the project項目的風險管理>1.3 References 參考資料Doc ID參考資料編號Name of the ref

13、erred document 參考資料名稱1 Resource Summary資源概述Total Estimated Effort (in person days)估計的總工作量 Proposal Cost (if available)建議成本(如果可以提出)Proposed Project Start Date建議項目起始時間Development Completion Date開發(fā)結束時間Support Completion Date (if applicable)支持結束時間(如果有)Remarks, if any.說明1 Project specific software Proces

14、ses 項目特定的軟件過程The project shall conform to the Life Cycle Model and the Processes defined in the Process Handbook, < Provide the document ID and link to the Process Handbook. >項目應該與生命周期模型和過程手冊中定義的過程保持一致<提供文檔ID并通過鏈接方式指向過程手冊>。2 Project Scope項目范圍< The project's purpose, scope, goals,

15、and objectives. ><項目的目的、范圍、目標。>3 Deliverables交付件3.1 Customer Deliverables給客戶的交付件< List down all the external deliverables i.e. deliverables to the customer as per the SOW/Allocated Requirements. > <羅列所有對外的交付件，如在工作任務書或分配需求中要求的交付件>>3.2 Internal Deliverables內部交付件< List down a

16、ll the Internal Deliverables, i.e. deliverables which are not necessary a delivered to the customer, but produced during the project life cycle ><羅列所有的內部交付件，如不必要給客戶，但是在生命周期內產生的。>4 Organization and Responsibilities組織和職責The table below identifies the roles and the name involved in the project

17、. 下表定義了項目組涉及到的角色和名稱。The Project Manager before the start of the review will identify reviewers for all documents and code. 在review之前PM需指定所有文檔和代碼的reviewers。For the responsibility of these roles, please refer to the Org. Manual of Huawei.這些角色的職責，請參考華為的組織手冊The below table shall be revisited at least at

18、 the end of every Phase/Stage.在每個階段結束時要檢查下表的內容。The changes to the team organization in-between the phase will be communicated to all concerned by the Project Manager through mail and later updated in the Project Plan at every phase.在階段之間如果對項目組的結構進行了改變，由PM通過mail通知所有相關人員，并在以后每個階段的項目計劃中更新。Sl. No.Role I

19、ncluding additional roles, if any. 如果有其他角色，請包括進角色Name姓名Reporting To來 Mention the abbreviated Role only (e.g. PM etc.) 以角色縮寫名填寫（如PM等向誰報告Backup resource備份資源1Customer Representative客戶代表NA2PDT R&D RepresentativePDT開發(fā)代表3Project ManagerPM4QA5Metrics Coordinator 度量協(xié)調員6Test Coordinator 測試協(xié)調員7Risk Office

20、r 風險管理員8Project Consultant(s)項目顧問9Configuration Librarian配置管理員10Team Members項目組成員11Change Control Board變更控制委員會（CCB）<PDT R&D Representative><PDT開發(fā)代表>NANA<PM><PM><QA>.12Technical Reviewers, if available技術reviewers13Affected groups相關小組1 Estimated Size /Effort/schedule規(guī)

21、模/工作量/進度的估計1.1 Estimated size估計的規(guī)模No. of estimationEstimated size in KLOC(NBNC)Initial estimationRe-estimation1Re-estimation2Re-estimation31.1 Estimated effort估計的工作量 TaskDistribution(%)Initial estimationRe-estimation1Re-estimation2Re-estimation3PPL項目計劃SRS需求規(guī)格STP系統(tǒng)測試計劃UM用戶手冊HLD概要設計ITP集成測試計劃LLD詳細設計UTP

22、單元測試計劃CODE編碼UT單元測試IT集成測試ST系統(tǒng)測試TRG培訓PM項目管理QA質量保證CM配置管理IGC組間協(xié)調TOTAL合計1.1 Estimated schedule估計的進度 PhaseInitial estimationRe-estimation1Re-estimation2Re-estimation3Start DateEnd DateStart DateEnd DateStart DateEnd DateStart DateEnd DatePLANSRSHLDLLDCODINGUTITST1 Project resource required 項目所需資源1.1 Equip

23、ment Requirement 設備需求< List down the hardware requirements for the project e.g. specific hardware platform, test equipment, which is considered as "critical computer resource" etc., 羅列項目開發(fā)需要的硬件資源，如特殊的硬件平臺、測試設備等。標準的辦公硬件不必在這里列。>Sl.No.Description描述Qty.數(shù)量Start Date起始日期End Date結束日期Remarks

24、說明123451.1 Software tools 軟件工具< List down the software required for the project e.g. Linux, Clearcase license, etc., 列出項目需要的軟件或軟件license，例如Linux、Clearcase license等。標準的辦公軟件不必在這里列。>Sl. No.Description描述Qty.數(shù)量Start Date起始日期End Date結束日期Remarks說明1< Mention the software details, including versions

25、 etc., 軟件描述，包括版本等>23451.1 Documents 文檔資料< List down the documents, books, and papers to be purchased for the project羅列項目需要的文檔資料、書籍、論文等>Sl. No.Description描述Qty.數(shù)量Start date起始日期Est. Cost估計成本Remarks說明12341.1 Customer Supplied Products 需要客戶提供的產品< List down any existing customer supplied prod

26、ucts required for the development, integration or testing of the project羅列開發(fā)、集成、測試中需要用戶提供的產品> Sl. No.Description描述Qty.數(shù)量Start date起始日期End date結束日期Remarks說明12341.1 Staffing 人員需求< List down the human resource requirement with required skills for the project 羅列項目需要的人力資源及技能要求>Sl. No.Designation

27、資源名稱Number人數(shù)Start date起始日期End date結束日期Required skill技能要求Remark說明12341.1 Travel 差旅Sl.No.Travel Description差旅描述Number次數(shù)Expected Date預計時間Remarks說明1234< List down the software hardware requirements for the project e.g. computer etc. ><羅列項目開發(fā)需要的軟硬件資源，如計算機等>Sl.No.Description描述Qty.數(shù)量Start Date起

28、始日期End Date結束日期Remarks說明123451 Project Schedule 項目進度Major milestones of the project is listed below:將項目的主要里程碑列在下表中：Phase階段Estimate Start date 估計開始日期Estimate finish date估計結束日期Responsibility責任人 SRS Phase軟件需求階段yyyy-mm-ddyyyy-mm-ddProject ManagerPMHLD Phase概要設計階段yyyy-mm-ddyyyy-mm-dd<Team Member>&l

29、t;項目組成員>LLD Phase詳細設計階段yyyy-mm-ddyyyy-mm-dd<Team member><項目組成員>Coding Phase編碼階段yyyy-mm-ddyyyy-mm-dd<Team member><項目組成員>Unit Testing Phase單元測試階段yyyy-mm-ddyyyy-mm-dd<Team member><項目組成員>Integration Testing Phase集成測試階段yyyy-mm-ddyyyy-mm-dd<Team member><項目組成

30、員>System Testing Phase系統(tǒng)測試階段yyyy-mm-ddyyyy-mm-dd<Team member><項目組成員>Release and Acceptance發(fā)布和驗收yyyy-mm-ddyyyy-mm-ddProject ManagerPMOther, if any其它yyyy-mm-ddyyyy-mm-ddProject ManagerPMRefer to the Gantt chart for detailed schedule. < Give reference to WBS (Microsoft Project Plan) h

31、ere. > Project manager will update the Gantt chart every week, and the activities will be tracked through Gantt chart. 進度細節(jié)請參考Gantt圖。<給出WBS的參考位置（Microsoft Project Plan）>。PM應該每周更新Gantt圖，通過它來跟蹤活動。1 Work Products工作產品< List down the Approver and Authorizer for each work product. Note that on

32、ly planning documents and management documents need to be authorized. ><列出每個工作產品的批準人和簽發(fā)人，注意只有計劃文檔和管理文檔需要簽發(fā)。>Work Product工作產品Approver (Name & Role)批準者（名字和角色）Authorizer (Name & Role)簽發(fā)者（名字和角色）1 Outsourced Task外包任務< This is applicable if any part of the project is outsourced to subc

33、ontractor ><本部分僅當項目中有外包時適用>1.1 Subcontractor Profile子承包商資料Subcontractor's Name子承包商名Contact Person聯(lián)系人Address for communication通訊地址<Others><其它>1.1 Scope of the Outsourced task 外包任務的范圍< Specify the scope of the work from the project outsourced to subcontractor. This could be

34、 specified as Features, requirements, modules etc. ><指明項目外包給子承擔商的工作內容，可以采用特性、需求、模塊等來說明>1.2 Milestone, Receivables & Deliverables 里程碑、交付件< Specify the agreed Milestones, Receivables & Deliverables by the subcontractor ><指明協(xié)商后確定的子承包商的里程碑、交付件>Milestone里程碑Work Product issued

35、 to subcontractor分配給子承包商的工作產品Planned Start date計劃開始日期Planned finish date計劃完成日期Deliverables to Huawei Technologies給華為的交付件1 Acceptance Criteria驗收標準The acceptance criteria for the customer are that the software meets the requirements stated in the requirement specification document. The system test and

36、 the acceptance test will demonstrate the software's conformance to the requirement specification.客戶的驗收標準就是軟件應滿足在需求規(guī)格文檔中描述的需求。系統(tǒng)測試和驗收測試將證實軟件與需求規(guī)格保持了一致。< Please mention here any specific acceptance criteria from the customer. The acceptance criteria are based on the need of the customer and so

37、 shall be defined by the customer with the assistance of the project wherever required. Examples could be Nature of deliveries, Quality Objectives, Testing criteria, Post acceptance fault handling, Documentation etc., ><請在這里注明客戶特殊的驗收標準。驗收標準是基于客戶的需要，所以應由客戶來制定，在需要的時候由項目組協(xié)助。交付件的屬性如：質量目標，測試標準，驗收結束

38、后發(fā)現(xiàn)故障的處理方式，文檔等。>2 Quality Plan 質量計劃2.1 Process Deviation 過程偏差< Provide the link of the Deviation Request Form ><提供到PJM03F10-偏差申請表的鏈接>。2.2 Quality Goal質量目標Following metrics will be collected as per the Metrics Procedure. These metrics will be tracked at least once per phase of the proj

39、ect.按照度量過程收集以下度量數(shù)據(jù)。這些度量數(shù)據(jù)將會在項目的各個階段進行跟蹤。Sl. No.序號Metric度量Quality Targets質量目標Remarks說明Project） These quality goals are also indicative of the priorities of the project. Lesser the variance more the priority. 這些質量目標也表明了項目的優(yōu)先級別，變化率較小者具有較高的優(yōu)先項目Org.組織Goal目標LCL 下限UCL上限Goal目標LCL下限UCL上限1Software Requirement

40、s Stability Index 軟件需求穩(wěn)定指數(shù) (%)2Duration Variance持續(xù)時間偏差 (%)3Schedule Slippage進度偏移 (%)4Effort Variance工作量偏差 (%)5Size Variance規(guī)模偏差 (%)6Defect Detected Density發(fā)布前缺陷發(fā)現(xiàn)密度 (個/KLOC)7Residual Defect Density遺留缺陷密度 (個/KLOC)8Productivity 生產率 (LOC /人天)Activity Wise Defect Detection Density 活動缺陷發(fā)現(xiàn)密度9SRS Review需求規(guī)

41、格review缺陷發(fā)現(xiàn)密度 (個/頁)10STP Review系統(tǒng)測試計劃review缺陷發(fā)現(xiàn)密度 (個/用例)11UM Review用戶文檔review缺陷發(fā)現(xiàn)密度 (個/頁)12HLD Review 概要設計review缺陷發(fā)現(xiàn)密度 (個/頁)13ITP Review集成測試計劃review缺陷發(fā)現(xiàn)密度 (個/用例)14LLD Review 詳細設計review缺陷發(fā)現(xiàn)密度 (個/頁)15UTP Review單元測試計劃review缺陷發(fā)現(xiàn)密度 (個/用例)16CODE Review代碼review缺陷發(fā)現(xiàn)密度 (個/KLOC)17UT單元測試缺陷發(fā)現(xiàn)密度 (個/KLOC)18IT集成測試

42、缺陷發(fā)現(xiàn)密度 (個/KLOC)19ST系統(tǒng)測試缺陷發(fā)現(xiàn)密度 (個/KLOC)1.1 Plan to achieve the Quality Targets & Contingency達到質量目標的計劃及應急措施1.1.1 Plan to achieve the Quality Targets達成質量目標的計劃< Please refer to the following two examples when plan to achieve the quality targets. ><制定達成質量目標的計劃請參考下述兩例：>< Static Code Ana

43、lysis tools would be utilized during the coding phase. These would be configured to ensure that all programming issues are identified even before the code reaches the code review. The entry criteria for code review would be a no-error and no-warning source code from those tools. This would help impr

44、ove the code quality and help reviewers focus on design defects in the code rather than on the coding defects (which would take more time )><在編碼階段使用靜態(tài)的代碼分析工具，配置工具以確保甚至在進行代碼review之前就能識別所有的編程問題。代碼review的入口條件是使用工具分析時無錯及無警告信息，如此將能改進代碼的質量，并幫助reviewers關注代碼中的設計問題而不是關注簡單的編碼缺陷（這樣將會花去更多的時間）。>< Tes

45、t Coverage tools have been identified to ensure that desired code coverage levels are monitored throughout the coding unit testing and subsequent phases. ><指明應使用的測試覆蓋率工具，以確保在整個編碼及單元測試階段及后續(xù)階段中，期望達到的代碼覆蓋率得到了監(jiān)控。>1.1.2 Contingency Plan應急計劃< Please take the following statements as example whe

46、n make contingency plan. If the said quality goals are not met, then we do the root cause analysis for the same. If the quality goal is related schedule variance then project manager will ask team members to work extra time to complete the activities on time. ><制定應急計劃時請參考下例：如果列出的質量目標沒有達到，我們將進行

47、針對性的根本原因分析，如果質量目標引起進度偏差，PM將要求項目組成員加班以及時完成各項任務。>1.2 Quality Assurance Activities級 For the schedule of these quality assurance activities, refer to the Gantt (WBS)質量保證活動的進度安排參考甘特圖（WBS質量保證活動Following Quality Assurance activities will be performed:應該執(zhí)行以下的質量保證活動：Activity 活動Responsibility 責任人Software R

48、equirement Specifications review軟件需求規(guī)格reviewPerson designated by Project Manager由PM指定的人員High Level Design Review概要設計reviewPerson designated by Project Manager由PM指定的人員Low Level Design Review詳細設計reviewPerson designated by Project Manager由PM指定的人員Code review代碼reviewPerson designated by Project Manager由P

49、M指定的人員Unit test plan and test cases review單元測試計劃和測試用例reviewPerson designated by Project Manager由PM指定的人員Integration test plan and test cases review集成測試計劃和測試用例reviewPerson designated by Project Manager由PM指定的人員System test plan and test cases review系統(tǒng)測試計劃和測試用例reviewPerson designated by Project Manager由P

50、M指定的人員(Unit/Integration/System) Test results review（單元/集成/系統(tǒng)）測試結果reviewPerson designated by Project Manager由PM指定的人員Backup and restoration Verification備份與恢復驗證QADeliverables audit交付件審計QABaseline audit基線審計QA1.1 Quality Control Activities）1.1Quality Control Activities For the schedule of these quality c

51、ontrol activities, refer to the Gantt (WBS)關于質量活動的進度，請參看甘特圖（WBS 質量控制活動Following Quality Control activities will be performed:應該執(zhí)行以下的質量控制活動：Activity 活動Responsibility 責任人Unit testing單元測試Team member designated by Project Manager由PM指定的小組成員Integration testing集成測試Team member designated by Project Manager由PM指定的小組成員System testing系統(tǒng)測試Team member designated by Project Manager由PM指定的小組成員1 Defect Prevention 缺陷預防 1.1 Defect Prevention Plan 缺陷預防計劃Sl NoCommon Defects公共缺陷Phase階段Preventive Action預防措施Mode (Review)方式（建議方式為：review）Responsibility責任人