项目管理计划书-模板_第1页
项目管理计划书-模板_第2页
项目管理计划书-模板_第3页
项目管理计划书-模板_第4页
项目管理计划书-模板_第5页
已阅读5页,还剩23页未读 继续免费阅读

下载本文档

版权说明:本文档由用户提供并上传,收益归属内容提供方,若内容存在侵权,请进行举报或认领

文档简介

1、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 should be lo

2、gged 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 修改XXXname 作者

3、名Distribution LIST 分发记录Copy No.Holder's Name & Role 持有者和角色Issue Date 分发日期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.2 1.2Scope 范围

4、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规模/工作量/进度的估计10

5、.6 7.1Estimated size估计的规模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.6Travel 差旅129 9

6、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 Process Deviati

7、on 过程偏差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 质量控制活动1814 14 Def

8、ect 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 现有构件20.27 16.2 New components 新增构件2017 17 Configuration Management 配置管理2

9、018 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 XX 图 1 XX7XX

10、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 the intended a

11、udience. 这部分要描述文档的目的,应该指明读者。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项目的计划完成的活动及其目标The quality

12、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 referred documen

13、t 参考资料名称1 Resource Summary资源概述Total Estimated Effort (in person days)估计的总工作量 Proposal Cost (if available)建议成本(如果可以提出)Proposed Project Start Date建议项目起始时间Development Completion Date开发结束时间Support Completion Date (if applicable)支持结束时间(如果有)Remarks, if any.说明1 Project specific software Processes 项目特定的软件过程

14、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, and objective

15、s. ><项目的目的、范围、目标。>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 all the Intern

16、al 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 the end of e

18、very 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 Including addi

19、tional roles, if any. 如果有其他角色,请包括进角色Name姓名Reporting To来 Mention the abbreviated Role only (e.g. PM etc.) 以角色缩写名填写(如PM等向谁报告Backup resource备份资源1Customer Representative客户代表NA2PDT R&D RepresentativePDT开发代表3Project ManagerPM4QA5Metrics Coordinator 度量协调员6Test Coordinator 测试协调员7Risk Officer 风险管理员8Proje

20、ct Consultant(s)项目顾问9Configuration Librarian配置管理员10Team Members项目组成员11Change Control Board变更控制委员会(CCB)<PDT R&D Representative><PDT开发代表>NANA<PM><PM><QA>.12Technical Reviewers, if available技术reviewers13Affected groups相关小组1 Estimated Size /Effort/schedule规模/工作量/进度的估计1.

21、1 Estimated size估计的规模No. of estimationEstimated size in KLOC(NBNC)Initial estimationRe-estimation1Re-estimation2Re-estimation31.1 Estimated effort估计的工作量 TaskDistribution(%)Initial estimationRe-estimation1Re-estimation2Re-estimation3PPL项目计划SRS需求规格STP系统测试计划UM用户手册HLD概要设计ITP集成测试计划LLD详细设计UTP单元测试计划CODE编码U

22、T单元测试IT集成测试ST系统测试TRG培训PM项目管理QA质量保证CM配置管理IGC组间协调TOTAL合计1.1 Estimated schedule估计的进度 PhaseInitial estimationRe-estimation1Re-estimation2Re-estimation3Start DateEnd DateStart DateEnd DateStart DateEnd DateStart DateEnd DatePLANSRSHLDLLDCODINGUTITST1 Project resource required 项目所需资源1.1 Equipment Requirem

23、ent 设备需求< List down the hardware requirements for the project e.g. specific hardware platform, test equipment, which is considered as "critical computer resource" etc., 罗列项目开发需要的硬件资源,如特殊的硬件平台、测试设备等。标准的办公硬件不必在这里列。>Sl.No.Description描述Qty.数量Start Date起始日期End Date结束日期Remarks说明123451.1 So

24、ftware tools 软件工具< List down the software required for the project e.g. Linux, Clearcase license, etc., 列出项目需要的软件或软件license,例如Linux、Clearcase license等。标准的办公软件不必在这里列。>Sl. No.Description描述Qty.数量Start Date起始日期End Date结束日期Remarks说明1< Mention the software details, including versions etc., 软件描述,包

25、括版本等>23451.1 Documents 文档资料< List down the documents, books, and papers to be purchased for the project罗列项目需要的文档资料、书籍、论文等>Sl. No.Description描述Qty.数量Start date起始日期Est. Cost估计成本Remarks说明12341.1 Customer Supplied Products 需要客户提供的产品< List down any existing customer supplied products required

26、 for the development, integration or testing of the project罗列开发、集成、测试中需要用户提供的产品> Sl. No.Description描述Qty.数量Start date起始日期End date结束日期Remarks说明12341.1 Staffing 人员需求< List down the human resource requirement with required skills for the project 罗列项目需要的人力资源及技能要求>Sl. No.Designation资源名称Number人数S

27、tart date起始日期End date结束日期Required skill技能要求Remark说明12341.1 Travel 差旅Sl.No.Travel Description差旅描述Number次数Expected Date预计时间Remarks说明1234< List down the software hardware requirements for the project e.g. computer etc. ><罗列项目开发需要的软硬件资源,如计算机等>Sl.No.Description描述Qty.数量Start Date起始日期End Date结束

28、日期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><项目组成员>LL

29、D 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><项目组成员>System T

30、esting Phase系统测试阶段yyyy-mm-ddyyyy-mm-dd<Team member><项目组成员>Release and Acceptance发布和验收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) here. > Pro

