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 distributedwhenever the document is revised. Also state the name of their parent organization.Document RecipientOrganizationTable of Contents1. Introduction91.1 Purpose91.2 Scope91.3 Definitions, Acronyms and Abbreviations91.4 References101.5 Overview112. Project Overview122

4、.1 Project Name, Code and Leader122.2 Project Purpose, Scope and Objectives122.3 Assumptions and Constraints122.3.1 Critical Assumptionsand Constraints13132.3.2 Non-Critical Assumptions and Constraints4.2.2 Size192.5 Project Deliverables132.6 Tailoring Guidelines142.7 Software Development LifeCycle1

5、43. Project Organization153.1 Organizational Structure153.2 External Interfaces173.3 Roles and Responsibilities173.3.1 184. Management Process194.1 Work Breakdown Structure(WBS)194.2 Project Estimates194.2.3 Effort194.3 Project Schedule204.3.1 Pre-Development Schedule204.3.2 Development Schedule204.

6、4 Project Phases, Iterations andReleases204.4.1 Project Phases204.4.2 Project Iterations214.4.3 Releases214.5 Project Resourcing214.5.1 Staffing214.5.2 Resource Acquisition214.5.3 Training225.6 Project Maintenance254.7 Project Monitoring and Control224.7.1 Schedule Control224.7.2 Budget Control224.7

7、.3 Measurements234.8 Risk Management Plan234.9 Project Closure235. Technical Process Plans245.1 User Experience Design245.2 Requirements Management245.3 Analysis and Design245.4 Development Plan245.7 Test Plan255.8 Tools, Techniques and Standards255.8.1 Tools255.8.2 Techniques and Standards285.9 Inf

8、rastructure285.10 Facilities295.11 Security Plan296. Supporting Process Plans296.1 Configuration Management Plan296.2 Documentation296.3 Software Quality AssurancePlan306.4Intergroup Coordination306.5 Communication306.6 Problem Resolution306.7 Subcontractor Management307. Additional plans318. Append

9、ices311.4 References1. IntroductionThe introduction of theProject Management Plasnhould provide an overview of the entire document. It should include the purpose, scope, definitions, acronyms, abbreviations, references and overview of tPhrisoject Management Pla.n1.1 PurposeSpecify the purpose of thi

10、Psroject Management Plan.1.2 ScopeA brief description of the scope of thiPsroject Management Pla; nwhat Project(s) itis associated with, and anything else that is affected or influenced by this document.1.3 Definitions, Acronyms and AbbreviationsThis subsection should provide the definitions of all

11、terms, acronyms, and abbreviations required to interpret properly thPeroject Management Pla.?n This information may be provided by reference to the project Glossary.This subsection should provide a complete list of all documents referenced elsewhere in thProject Management Pla nEach document should

12、be identified by title, report number (if applicable), date, and publishing organization. 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 artifa

13、cts may include:Risk Management PlanUser Interfaces GuidelinesConfiguration Management PlanSoftware Quality Assurance Plan, etc.Document TitlePublishing Organization1.5 OverviewThis subsection should describe what the rest ofPthroeject Management Plancontains and explain how the document is organize

14、d.2. Project Overview2.1 Project Name, Code and LeaderSpecify the project name, project code and project leader (project manager).Project Name: Project Code: Project Leader: 2.2 Project Purpose, Scope and ObjectivesA brief description of the purpose and objectives of this project, and a brief descri

15、ption of what deliverables the project is expected to deliver.2.3 Assumptions 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

16、.3.1 Critical Assumptions and ConstraintsState the critical assumptions and constraints affecting the project.2.3.2 Non-Critical Assumptions and ConstraintsState the non-critical assumptions and constraints affecting the project.2.4 Project MilestonesTabular list of major milestones to be achieved d

17、uring the project, with target dates.MilestoneTarget Achievement Date2.5 Project DeliverablesTabular list of the artifacts to be created during the project, with target delivery dates.DeliverablesTarget Delivery Date2.6 Tailoring GuidelinesSpecify the tailoring guidelines for the project.2.7 Softwar

