国内某着名公司的项目计划模版

1、Co. LtProduct versionConfidentiality产品版本level密级Project ID项目 IDTotalpages：共 28页XX Project PlanXX项目计划Prepared byDateyyyy-mm-dd拟制日期Reviewed byDateyyyy-mm-dd审核日期Approved byDateyyyy-mm-dd批准日期All rights reserved所有侵权必究Revision record修订记录DateRevisionDescription日期version描述修订版本2001-06-081.00initial初稿完成yyyy-mm

2、-dd1.01revised xxx修改 XXXyyyy-mm-dd1.02revised xxx修改 XXXAuthor作者name 作者名name 作者名name 作者名yyyy-mm-dd2.00revised xxx修改 XXXname 作者名Distribution LIST分发记录CopyHolder's Name & RoleIssue DateNo.持有者和角色分发日期1< RDPDT >yyyy-mm-dd2<Project Manager>yyyy-mm-dd3<Team members>yyyy-mm-dd4<Cu

3、stomer Representative>yyyy-mm-dd5<Others>yyyy-mm-ddCatalog 目录11 Introduction7简介.11.1Purpose目的77.21.2Scope 围.31.3References参考资料722Resource Summary 资源概述7833Project specific software Processes项目特定的软件过程44 Project Scope8项目围55 Deliverables8交付件.45.1 Customer Deliverables.55.2 Internal Deliverables

4、给客户的交付件部交付件88866 Organization and Responsibilities组织和职责1077 Estimated Size /Effort/schedule规模 / 工作量 / 进度的估计.67.1Estimated size估计的规模1010.77.2Estimated effort估计的工作量.87.3Estimated schedule 估计的进度111188 Project resource required项目所需资源.98.1Equipment Requirement设备需求1111.108.2Software tools软件工具.118.3Documen

5、ts 文档资料1212.128.4Customer Supplied Products需要客户提供的产品12.138.5Staffing人员需求.148.6Travel差旅121399 Project Schedule项目进度1310 10 Work Products工作产品11 11 Outsourced Task14外包任务.1511.1Subcontractor Profile子承包商资料14.1611.2Scope of the Outsourced task外包任务的围14.1711.3Milestone, Receivables & Deliverables里程碑、交付件1

6、412 12 Acceptance Criteria14验收标准1513 13 Quality Plan质量计划.1813.1Process Deviation过程偏差1515.1913.2Quality Goal质量目标.2013.3Plan to achieve the Quality Targets & Contingency达到质16量目标的计划及应急措施.113.3.1 Plan to achieve the Quality Targets达成质量目标的计划Contingency Plan应急计划17.2113.4Quality Assurance Act

7、ivities质量保证活动1718.2213.5Quality Control Activities质量控制活动14 14 Defect Prevention18缺陷预防.2314.1Defect Prevention Plan缺陷预防计划181915 15 Project Control项目控制.2415.1Project Reports项目报告19.2515.2Project Team Meeting项目组会议192016 16 Reuse Component Management重用构件管理.2616.1Existing components现有构件20.2716.2New compon

8、ents 新增构件202017 17 Configuration Management配置管理2018 18 Criteria for updating Project plan项目计划的修订2119 19 Assumptions假定2120 20Dependencies依赖关系2221 21 Issues问题2222 22 Customer involvement客户的参与2223 23 Risk Management 风险管理2224 24 Training培训Table of contents for the table表目录Table 1 XX表1 XX6Table of conten

9、ts for the figure图目录Figure 1 XX图 1XX7XX Project PlanXX项目计划Keywords 关键词：Abstract摘要：List of abbreviations缩略语清单：术语Definition定义AcronymSOWStatement Of Work工作任务书QAQuality Assurance Engineer QARATRisk Analysis Tool风险分析工具1Introduction简介1.1Purpose目的This section should state the purpose of the document. It co

10、uld also specify the intended audience.这部分要描述文档的目的，应该指明读者。1.2Scope围< 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项

11、目的计划完成的活动及其目标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.3References参考资料Doc IDName of th