31、ject manager will update the Gantt chart every week, and the activities will be tracked through Gantt chart. 进度细节请参考Gantt图。<给出WBS的参考位置(Microsoft Project Plan)>。PM应该每周更新Gantt图,通过它来跟踪活动。1 Work Products工作产品< List down the Approver and Authorizer for each work product. Note that only planning d

32、ocuments and management documents need to be authorized. ><列出每个工作产品的批准人和签发人,注意只有计划文档和管理文档需要签发。>Work Product工作产品Approver (Name & Role)批准者(名字和角色)Authorizer (Name & Role)签发者(名字和角色)1 Outsourced Task外包任务< This is applicable if any part of the project is outsourced to subcontractor >

33、;<本部分仅当项目中有外包时适用>1.1 Subcontractor Profile子承包商资料Subcontractor's Name子承包商名Contact Person联系人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 specified as

34、 Features, requirements, modules etc. ><指明项目外包给子承担商的工作内容,可以采用特性、需求、模块等来说明>1.2 Milestone, Receivables & Deliverables 里程碑、交付件< Specify the agreed Milestones, Receivables & Deliverables by the subcontractor ><指明协商后确定的子承包商的里程碑、交付件>Milestone里程碑Work Product issued to subcontra

35、ctor分配给子承包商的工作产品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 the acceptan

36、ce test will demonstrate the software's conformance to the requirement specification.客户的验收标准就是软件应满足在需求规格文档中描述的需求。系统测试和验收测试将证实软件与需求规格保持了一致。< Please mention here any specific acceptance criteria from the customer. The acceptance criteria are based on the need of the customer and so shall be def

37、ined 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., ><请在这里注明客户特殊的验收标准。验收标准是基于客户的需要,所以应由客户来制定,在需要的时候由项目组协助。交付件的属性如:质量目标,测试标准,验收结束后发现故障的处理方式,文档

38、等。>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 project.按照度量过程收集以

39、下度量数据。这些度量数据将会在项目的各个阶段进行跟踪。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. 这些质量目标也表明了项目的优先级别,变化率较小者具有较高的优先项目Org.组织Goal目标LCL 下限UCL上限Goal目标LCL下限UCL上限1Software Requirements Stability I

40、ndex 软件需求稳定指数 (%)2Duration Variance持续时间偏差 (%)3Schedule Slippage进度偏移 (%)4Effort Variance工作量偏差 (%)5Size Variance规模偏差 (%)6Defect Detected Density发布前缺陷发现密度 (个/KLOC)7Residual Defect Density遗留缺陷密度 (个/KLOC)8Productivity 生产率 (LOC /人天)Activity Wise Defect Detection Density 活动缺陷发现密度9SRS Review需求规格review缺陷发现密度

41、 (个/页)10STP Review系统测试计划review缺陷发现密度 (个/用例)11UM Review用户文档review缺陷发现密度 (个/页)12HLD Review 概要设计review缺陷发现密度 (个/页)13ITP Review集成测试计划review缺陷发现密度 (个/用例)14LLD Review 详细设计review缺陷发现密度 (个/页)15UTP Review单元测试计划review缺陷发现密度 (个/用例)16CODE Review代码review缺陷发现密度 (个/KLOC)17UT单元测试缺陷发现密度 (个/KLOC)18IT集成测试缺陷发现密度 (个/KLO

42、C)19ST系统测试缺陷发现密度 (个/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 Analysis tools w

43、ould 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 improve the code

44、quality and help reviewers focus on design defects in the code rather than on the coding defects (which would take more time )><在编码阶段使用静态的代码分析工具,配置工具以确保甚至在进行代码review之前就能识别所有的编程问题。代码review的入口条件是使用工具分析时无错及无警告信息,如此将能改进代码的质量,并帮助reviewers关注代码中的设计问题而不是关注简单的编码缺陷(这样将会花去更多的时间)。>< Test Coverage to

45、ols have been identified to ensure that desired code coverage levels are monitored throughout the coding unit testing and subsequent phases. ><指明应使用的测试覆盖率工具,以确保在整个编码及单元测试阶段及后续阶段中,期望达到的代码覆盖率得到了监控。>1.1.2 Contingency Plan应急计划< Please take the following statements as example when make contin

46、gency 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:应该执行以下的质量保证活动:Activity 活动Responsibility 责任人Software Requirement Sp

48、ecifications review软件需求规格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由PM指定的人员Unit te

49、st 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系统测试计划和测试用例reviewPerson designated by Project Manager由PM指定的人员(Unit/I

50、ntegration/System) Test results review(单元/集成/系统)测试结果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 control activi

51、ties, refer to the Gantt (WBS)关于质量活动的进度,请参看甘特图(WBS 质量控制活动Following Quality Control activities will be performed:应该执行以下的质量控制活动:Activity 活动Responsibility 责任人Unit testing单元测试Team member designated by Project Manager由PM指定的小组成员Integration testing集成测试Team member designated by Project Manager由PM指定的小组成员System testing系统测试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责任人DP Da

温馨提示

  • 1. 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。图纸软件为CAD,CAXA,PROE,UG,SolidWorks等.压缩文件请下载最新的WinRAR软件解压。
  • 2. 本站的文档不包含任何第三方提供的附件图纸等,如果需要附件,请联系上传者。文件的所有权益归上传用户所有。
  • 3. 本站RAR压缩包中若带图纸,网页内容里面会有图纸预览,若没有图纸预览就没有图纸。
  • 4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
  • 5. 人人文库网仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对用户上传分享的文档内容本身不做任何修改或编辑,并不能对任何下载内容负责。
  • 6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
  • 7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

评论

0/150

提交评论