项目管理计划模板(英文)

1、<Project Name> Project Management PlanVersion <x.x>Note: The following template is provided for use in Xavor projects.Text enclosed in squarebrackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the d

2、ocument.Revisi on HistoryFor every revisio n of this docume nt, provide the revisio n history that should in elude the date of revisio n, versi on n umber, descripti on of the cha nges in the docume nt, and author of the docume nt for that particular versi on.DateVersio nDescripti onAuthor<dd/mm/

3、yyyy><x.x><Details><Name>Distribution ListState the pers on s/teams/groups to whom this docume nt should be distributed whe never the docume nt is revised. Also state the n ame of their pare nt orga ni zati on.Docume nt Recipie ntOrga ni zati on<Role Name><Orga ni zati

4、on NameTable of Contents1. Introduction51.1 Purpose51.2 Scope51.3 Definitions, Acronyms and Abbreviations51.4 References51.5 Overview52. Project Overview62.1 Project Name, Code and Leader62.2 Project Purpose, Scope and Objectives62.3 Assumptions and Constraints62.3.1 Critical Assumptions and Constra

5、ints62.3.2 Non-Critical Assumptions and Constraints62.4 Project Milestones62.5 Project Deliverables62.6 Tailoring Guidelines62.7 Software Development Life Cycle63. Project Organization73.1 Organizational Structure73.2 External Interfaces93.3 Roles and Responsibilities93.3.1 <Organizational Unit N

6、ame>94. Management Process104.1 Work Breakdown Structure (WBS)104.2 Project Estimates104.2.1 Estimation Technique104.2.2 Size104.2.3 Effort104.3 Project Schedule104.3.1 Pre-Development Schedule104.3.2 Development Schedule104.4 Project Phases, Iterations and Releases104.4.1 Project Phases104.4.2 P

7、roject Iterations104.4.3 Releases104.5 Project Resourcing104.5.1 Staffing104.5.2 Resource Acquisition104.5.3 Training104.6 Project Budget104.7 Project Monitoring and Control114.7.1 Schedule Control114.7.2 Budget Control114.7.3 Measurements114.8 Risk Management Plan114.9 Project Closure115. Technical

8、 Process Plans125.1User Experience Design125.2Requirements Management125.3Analysis and Design125.4Development Plan125.5Peer Review Plan125.6Project Maintenance125.7Test Plan125.8Tools, Techniques and Standards125.8.1 Tools125.8.2 Techniques and Standards135.9Infrastructure135.10Facilities135.11Secur

9、ity Plan136.Supporting Process Plans136.1Configuration Management Plan136.2Documentation136.3Software Quality Assurance Plan136.4Intergroup Coordination136.5Communication146.6Problem Resolution146.7Subcontractor Management147.Additional plans158.Appendices15Project Man ageme nt Pla n1. In troducti o

10、nThe in troducti on of the Project Man ageme nt Pla nshould provide an overview of the en tire docume nt. Itshould include the purpose, scope, definitions, acronyms, abbreviations, references and overview of this Project Management Plan .1.1 PurposeSpecify the purpose of this Project Management Plan

11、.1.2 ScopeA brief description of the scope of this Project Management Plan ; what Project(s) it is associated with, and anything else that is affected or in flue need by this docume nt.1.3 Defin iti ons, Acronyms and Abbreviati onsThis subsection should provide the definitions of all terms, acronyms

12、, and abbreviations required to in terpret properly the Project Man ageme nt Pla n . This in formati on may be provided by refere nee to the project Glossary.1.4 Refere ncesThis subsecti on should provide a complete list of all docume nts referen ced elsewhere in the Project Management Plan . Each d

13、ocument should be identified by title, report number (if applicable), date, and publishi ng orga ni zati on. Specify the sources from which the refere nces can be obta in ed. This in formatio n may be provided by reference to an appe ndix or to ano ther docume nt. For the Project Man ageme nt Pla n,

14、 the list of refere need artifacts may in clude:?Risk Man ageme nt Plan? User In terfaces Guideli nes?Con figurati on Man ageme nt Pla n? Software Quality Assura nee Pla n, etc.Docume nt TitlePublish ing Orga ni zati on<Title><Orga ni zati on Name1.5 OverviewThis subsecti on should describe

