1、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 in
2、clude 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
3、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
4、.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 control
5、led 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
6、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
7、very high degree of reuse through employment and enforcement of NAME OF METHODOLOGY TOOL, standards, specifications, and reusable frameworks and components designed for flexibility; and An ongoing preventive maintenance program.Areas of ImpactThe IS project manager and teams will be the primary area
8、s 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 pr
9、oduct, 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 Area Assessment Impact MitigationLeadership, Suppor
10、t and Buy-InHighProject requires support by IS Department Heads for an enterprise infrastructure solution.Dedicated change management effort.Staffing MediumSuccess of project depends on ability to staff with credible experience in the technical areas. Use of 3rd party vendors to build internal exper
11、tise; staffing assessment at each project review.Cost MediumWe 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.Schedule MediumCurr
12、ent industry practices indicate 18-36 months were required to institute a methodology. Introduction of methodology into CLIENT based on “pull” from applications delivery areas.Scope LowSuccessful completion of concept validation will result in a client-wide implementation.-Quality UnknownThis risk f
13、actor will depend on the results of concept validation.Continue to understand IS departmental requirements for repeatable processes and rigor.Assumptions1. The methodology will be piloted using pathfinder projects that represent typical CLIENT applications delivery efforts. 2. Methodology project me
14、mbers 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 OTH
15、ER ASSUMPTIONS HERE.Constraints1. 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 dec
16、ision.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 implementati
17、on planning will also be completed during this phase.2. DESCRIBE FIRST FULL-SCALE DEPLOYMENT PHASE AND TIMEFRAME.3. DESCRIBE SECOND FULL-SCALE DEPLOYMENT PHASE AND TIMEFRAME.4. Implementation through the end of YEAR. Implementation on additional projects, completions of knowledge transfer to CLIENT,
18、 and activation of the sustaining organization.The project RoadMap will describe the overall project implementation plan, including work packages and deliverables for each year. The RoadMap also defines the overall project completion goals and the specific objectives set for each year of the impleme
19、ntation.Specific implementation project plans for each approved phase will be developed at the milestone decision points.Functional RequirementsThe following table reflects the requirements this project will solve by phase. A specific project plan will be developed at the start of each phase and wil
20、l provide the specific work packages required to satisfy the requirements.Concept Validation - YEAR Full Scale Deployment - YEAR Implementation - YEAR1. CLIENT proof of concept pathfinder projects identified and initiated.2. Pathfinder project lessons learned gathered and analyzed.3. Initial CLIENT
21、pathfinder project staff trained in NAME OF METHODOLOGY TOOL methods.4. Training improvements identified for methods and tool.5. Initial technical infrastructure defined and deployed.6. Pathfinder project teams 1. Forty percent of CLIENT IT Solutions Delivery staff trained.2. Technical infrastructur
22、e refined.3. Training program established.4. Project estimating & tracking improved.5. Interaction with implementation of new tool set managed.6. Projects planned & managed jointly by business & IT project managers.7. CLIENT metrics definitions 1. TBD percent of CLIENT IT Solutions Delivery staff tr
23、ained.2. One hundred percent of training responsibility assumed by CLIENT.3. Integration with external initiatives completed.4. Technical infrastructure refined.5. CLIENT best practices from lessons learned incorporated into methodology.6. Repository of best practices -reusable templates, deliverabl
24、es, and methods established.5Concept Validation - YEAR Full Scale Deployment - YEAR Implementation - YEARavailable to seed new projects.7. Roadmap approach approved by Steering Committee.8. Process library management and enhancement infrastructure established for pathfinder routes.9. Process improve
25、ment metrics for time, cost, and quality established for CV and identified for FSD & Implementation.10. Policies, standards, and compliance criteria identified for methodology institutionalization.11. FSD phase defined and planned.incorporated in NAME OF METHODOLOGY TOOL8. Continuous process improve
26、ment process established.9. Standardized processes and methods defined with limited use.10. Sixty percent of classroom training responsibility assumed by CLIENT.7. Application productivity increased.8. System quality improved by (Percentage TBD)9. Application delivery cycle time reduced.Key People Program Sponsor: NAME, TITLE Methodology Project Sponsor: NAME Program Manager: NAME Methodology Project Lead: NAMEApprovedNAME, Program Manager Date
