项目管理计划模板.doc

15 / 16Project 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 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 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 RecipientOrganizationTable of Contents1.Introduction51.1Purpose51.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.4Project Milestones62.5Project Deliverables62.6Tailoring Guidelines62.7Software Development Life Cycle73.Project Organization83.1Organizational Structure83.2External Interfaces103.3Roles and Responsibilities103.3.1104.Management Process114.1Work Breakdown Structure (WBS)114.2Project Estimates114.2.1Estimation Technique114.2.2Size114.2.3Effort114.3Project Schedule114.3.1Pre-Development Schedule114.3.2Development Schedule114.4Project Phases, Iterations and Releases114.4.1Project Phases114.4.2Project Iterations114.4.3Releases114.5Project Resourcing114.5.1Staffing114.5.2Resource Acquisition114.5.3Training124.6Project Budget124.7Project Monitoring and Control124.7.1Schedule Control124.7.2Budget Control124.7.3Measurements124.8Risk Management Plan124.9Project Closure125.Technical Process Plans135.1User Experience Design135.2Requirements Management135.3Analysis and Design135.4Development Plan135.5Peer Review Plan135.6Project Maintenance135.7Test Plan135.8Tools, Techniques and Standards135.8.1Tools135.8.2Techniques and Standards145.9Infrastructure145.10Facilities145.11Security Plan146.Supporting Process Plans156.1Configuration Management Plan156.2Documentation156.3Software Quality Assurance Plan156.4Intergroup Coordination156.5Communication156.6Problem Resolution156.7Subcontractor Management157.Additional plans168.Appendices16Project Management Plan1. IntroductionThe introduction of the Project Management Plan should provide an overview of the entire document. It should 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.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 influenced by this document.1.3 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 may be provided by reference to the project Glossary.1.4 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 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 Management Plan Software Quality Assurance Plan, etc.Document TitlePublishing Organization1.5 OverviewThis subsection should describe what the rest of the Project Management Plan contains and explain how the document is organized.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 description 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.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 during 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 Software 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 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 Committee Project Steering Committee Project Management Team Architecture Group User Experience Design Team Requirements Team Analysis and Design Team Implementation Group Development Team Database Management Team Testing Team Infrastructure Team Configuration Management Team Software Quality Assurance Team, etc.Organizational UnitDescription3.2 External InterfacesDescribe how the project interfaces with external groups. For each external group, identify the internal/external contact names.External OrganizationExternal RoleExternal Role HolderResponsibility of External Role HolderInternal Contact Role and Person, 3.3 Roles and ResponsibilitiesSpecify the roles, responsibilities and role holders within each organizational unit of the project.3.3.1 RoleResponsibilityRole Holder4. Management Process4.1 Work Breakdown Structure (WBS)List the activities necessary for completing the 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 activity 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 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, release 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 coding, 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.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 Resource 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 the 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 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 completion 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 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 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 Plan Enclosed by reference5.8 Tools, Techniques and Standards5.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 these tools are MS Project, etc. 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 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. LanguagesSpecify 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 selection. 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 SoftwareSpecify 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 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 configuration 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 GuidelinesTest Guidelines, etc.5.9 InfrastructureSpecify hardware, network connectivity, bandwidth, etc