项目管理计划模板英文

1、<Project Name>错误！未指定书签。Version <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 document.Revisio

2、n HistoryFor every revision of this document, provide the revision history that should include the date of revision, version number, description of the changes in the document, and author of the document for that particular version.DateVersionDescriptionAuthor<dd/mm/yyyy><x.x><Details

3、><Name>Distribution ListState the persons/teams/groups to whom this document should be distributed whenever the document is revised. Also state the name of their parent organization.Document RecipientOrganization<Role Name><Organization Name>Table of Contents1.Introduction51.1Pu

4、rpose51.2Scope51.3Definitions, Acronyms and Abbreviations51.4References51.5Overview52.Project Overview62.1Project Name, Code and Leader62.2Project Purpose, Scope and Objectives62.3Assumptions and Constraints62.3.1Critical Assumptions and Constraints62.3.2Non-Critical Assumptions and Constraints62.4P

5、roject Milestones62.5Project Deliverables62.6Tailoring Guidelines62.7Software Development Life Cycle63.Project Organization73.1Organizational Structure73.2External Interfaces93.3Roles and Responsibilities93.3.1<Organizational Unit Name>94.Management Process104.1Work Breakdown Structure (WBS)10

6、4.2Project Estimates104.2.1Estimation Technique104.2.2Size104.2.3Effort104.3Project Schedule104.3.1Pre-Development Schedule104.3.2Development Schedule104.4Project Phases, Iterations and Releases104.4.1Project Phases104.4.2Project Iterations104.4.3Releases104.5Project Resourcing104.5.1Staffing104.5.2

7、Resource Acquisition104.5.3Training104.6Project Budget104.7Project Monitoring and Control114.7.1Schedule Control114.7.2Budget Control114.7.3Measurements114.8Risk Management Plan114.9Project Closure115.Technical Process Plans125.1User Experience Design125.2Requirements Management125.3Analysis and Des

8、ign125.4Development Plan125.5Peer Review Plan125.6Project Maintenance125.7Test Plan125.8Tools, Techniques and Standards125.8.1Tools125.8.2Techniques and Standards135.9Infrastructure135.10Facilities135.11Security Plan136.Supporting Process Plans136.1Configuration Management Plan136.2Documentation136.

9、3Software Quality Assurance Plan136.4Intergroup Coordination136.5Communication146.6Problem Resolution146.7Subcontractor Management147.Additional plans158.Appendices15错误！未指定书签。1. IntroductionThe introduction of the Project Management Plan should provide an overview of the entire document. It should i

10、nclude the purpose, scope, definitions, acronyms, abbreviations, references and overview of this Project Management Plan .1.1PurposeSpecify the purpose of thisProject Management Plan. 1.2ScopeA brief description of the scope of this Project Management Plan ; what Project(s) it is associated with, an

11、d anything else that is affected or influenced by this document.1.3Definitions, Acronyms and AbbreviationsThis subsection should provide the definitions of all terms, acronyms, and abbreviations required to interpret properly the Project Management Plan . This information may be provided by referenc

12、e to the project Glossary.1.4ReferencesThis subsection should provide a complete list of all documents referenced elsewhere in theProjectManagement Plan . Each document should be identified by title, report number (if applicable), date, andpublishing organization.Specify the sources from which the r

13、eferences can be obtained. This informationmay be provided by reference to an appendix or to another document.For the Project Management Plan,the list of referenced artifacts may include:Risk Management PlanUser Interfaces GuidelinesConfiguration Management PlanSoftware Quality Assurance Plan, etc.D

14、ocument TitlePublishing Organization<Title><Organization Name>1.5OverviewThis subsection should describe what the rest of the Project Management Plan contains and explain howthe document is organized.2. Project Overview2.1Project Name, Code and LeaderSpecify the project name, project cod

15、e and project leader (project manager).Project Name: <Project Name>Project Code: <xxx-xxx>Project Leader: <Name>2.2Project Purpose, Scope and ObjectivesA brief description of the purpose and objectives of this project, and a brief description of whatdeliverables the project is expe

16、cted to deliver.2.3Assumptions and ConstraintsA list of assumptions that this plan is based on, and any constraints (e.g. budget, staff, equipment,schedule, etc.) that apply to the project.Make a distinction between critical and non-critical factors.2.3.1Critical Assumptions and ConstraintsState the

17、 critical assumptions and constraints affecting the project.2.3.2Non-Critical Assumptions and ConstraintsState the non-critical assumptions and constraints affecting the project.2.4Project MilestonesTabular list of major milestones to be achieved during the project, with target dates.MilestoneTarget

