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

1、Project Management PlanVersion Note: The following template is provided for use in Xavor projects. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document.Revision HistoryFor ev

2、ery 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.DateVersionDescriptionAuthorDistribution ListState the persons/teams/groups to whom

3、 this document should be distributed whenever the document is revised. Also state the name of their parent organization.Document RecipientOrganizationTable of Contents TOC o 1-3 1.Introduction Project Management PlanIntroductionThe introduction of the Project Management Plan should provide an overvi

4、ew of the entire document. It should include the purpose, scope, definitions, acronyms, abbreviations, references and overview of this Project Management Plan.PurposeSpecify the purpose of this Project Management Plan.ScopeA brief description of the scope of this Project Management Plan; what Projec

5、t(s) it is associated with, and anything else that is affected or influenced by this document.Definitions, Acronyms and AbbreviationsThis subsection should provide the definitions of all terms, acronyms, and abbreviations required to interpret properly the Project Management Plan. This information m

6、ay be provided by reference to the project Glossary.ReferencesThis subsection should provide a complete list of all documents referenced elsewhere in the Project Management Plan. Each document should be identified by title, report number (if applicable), date, and publishing organization. Specify th

7、e sources from which the references can be obtained. This information may 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 Plan User Interfaces Guidelines Configuration Management Plan Softw

8、are Quality Assurance Plan, etc.Document TitlePublishing OrganizationOverviewThis subsection should describe what the rest of the Project Management Plan contains and explain how the document is organized.Project OverviewProject Name, Code and LeaderSpecify the project name, project code and project

9、 leader (project manager).Project Name: Project Code: Project Leader: 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.Assumptions and ConstraintsA list of assumptio

10、ns 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.Critical Assumptions and ConstraintsState the critical assumptions and constraints affecting the project.Non-Crit

11、ical Assumptions and ConstraintsState the non-critical assumptions and constraints affecting the project.Project MilestonesTabular list of major milestones to be achieved during the project, with target dates.MilestoneTarget Achievement DateProject DeliverablesTabular list of the artifacts to be cre

12、ated during the project, with target delivery dates.DeliverablesTarget Delivery DateTailoring GuidelinesSpecify the tailoring guidelines for the project.Software Development Life CycleSpecify the Software Development Life Cycle that is to be followed in the project.Project OrganizationOrganizational

13、 StructureDescribe the organizational structure of the project team, including management and other review authorities. This should include identification of all project organizational units and a description of their function and responsibility. A diagram of the organizational structure should also

14、 be attached for further illustration.Examples of project organizational units are:Project Implementation CommitteeProject Steering CommitteeProject Management TeamArchitecture GroupUser Experience Design TeamRequirements TeamAnalysis and Design TeamImplementation GroupDevelopment TeamDatabase Manag

15、ement TeamTesting TeamInfrastructure TeamConfiguration Management TeamSoftware Quality Assurance Team, etc.Organizational UnitDescriptionExternal InterfacesDescribe how the project interfaces with external groups. For each external group, identify the internal/external contact names.External Organiz

16、ationExternal RoleExternal Role HolderResponsibility of External Role HolderInternal Contact Role and Person, Roles and ResponsibilitiesSpecify the roles, responsibilities and role holders within each organizational unit of the project.RoleResponsibilityRole HolderManagement ProcessWork Breakdown St

17、ructure (WBS)List the activities necessary for completing the project.Project 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

18、will occur.SizeState the size of each activity as calculated 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.Project ScheduleDia

19、grams/tables showing target dates for completion of iterations and phases, release points, demos, and other milestones. Critical path must be specified. Usually enclosed by reference to MS Project file.Pre-Development ScheduleThis schedule will cater for project planning, requirements, analysis and

20、design activities.Development ScheduleThis schedule will cater coding, testing and deployment activities.Project Phases, Iterations and ReleasesProject PhasesIdentify phases and major milestones with their achievement criteria.Project IterationsSpecify the number of iterations and list the objective

21、s to be accomplished for each of the iterations.ReleasesBrief descriptions of each software release, whether demo, beta, etc.Project ResourcingStaffingIdentify here the numbers and type of staff required (including and special skills or experience), scheduled by project phase or iteration. State wha

22、t resources are critical.Resource 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.Project BudgetAllocation of costs again

23、st the WBS and the project phases.Project 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

24、 budget and how to take corrective action when required.MeasurementsDescribe the types of measurements to be taken, their frequency, and responsible workers/entities for this purpose.Risk Management PlanEnclosed by referenceProject ClosureDescribe the activities for the orderly completion of the pro

25、ject, including staff reassignment, archiving of project materials, post-mortem debriefings and reports etc.Technical Process PlansUser Experience DesignDescribe the approach that will be adopted with details of processes, procedures, and guidelines to be followed.RequirementsDescribe the approach t

26、hat will be adopted with details of processes, procedures, and guidelines to be followed.Analysis and DesignDescribe the approach that will be adopted with details of processes, procedures, and guidelines to be followed.Development PlanEnclosed by referencePeer Review PlanSpecify the work products t

27、o be peer reviewed, type of peer review, their frequency, etc.MaintenanceDescribe details of any software maintenance for the warranty period of the project.Test Plan Enclosed by referenceTools, Techniques and StandardsToolsProject Management ToolsSpecify the project management tools that are to be

28、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.Requirements Management ToolsSpecify the requirements management too

29、ls 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 these tools are Rational Requisite Pro, EINS, etc.System Analysis & Desig

30、n 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.LanguagesSpecify the languages that are to be used for software development in the project and the r

31、easons 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 selection. Examples of these tools can be Dreamweaver, Flash, etc.Database Management System Softwar

32、eSpecify 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 SoftwareSpecify any third party software that is to be used in the project and the reasons for their selection. Exam

33、ples 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 tools are WinRunner, LoadRunner, etc.Defect and Change Management ToolsSpecify the defect and change management tools tha

34、t are to be used in the project and the reasons for their selection. 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

35、.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.Techniques and Standa

36、rdsLists the documented project technical standards etc by reference. Examples may be:User-Interface GuidelinesProgramming GuidelinesTest Guidelines, etc.InfrastructureSpecify hardware, network connectivity, bandwidth, etc., required in this project. Make a clear distinction about what factors are critical.FacilitiesDescribe the facilities required for the execution of the pro