18、e Development Life CycleSpecify the Software Development Life Cycle that is to be followed in the project.3.Project Organization3.1 Organizational StructureDescribe the organizational structure of the project team, including management and other review authorities. This should include identification

19、 of all projectorganizational 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 Steering CommitteeProject Manage

20、ment TeamArchitecture GroupUser Experience Design TeamRequirements TeamAnalysis and Design TeamImplementation GroupDevelopment TeamDatabase Management TeamTesting TeamInfrastructure TeamConfiguration Management TeamSoftware Quality Assurance Team, etc.Organizational UnitDescription3.2 External Inter

21、facesDescribe how the project interfaces with external groups. For each external group, identify the internal/external contact names.ExternalOrganizationExternal RoleExternal RoleHolderResponsibility ofExternal Role HolderInternalContact Role and PersonOrganizationRoleRoleResponsibilityNameHolderDet

22、ailsName,Name3.3 Roles and ResponsibilitiesSpecify the roles, responsibilities and role holders within each organizational unit of the project.3.3.1 RoleResponsibilityRole HolderResponsibility Detail4. Management Process4.1 Work Breakdown Structure (WBS)List the activities necessary for completing t

23、he project.4.2 Project Estimates4.2.1 Estimation 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.4.2.2 SizeState the size of each activ

24、ity as calculated according to the estimation 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 thesize estimation. Units may be man-hours, man-days, etc.4.3 Project ScheduleDiagrams/tables showing target dates f

25、or completion of iterations and phases, release points, demos, and other milestones. Critical path must be specified. Usually enclosed by reference to MS Project file.1.1.1 Pre-Development ScheduleThis schedule will cater for project planning, requirements, analysis and design activities.1.1.2 Devel

26、opment ScheduleThis schedule will cater coding, testing and deployment activities.1.4 Project Phases, Iterations and Releases1.4.1 Project PhasesIdentify phases and major milestones with their achievement criteria.1.4.2 Project IterationsSpecify the number of iterations and list the objectives to be

27、 accomplished for eachof the iterations.1.4.3 ReleasesBrief descriptions of each software release, whether demo, beta, etc.1.5 Project Resourcing1.5.1 StaffingIdentify here the numbers and type of staff required (including and special skills orexperience), scheduled by project phase or iteration. St

28、ate what resources are critical.1.5.2 Resource AcquisitionDescribe how you will approach finding and acquiring the staff needed for theproject.1.5.3 TrainingList any special training project team members will require, with target dates for when this training should be completed.1.6 Project BudgetAll

29、ocation of costs against the WBS and the project phases.1.7 Project Monitoring and Control1.7.1 Schedule ControlDescribes the approach to be taken to monitor progress against the planned schedule and how to take corrective action when required.1.7.2 Budget ControlDescribes the approach to be taken t

30、o monitor spending against the project budget and how to take corrective action when required.1.7.3 MeasurementsDescribe the types of measurements to be taken, their frequency, and responsibleworkers/entities for this purpose.1.8 Risk Management PlanEnclosed by reference1.9 Project ClosureDescribe t

31、he activities for the orderly completion of the project, including staffreassignment, 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 guid

32、elines to be followed.5.2 RequirementsDescribe 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

33、 PlanEnclosed by reference5.5 Peer Review 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 Standa

34、rds5.8.1 Tools Project Management 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 the

35、se tools are MS Project, etc. Database Management System SoftwareSpecify 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 manag

36、ement, 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,

37、Power Designer etc. LanguagesSpecify the languages that are to be used for software development in the projectand 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

38、project and thereasons for their selection. Examples of these tools can be Dreamweaver, Flash, etc.Specify 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 SoftwareSp

39、ecify 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 reasonsfor their selection. Examples of these tools ar

40、e 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 configuration m

41、anagement tools that are to be used in the project andthe 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 pro

42、ject and the reasons for theirselection. 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 GuidelinesTest Guidelines, etc.5.9 InfrastructureSpecify hardware, network connectivity, bandwidth, etc., req