Project_Plan_Project_Charter-项目章程模板-项目管理英文模板

1Project Plan/Project CharterProject NumberASSIGN A NUMBER.Project Or Sub-Project NameApplications Delivery MethodologyBackground NAME OF CLIENT must dramatically improve its ability to delivery business applications in a timely, cost-effective, flexible and quality manner. Specific program goals include achievement of at least an order of magnitude productivity improvement.ScopeTwelve functional objectives have been identified for project completion: 1. Provide identifiable and measurable improvements to the applications delivery process. Specific measures of improvement will be identified as part of concept validation. 2. Central repository of delivery routes customized to capture CLIENTS best practices implemented. 3. Processes in place to support project managers in the use of the uniform and proven best practices to generate project plans. 4. Support of the enterprise CMM/SEI objectives. 5. Time, cost and quality metrics and effort estimation models implemented. 6. Consistent use of the methodology for applications delivery. 7. Continuous process improvement infrastructure defined and implemented. 8. Risk driven project management implemented. 9. Process library delivery routes controlled from the process librarian workstation. 10.Project management automated and controlled from the project managers workstation. 11.Knowledge transfer to CLIENT completed. 12.Sustaining organization defined and implemented.2Concept DefinitionThe concept is that a methodology will dramatically improve CLIENTs ability to deliver business applications in a timely, cost-effective, flexible, and quality manner. This concept will be achieved through:A proactively managed applications delivery environment;Process, technology, organization, people, and leadership factors all planned and integrated;A very high degree of reuse through employment and enforcement of NAME OF METHODOLOGY TOOL, standards, specifications, and reusable frameworks and components designed for flexibility; andAn ongoing preventive maintenance program.Areas of ImpactThe IS project manager and teams will be the primary areas impacted by this project. During the deployment (concept validation, full-scale development, and implementation) phases, the methodology project will fund for activities relating to deployment.Pathfinder projects will provide resources for training, to support customization of the process tool product, participate in project meetings, and support assessments. Specific resource requirements for each project will be determined at project start-up. Limited workstation services support will be required to support tool implementation.3RisksRisk AreaAssessmentImpactMitigation Leadership, Support and Buy-InHighProject requires support by IS Department Heads for an enterprise infrastructure solution.Dedicated change management effort.StaffingMediumSuccess of project depends on ability to staff with credible experience in the technical areas. Use of 3rd party vendors to build internal expertise; staffing assessment at each project review.CostMediumWe developed an early estimate of 98 and 99 costs. However, we do not yet have a full understanding of sustained costs. Develop a total life cycle cost estimate during concept validation as part of the milestone decision.ScheduleMediumCurrent industry practices indicate 18-36 months were required to institute a methodology. Introduction of methodology into CLIENT based on “pull” from applications delivery areas.ScopeLowSuccessful completion of concept validation will result in a client-wide implementation.-QualityUnknownThis risk factor will depend on the results of concept validation.Continue to understand IS departmental requirements for repeatable processes and rigor.Assumptions 1. The methodology will be piloted using pathfinder projects that represent typical CLIENT applications delivery efforts. 2. Methodology project members will participate in the pathfinder projects to gain knowledge of the effectiveness of the methodology for enterprise use. 3. The initial pathfinder projects will use NAME/DESCRIPTION of approach for implementation and deployment. 4. The deployment will run through the end of YEAR. 5. LIST ANY OTHER ASSUMPTIONS HERE.Constraints 1. Concept validation will run through MONTH, YEAR and is budgeted for $AMOUNT. 2. YEAR budget is $AMOUNT. 3. Late selection of concept validation pathfinder projects may constrain the amount of quantitative information to support the full-scale development milestone decision.4Implementation ApproachThe implementation will occur from WHEN through WHEN with the following phase points currently planned: 1. Concept validation through MONTH/YEAR at a cost of $AMOUNT. During this phase, the methodology will be implemented on NUMBER OF projects WHERE. Overall implementation planning will also be completed during this phase. 2. DESCRIBE FIRST FULL-SCALE DEPLOYMENT PHASE AND TIMEFRAME. 3. DESCRI