12、e referred document参考资料编号参考资料名称1Resource Summary 资源概述Total Estimated Effort (in persondays)估计的总工作量Proposal Cost (if available)建议成本 ( 如果可以提出 )Proposed Project Start Date建议项目起始时间Development Completion Date开发结束时间Support Completion Date (ifapplicable)支持结束时间 ( 如果有 )Remarks, if any.说明1Project specific sof

13、tware Processes项目特定的软件过程The project shall conform to the Life Cycle Model and the Processes defined in the Process Handbook, < Provide the document ID and link to theProcess Handbook. >项目应该与生命周期模型和过程手册中定义的过程保持一致<提供文档 ID 并通过方式指向过程手册 >。2Project Scope项目围< The project's purpose, scope

14、, goals, and objectives. ><>项目的目的、围、目标。3Deliverables交付件3.1Customer Deliverables给客户的交付件< Listdown alltheexternaldeliverablesi.e.deliverablesto thecustomer as per the SOW/Allocated Requirements. ><>>罗列所有对外的交付件，如在工作任务书或分配需求中要求的交付件3.2Internal Deliverables部交付件< List down all th

15、e Internal Deliverables, i.e. deliverables which are notnecessarya deliveredto thecustomer, butproducedduring theprojectlife cycle ><>罗列所有的部交付件，如不必要给客户，但是在生命周期产生的。4Organization and Responsibilities组织和职责The table below identifies the roles and the name involved in the project.下表定义了项目组涉及到的角色和

16、名称。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 ev

17、ery Phase/Stage.在每个阶段结束时要检查下表的容。Thechangestotheteamorganizationin-betweenthephasewillbecommunicated to all concerned by the Project Manager through mail and later updated in the Project Plan at every phase.在阶段之间如果对项目组的结构进行了改变，由 PM通过 mail 通知所有相关人员，并在以后每个阶段的项目计划中更新。Sl.Role1NameReporting To2Backup reso

18、urceNo.角色向谁报告备份资源1Customer RepresentativeNA客户代表2 PDT R&D RepresentativePDT开发代表3 Project ManagerPM4 QA5 Metrics Coordinator度量协调员6Test Coordinator测试协调员7Risk Officer风险管理员8Project Consultant(s)项目顾问9Configuration Librarian配置管理员10Team Members项目组成员1 Including additional roles, if any.如果有其他角色，请包括来2 M en

19、tion the abbreviated Role only (e.g. PM etc.)以角色缩写名填写（如PMSl.Role1NameReporting To2Backup resourceNo.角色向谁报告备份资源11 Change Control Board<PDT R&DNANA变更控制委员会（）RepresentaCCBtive><PDT开发代表 ><PM><PM><QA>.12 Technical Reviewers, if available技术 reviewers13Affected groups相关小组1E

20、stimated Size /Effort/schedule规模 / 工作量 / 进度的估计1.1Estimated size估计的规模No. of estimationInitial estimationEstimated size in KLOC(NBNC)Re-estimation1Re-estimation2Re-estimation31.1Estimated effort估计的工作量TaskDistributioInitialRe-Re-Re-n(%)estimatiestimation1estimation2estimation3onPPL项目计划SRS需求规格STP系统测试计划U

21、M用户手册HLD概要设计ITP 集成测试计划LLD详细设计UTP单元测试计划CODE编码UT单元测试IT 集成测试ST系统测试TRG培训PM项目管理QA质量保证CM配置管理IGC组间协调TOTAL合计1.1Estimated schedule 估计的进度PhaseInitial estimationRe-estimation1Re-estimation2StartEnd DateStart DateEnd DateStart DateEnd DateDatePLANSRSHLDLLDCODINGUTITST1Project resource required项目所需资源1.1 Equipmen

22、t Requirement设备需求< Listdownthehardwarerequirementsforthe projecte.g.specifichardwareplatform,testequipment,whichis consideredas"criticalcomputerresource"etc.,罗列项目开发需要的硬件资源，如特殊的硬件平台、测试设备等。标准的办公硬件不必在这里列。 >Sl.DescriptionQty.StartEnd DateRemarksNo.描述数量Date结束日期说明起始日期123451.1 Software tool

