Sei sulla pagina 1di 6

Project Plan/Project Charter

Project Number


Project or Sub-Project Name

Applications Delivery Methodology


<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.


Twelve 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

2. Central repository of delivery routes customized to capture <Client>’s best practices


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 manager’s

11. Knowledge transfer to <Client> completed.

12. Sustaining organization defined and implemented.

Concept Definition

The concept is that a methodology will dramatically improve <Client>’s ability to deliver
business applications in a timely, cost-effective, flexible, and quality manner. This
concept will be achieved through: Project Plan/Project Charter

• A proactively managed applications delivery environment;

• Process, technology, organization, people, and leadership factors all planned and
• A very high degree of reuse through employment and enforcement of
<Methodology Tool>, standards, specifications, and reusable frameworks and
components designed for flexibility; and
• An ongoing preventive maintenance program.
Areas of Impact

The 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

• 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-
• Limited workstation services support will be required to support tool implementation.

Risk Area Assessment Impact Mitigation

Leadership, Project requires support by IS Dedicated change
Support and High Department Heads for an management effort.
Buy-In enterprise infrastructure solution.
Success of project depends on Use of 3rd party vendors to
Staffing Medium ability to staff with credible build internal expertise;
experience in the technical areas. staffing assessment at each
project review.
We developed an early estimate Develop a total life cycle
Cost Medium of 98 and 99 costs. However, we cost estimate during
do not yet have a full concept validation as part
understanding of sustained costs. of the milestone decision.
Current industry practices Introduction of
Schedule Medium indicate 18-36 months were methodology into
required to institute a <Client> based on “pull”
methodology. from applications delivery
Successful completion of
Scope Low concept validation will result in -
a client-wide implementation.
This risk factor will depend on Continue to understand IS
Quality Unknown the results of concept validation. departmental requirements
for repeatable processes
and rigor.

©2007 2 Project Plan/Project Charter


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>.


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.

Implementation Approach

The 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. <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>, and activation of the sustaining

5. 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 implementation.

Specific implementation project plans for each approved phase will be developed at the
milestone decision points.

Functional Requirements

The 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 will provide the specific
work packages required to satisfy the requirements.

©2007 3 Project Plan/Project Charter

Concept Validation - Full Scale Deployment - Implementation - <Year>

<Year> <Year>
1. <Client> proof of 1. Forty percent of 1. TBD percent of
concept pathfinder <Client> IT <Client> IT
projects identified Solutions Delivery Solutions Delivery
and initiated. staff trained. staff trained.
2. Pathfinder project 2. Technical 2. One hundred
lessons learned infrastructure percent of training
gathered and refined. responsibility
analyzed. assumed by
3. Training program
3. Initial <Client> established.
pathfinder project 3. Integration with
4. Project estimating &
staff trained in external initiatives
tracking improved.
<Methodology completed.
Tool> methods. 5. Interaction with
4. Technical
implementation of
4. Training infrastructure
new tool set
improvements refined.
identified for
5. <Client> best
methods and tool. 6. Projects planned &
practices from
managed jointly by
5. Initial technical lessons learned
business & IT
infrastructure incorporated into
project managers.
defined and methodology.
deployed. 7. <Client> metrics
6. Repository of best
6. Pathfinder project practices -reusable
incorporated in
teams available to templates,
seed new projects. deliverables, and
7. Roadmap approach
8. Continuous process established.
approved by
Steering Committee. 7. Application
process established.
8. Process library
9. Standardized increased.
management and
processes and
enhancement 8. System quality
methods defined
infrastructure improved by
with limited use.
established for (Percentage TBD)
pathfinder routes. 10. Sixty percent of
9. Application delivery
classroom training
9. Process cycle time reduced.
assumed by
metrics for time,
cost, and quality
established for CV
and identified for
10. Policies, standards,
and compliance
criteria identified for

©2007 4 Project Plan/Project Charter

Concept Validation - Full Scale Deployment - Implementation - <Year>

<Year> <Year>
11. FSD phase defined
and planned.

©2007 5 Project Plan/Project Charter

Key People

• Program Sponsor: <Name, Title>

• Methodology Project Sponsor: <Name>
• Program Manager: <Name>
• Methodology Project Lead: <Name>

Project Manager: Date:


©2007 6