15、 what the rest of the Project Man ageme nt Plan contains and expla in how the docume nt is orga ni zed.2. Project Overview2.1 Project Name, Code and LeaderSpecify the project n ame, project code and project leader (project man ager).Project Name: <Project NameProject Code: <xxx-xxx>Project

16、Leader: <Name>2.2 Project Purpose, Scope and ObjectivesA brief description of the purpose and objectives of this project, and a brief description of what deliverables the project is expected to deliver.2.3 Assumpti ons and Con stra intsA list of assumpti ons that this pla n is based on, and an

17、y con stra ints (e.g. budget, staff, equipme nt, schedule, etc.) that apply to the project. Make a dist in cti on betwee n critical and non-critical factors.2.3.1 Critical Assumpti ons and Con stra intsState the critical assumptions and constraints affecting the project.2.3.2 Non-Critical Assumpti o

18、ns and Con stra intsState the non-critical assumptions and constraints affecting the project.2.4 Project Milest on esTabular list of major milestones to be achieved during the project, with target dates.Milesto neTarget Achieveme nt Date<Milest one Name><dd/mm/yyyy>2.5 Project Deliverabl

19、esTabular list of the artifacts to be created during the project, with target delivery dates.DeliverablesTarget Delivery Date<Deliverable Name><dd/mm/yyyy>2.6 Tailori ng Guideli nesSpecify the tailori ng guideli nes for the project.2.7 Software Developme nt Life CycleSpecify the Software

20、 Developme nt Life Cycle that is to be followed in the project.3. Project Orga ni zati on3.1 Orga ni zati onal StructureDescribe the orga ni zati onal structure of the project team, in clud ing man ageme nt and other review authorities. This should include identification of all project organizationa

21、l units and a description of their fun cti on and resp on sibility.A diagram of the orga ni zati onal structure should also be attached for furtherillustrati on.Examples of project orga ni zati onal un its are:?Project Impleme ntati on Committee?Project Steer ing Committee?Project Man ageme nt Team?

22、 Architecture Group? User Experie nee Desig n Team? Requireme nts Team?An alysis and Desig n Team? Impleme ntati on GroupDevelopme nt TeamDatabase Man ageme nt TeamTesti ng TeamInf rastructure TeamCon figurati on Man ageme nt TeamSoftware Quality Assura nee Team, etc.Orga ni zati onal Un itDescripti

23、 on<Orga ni zati onal Un it Name><Descripti on>3.2Exter nal In terfacesDescribe how the project in terfaces with exter nal groups.For each exter nal group, ide ntify theintern al/exter nal con tact n ames.ExternalOrga ni zati onExter nal RoleExter nal RoleHolderResp on sibility of Extern

24、al Role HolderIn ternal Con tactRole andPers on<Orga ni zati on Name><Role Name><Role Holder Name><Resp on sibility Details><Role Name， <Pers on Name3.3 Roles and Resp on sibilitiesSpecify the roles, resp on sibilities and role holders withi n each orga ni zati onal un

25、it of the project.3.3.1 <Orga nizatio nal Unit NameRoleResp on sibilityRole Holder<Role Name><Resp on sibility Detail><Role Holder Name>4. Management Process4.1 Work Breakdown Structure (WBS)List the activities necessary for completing the project.4.2 Project Estimates4.2.1 Esti

26、mation TechniqueSpecify the estimation method and the reason for its choice.Provide the estimated cost as well as thebasis for those estimates, and the points/circumstances in the project when re-estimation will occur.4.2.2 SizeState the size of each activity as calculated according to the estimatio

27、n technique. Units of size may be in LOC, FP, etc.4.2.3 EffortSpecify the amount of effort required to perform each activity on the basis of the size estimation. Units may be man-hours, man-days, etc.4.3 Project ScheduleDiagrams/tables showing target dates for completion of iterations and phases, re

28、lease points, demos, and other milestones. Critical path must be specified. Usually enclosed by reference to MS Project file.4.3.1 Pre-Development ScheduleThis schedule will cater for project planning, requirements, analysis and design activities.4.3.2 Development ScheduleThis schedule will cater co