23、s软件工具<List down the softwarerequiredfor theproject e.g.Linux,Clearcaselicense,etc.,列出项目需要的软件或软件license，例如 Linux 、 Clearcase license等。标准的办公软件不必在这里列。>Sl.Description 描述Qty.StartEnd DateRemarks说明No.数量Date结束日期起始日期1 < Mention the software details, includingversions etc.,软件描述，包括版本等 >23451.1Docu

24、ments 文档资料< List down the documents, books, and papers to be purchased for the project罗列项目需要的文档资料、书籍、论文等>Sl.DescriptionQty.StartEst. CostRemarksNo.描述数量date估计成本说明起始日期12341.1 Customer Supplied Products需要客户提供的产品< List down anyexistingcustomersuppliedproductsrequiredfor thedevelopment,integrati

25、onortestingoftheproject罗列开发、集成、测试中需要用户提供的产品 >Sl.Description 描述Qty.StartEnd dateRemarks说明No.数量date结束日期起始日期12341.1Staffing人员需求< List down the human resource requirement with required skills for the project罗列项目需要的人力资源及技能要求>Sl.DesignationNumberStartEnd dateRequiredRemarkNo.资源名称人数date结束日skill说明起

26、始日期技能要求期12341.1Travel差旅Sl.Travel DescriptionNumberExpectedRemarksNo.差旅描述次数Date说明预计时间1234<List down thesoftwarehardwarerequirementsfor the puteretc.>罗列项目开发需要的软硬件资源，如计算机等><Sl.NoDescriptionQty.StartEnd DateRemarks.描述数量Date结束日期说明起始日期123451Project Schedule项目进度Major milestones of

27、 the project is listed below:下表中：PhaseEstimate StartEstimate finish阶段datedate估计开始日期估计结束日期SRS Phaseyyyy-mm-ddyyyy-mm-dd软件需求阶段HLD Phaseyyyy-mm-ddyyyy-mm-dd概要设计阶段LLD Phaseyyyy-mm-ddyyyy-mm-dd详细设计阶段Coding Phaseyyyy-mm-ddyyyy-mm-dd编码阶段Unit Testingyyyy-mm-ddyyyy-mm-ddPhase单元测试阶段Integrationyyyy-mm-ddyyyy-m

28、m-ddTesting Phase集成测试阶段System Testingyyyy-mm-ddyyyy-mm-ddPhase系统测试阶段Release andyyyy-mm-ddyyyy-mm-ddAcceptance发布和验收Other, if anyyyyy-mm-ddyyyy-mm-dd其它将项目的主要里程碑列在Responsibility责任人Project ManagerPM<Team Member><项目组成员 ><Team member><项目组成员 ><Team member><项目组成员 ><Tea

29、m member><项目组成员 ><Team member><项目组成员 ><Team member><项目组成员 >Project ManagerPMProject ManagerPMRefer tothe Ganttchartfordetailedschedule.<Givereferenceto WBS(MicrosoftProjectPlan)here.> Projectmanagerwillupdate theGanttchart every week, and the activities will be

30、 tracked through Gantt chart.进度细节请参考Gantt图。<给 出的参考位置（MicrosoftProject）。WBSPlan应该每周更新Gantt图，通过它来跟踪活动。>PM1 Work Products 工作产品< List down the Approver and Authorizer for each work product. Note thatonly planning documents and management documents need to be authorized. ><列出每个工作产品的批准人和签发人

31、，注意只有计划文档和管理文档需要签发。 >Work ProductApprover (Name & Role)Authorizer (Name & Role)工作产品批准者（名字和角色）签发者（名字和角色）1Outsourced Task外包任务<Thisisapplicableifanypartoftheprojectisoutsourcedtosubcontractor ><本部分仅当项目中有外包时适用>1.1Subcontractor Profile子承包商资料Subcontractor's Name子承包商名Contact Pers

32、on联系人Address for communication通讯地址<Others><其它>1.1Scope of the Outsourced task外包任务的围<Specifythescopeoftheworkfromtheprojectoutsourcedtosubcontractor. This could be specified as Features, requirements, modules etc. ><指明项目外包给子承担商的工作容，可以采用特性、需求、模块等来说明>1.2Milestone, Receivables &a

