Project Management Plan Template项目管理计划模板.docx

1、Project Management Plan Template项目管理计划模板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 publis

2、hing the document.Revision 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.DateVersionDescriptionAuthorDistribution Li

3、stState 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 RecipientOrganizationTable of ContentsProject Management Plan1.IntroductionThe introduction of the Project Management Plan should p

4、rovide an overview 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 P

5、lan; what Project(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. Th

6、is information may 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 organiza

7、tion. Specify the 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 Manag

8、ement Plan Software 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.2.Project OverviewProject Name, Code and LeaderSpecify the project name, projec

9、t code and project 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

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

11、e project.Non-Critical 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 a

12、rtifacts to be created 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.3.Project Organi

13、zationOrganizational 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 s

14、tructure should also 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 GroupDevelopmen

15、t TeamDatabase Management 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 na

16、mes.External OrganizationExternal 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 Holder4.Management Pr

17、ocessWork Breakdown Structure (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 proje

18、ct when re-estimation 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, e

19、tc.Project ScheduleDiagrams/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, requi

20、rements, analysis and 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

21、and list the objectives 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 o

22、r iteration. State what 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 BudgetAll

23、ocation of costs against 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 spendi

24、ng against the project 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

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

26、sDescribe the approach that 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 PlanSpe

27、cify the work products to 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 manageme

28、nt 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.Requirements Management ToolsSpecify the req

29、uirements 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 these 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