29、ding, testing and deployment activities.4.4 Project Phases, Iterations and Releases4.4.1 Project PhasesIdentify phases and major milestones with their achievement criteria.4.4.2 Project IterationsSpecify the number of iterations and list the objectives to be accomplished for each of the iterations.4

30、.4.3 ReleasesBrief descriptions of each software release, whether demo, beta, etc.4.5 Project Resourcing4.5.1 StaffingIdentify here the numbers and type of staff required (including and special skills or experience), scheduled by project phase or iteration. State what resources are critical.4.5.2 Re

31、source AcquisitionDescribe how you will approach finding and acquiring the staff needed for the project.4.5.3 TrainingList any special training project team members will require, with target dates for when this training should be completed.4.6 Project BudgetAllocation of costs against the WBS and th

32、e project phases.4.7 Project Monitoring and Control4.7.1 Schedule ControlDescribes the approach to be taken to monitor progress against the planned schedule and how to take corrective action when required.4.7.2 Budget ControlDescribes the approach to be taken to monitor spending against the project

33、budget and how to take corrective action when required.4.7.3 MeasurementsDescribe the types of measurements to be taken, their frequency, and responsible workers/entities for this purpose.4.8 Risk Management PlanEnclosed by reference4.9 Project ClosureDescribe the activities for the orderly completi

34、on of the project, including staff reassignment, archiving of project materials, post-mortem debriefings and reports etc.5. Technical Process Plans5.1 User Experience DesignDescribe the approach that will be adopted with details of processes, procedures, and guidelines to be followed.5.2 Requirement

35、sDescribe the approach that will be adopted with details of processes, procedures, and guidelines to be followed.5.3 Analysis and DesignDescribe the approach that will be adopted with details of processes, procedures, and guidelines to be followed.5.4 Development PlanEnclosed by reference5.5 Peer Re

36、view PlanSpecify the work products to be peer reviewed, type of peer review, their frequency, etc.5.6 MaintenanceDescribe details of any software maintenance for the warranty period of the project.5.7 Test PlanEnclosed by reference5.8 Tools, Techniques and Standards5.8.1 Tools Project Managem

37、ent ToolsSpecify the project management tools that are to be used in the project and the reasons for their selection. Examples of areas to be covered are project planning, project scheduling, project monitoring, status reporting, measurements, etc. Examples of these tools are MS Project, etc.

38、 Requirements Management ToolsSpecify the requirements management tools that are to be used in the project and the reasons for their selection. Examples of areas to be covered are requirements gathering, requirement issue resolution, requirement change management, measurements, etc. Examples of thes

39、e tools are Rational Requisite Pro, EINS, etc. System Analysis & Design ToolsSpecify the system analysis and design tools that are to be used in the project and the reasons for their selection. Examples of tools in this area are Visio, Rational Rose, Power Designer etc. LanguagesSp

40、ecify the languages that are to be used for software development in the project and the reasons for their selection. Examples of languages are HTML, Java, etc. User-Interface Development ToolsSpecify the tools that are to be used for UI development in the project and the reasons for their sel

41、ection. Examples of these tools can be Dreamweaver, Flash, etc. Database Management System SoftwareSpecify the database management system software that is to be used in the project and the reasons for their selection. Examples of these tools are Oracle, SQL Server, etc. Third Party Sof

42、twareSpecify any third party software that is to be used in the project and the reasons for their selection. Examples are Inktomi, Infranet, etc. Software Testing ToolsSpecify the software testing tools that are to be used in the project and the reasons for their selection. Examples of these

43、tools are WinRunner, LoadRunner, etc. Defect and Change Management ToolsSpecify the defect and change management tools that are to be used in the project and the reasons for their selection. Examples of these tools are ClearQuest, etc.0 Configuration Management ToolsSpecify the configu

44、ration management tools that are to be used in the project and the reasons for their selection. Examples of these tools are ClearCase, etc.1 Integrated Development EnvironmentSpecify the operating systems (platforms), web servers, application servers, development servers that are to be used in the project and the reasons for their selection.Examples of these tools are Sun Solaris,iPlanet, JBuilder, WebSphere, etc.5.8.2 Techniques and StandardsLists the documented project technical standards etc by reference.Examples may be:User-Interface GuidelinesProgramming GuidelinesTes