18、 Achievement Date<Milestone Name><dd/mm/yyyy>2.5Project DeliverablesTabular list of the artifacts to be created during the project, with target delivery dates.DeliverablesTarget Delivery Date<Deliverable Name><dd/mm/yyyy>2.6Tailoring GuidelinesSpecify the tailoring guidelines

19、 for the project.2.7Software Development Life CycleSpecify the Software Development Life Cycle that is to be followed in the project.3. Project Organization3.1Organizational StructureDescribe the organizational structure of the project team, including management and other review authorities. This sh

20、ould include identification of all project organizational units and a description of their function and responsibility. A diagram of the organizational structure should also be attached for further illustration.Examples of project organizational units are:Project Implementation CommitteeProject Stee

21、ring CommitteeProject Management TeamArchitecture GroupUser Experience Design TeamRequirements TeamAnalysis and Design TeamImplementation GroupDevelopment TeamDatabase Management TeamTesting TeamInfrastructure TeamConfiguration Management TeamSoftware Quality Assurance Team, etc.Organizational UnitD

22、escription<Organizational Unit Name><Description>Project Team<Project Name>Version: <x.x>Date: <dd/mm/yyyy>ProjectProject ManagerManagementTeamProjectSoftware QualitySoftwareProjectArchitectureConfigurationImplementationAssurance TeamGroupTeamGroupSoftwareUser Experienc

23、eDevelopmentTeamTeamSystemArchitectureTeamDatabaseManagementTeamRequirementsTesting TeamTeamSystem Analysis& Design TeamInfrastructureTeam3.2External InterfacesDescribe how the project interfaces with external groups.For each external group, identify theinternal/external contact names.ExternalOr

24、ganizationExternal RoleExternal RoleHolderResponsibility ofExternal Role HolderInternal ContactRole andPerson<OrganizationName><Role Name><Role HolderName><Responsibility Details><Role Name>,<Person Name>3.3Roles and ResponsibilitiesSpecify the roles, responsibili

25、ties and role holders within each organizational unit of the project.<Organizational Unit Name>RoleResponsibilityRole Holder<Role Name><Responsibility Detail><Role Holder Name>4. Management Process4.1Work Breakdown Structure (WBS)List the activities necessary for completing t

26、he project.4.2Project EstimatesEstimation TechniqueSpecify the estimation method and the reason for its choice. Provide the estimated cost as well as the basis for those estimates, and the points/circumstances in the project when re-estimation will occur.SizeState the size of each activity as calcul

27、ated according to the estimation technique. Units of size may be in LOC, FP, etc.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.3Project ScheduleDiagrams/tables showing target dates for completion of i

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

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

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

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

32、d the project phases.4.7Project Monitoring and ControlSchedule ControlDescribes the approach to be taken to monitor progress against the planned schedule and how to take corrective action when required.Budget ControlDescribes the approach to be taken to monitor spending against the project budget an

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

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

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

36、ork products to be peer reviewed, type of peer review, their frequency, etc.5.6MaintenanceDescribe details of any software maintenance for the warranty period of the project.5.7Test PlanEnclosed by reference5.8Tools, Techniques and StandardsToolsProject Management ToolsSpecify the project management

37、 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.Specify the requirements management tools that

38、 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 these tools are Rational Requisite Pro, EINS, etc.Specify the system analysis an

39、d 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.LanguagesSpecify the languages that are to be used for software development in the project and the reasons for their selection. Examples

40、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 selection.Examples of these tools can be Dreamweaver, Flash, etc.Database Management System SoftwareSpecify the database management syste

41、m software that is to be used in the project and the reasons for their selection. Examples of these tools are Oracle, SQL Server, etc.Specify 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 ToolsSpeci

42、fy the software testing tools that are to be used in the project and the reasons for their selection.Examples of these 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 se

43、lection. Examples of these tools are ClearQuest, etc.Configuration Management ToolsSpecify the configuration management tools that are to be used in the project and the reasons for their selection. Examples of these tools are ClearCase, etc.Specify the operating systems (platforms), web servers, app

44、lication servers, development servers that areto be used in the project and the reasons for their selection. Examples of these tools are Sun Solaris, iPlanet, JBuilder, WebSphere, etc.5.8.2Techniques and StandardsLists the documented project technical standards etc by reference.Examples may be:User-Interface GuidelinesProgramming GuidelinesTest Guidelines, e