33、mp; Deliverables里程碑、交付件<SpecifytheagreedMilestones,Receivables&Deliverablesbythesubcontractor ><指明协商后确定的子承包商的里程碑、交付件>MilestoneWork ProductPlannedPlannedDeliverables里程碑issued toStart datefinish dateto HuaweisubcontractorTechnologies计划开始日计划完成日分配给子承包期期给华为的交付商的工作产品件1Acceptance Criteria验收

34、标准The acceptancecriteriaforthecustomerarethat the software meets therequirements stated in the requirement specification document. The systemtestand theacceptancetestwilldemonstratethesoftware'sconformanceto the requirement specification.客户的验收标准就是软件应满足在需求规格文档中描述的需求。系统测试和验收测试将证实软件与需求规格保持了一致。<

35、Please mention here any specific acceptance criteria from the customer. The acceptance criteria are based on the need of the customer and so shallbedefinedbythecustomerwiththeassistanceoftheprojectwhereverrequired.ExamplescouldbeNatureofdeliveries,QualityObjectives,Testing criteria, Post acceptance

36、fault handling, Documentation etc., ><请在这里注明客户特殊的验收标准。验收标准是基于客户的需要，所以应由客户来制定，在需要的时候由项目组协助。交付件的属性如：质量目标，测试标准，验收结束后发现故障的处理方式，文档等。 >2Quality Plan质量计划2.1Process Deviation过程偏差< Provide the link of the Deviation Request Form > <提供到 PJM03F10-偏差申请表的 >。2.2Quality Goal质量目标Following metric

37、s will be collected as per the Metrics Procedure. These metrics will be tracked at least once per phase of the project.按照度量过程收集以下度量数据。这些度量数据将会在项目的各个阶段进行跟踪。SlMetricQuality Targets质量目标Remarks说明.度量No.序号Project3 项目Org. 组织GoalLCL上GoalLCLUCLUCL目标下限限目标下限上限1 Software Requirements Stability Index软件需求稳定指数 (%)

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

39、eview系统测试计划review 缺陷发现密度 ( 个/用例)） 3 These quality goals are also indicative of the priorities of the project. Lesser the variance more the priority.这些质量目标也表明了项目的优先级别，变化率较小者具有较高的优SlMetric.度量No.序号11UM Review用户文档 review 缺陷发现密度(个/ 页 )12HLD Review概要设计 review 缺陷发现密度(个/ 页 )13ITP Review集成测试计划review 缺陷发现密度 (

40、 个/用例)14 LLD Review详细设计 review 缺陷发现密度(个/ 页 )15UTP Review单元测试计划review 缺陷发现密度 ( 个/用例)16 CODE Review代码 review 缺陷发现密度(个/KLOC)17UT单元测试缺陷发现密度(个/KLOC)18IT集成测试缺陷发现密度(个/KLOC)19ST系统测试缺陷发现密度(个/KLOC)Quality Targets质量目标Remarks说明Project3 项目Org. 组织GoalLCL上GoalLCLUCLUCL目标下限限目标下限上限1.1Plan to achieve the Quality Targ

41、ets & Contingency达到质量目标的计划及应急措施1.1.1Plan to achieve the Quality Targets达成质量目标的计划< Please refer to the following two examples when plan to achieve the quality targets. ><制定达成质量目标的计划请参考下述两例：>< Static Code Analysis tools would be utilized during the coding phase.These wouldbeconfigur

42、edto ensurethatallprogrammingissuesareidentifiedevenbefore thecode reachesthecode review.Theentrycriteria for code review would be a no-error and no-warning source codefrom thosetools.This would help improvethecode qualityandhelpreviewers focus on design defects in the code rather than on the codingdefects (which would take more time )><在编码阶段使用静态的代码分析工具，配置工具以确保甚至在进行代码review 之前就能识别所有的编程问题。代码review的入口条件是使用工具分析时无错及无警告信息，如此将能改进代码的质量，并帮助reviewers 关注代码中的设计问题而不是关注简单的编码缺陷（这样将会花去更多的时间）。>< Test Coverage tools have been identifie