Project Charter DRAFT

Sample

<Company>

Date: <MM/DD/YYYY>
gantthead.com Project Charter Draft

Project Description
The PlanView implementation is sponsored by Mr. Jones, Vice President of Information
Systems, who is responsible for determining the success or failure of the system in
meeting the project objectives. The system is being implemented in the information
services and information technology departments of <Company> The departments
collectively consist of approximately 13 managers and 70 team members. The
information services departments support their respective business segment, whereas
the information technology groups support all business segments for their respective
area of technology. Projects routinely cross the various information services and
information technology groups. During the implementation of PlanView, project
management processes and procedures will be improved and standardized for all the
groups. XYZ Division will be the first group to be converted to PlanView; the other
groups will then follow.

The project is comprised of four key phases:

 Requirements – Plan the complete implementation, analyze business requirements,

design the implementation for customer’s environment, and set up the project
management activities to oversee the implementation.

 Development – Install, initialize and test the PlanView software, identify the system
interface requirements, develop the Procedures Guide, develop user training, train
the implementation team.

 Execute – Migrate existing projects into PlanView’s central repository, train users,
rollout PlanView to production environment; and

 Finish – wrapup activities of the project will be performed to conclude the project
such as post-implementation support and project assessment.

Objectives
Business Objectives for the project are as follows:

 All current information services and information technology projects will be loaded
and maintained in a central repository.

 All information services and information technology time will be tracked for all project,
support, and administrative activities.

 All required project and time reports will be available to team members and
management.

 A project methodology will be in place to promote consistency and effectiveness.

 All associated project management standards and methodologies will be available on

the intranet.

Scope
The scope of the project includes:

©2007 gantthead.com 2
gantthead.com Project Charter Draft

 Plan and manage the implementation of the PlanView software.

 Install the PlanView software in City, State.

 PlanView, Inc. staff to train and mentor up to ten (10) Customer Implementation staff
in use of the software.

 Identification of any necessary or desired interfaces with PlanView.

 Tailoring (not customization) of the PlanView training material for <Company>

 Assisting the <Company> Implementers with the development of the Procedures

Guide.

 Load PlanView repository with structures and approximately 300 projects containing
an average of 10 work entities per project.

 Custom report development is not included in the scope of this project.

Assumptions
 We will have the full cooperation and participation of the five information services
and information technology groups involved in the project.

 37 days of consulting time with PlanView, Inc. will be adequate for installation,
training, and other implementation assistance.

 PlanView will provide training for up to ten (10) Implementers; the Implementers will
then train the other groups.

 PlanView software will be adequate to support all information services and

information technology project management needs.

 <Company> staff will act as mentors for the various groups implementing PlanView.

 PlanView documentation and training materials are satisfactory.

 <Company> will schedule the PlanView, Inc. staff using the Project Approach as
defined in the PlanView Consulting Services Engagement Management Approach
document.

©2007 gantthead.com 3
 gantthead.com Project Charter Draft

Project Components
There are three major components to any project. <Company> has chosen
RESOURCES as the most important component for the project.

Sc
e

he
op

d
Sc

ule
Resources
Project Approach
The major items of work for the project are

 Install Version 5.2A of the PlanView software.

 Plan and manage the PlanView implementation.

 Identification of interfaces to and from PlanView.

 Conduct training and mentoring for <Company> staff.

 Implementation of the PlanView for all 13 Managers and 70 Time Reporters at

<Company>

Summary Schedule
The following is a very high level schedule of the major components of this project.

June July August September Octo

ID Task Name Duration 31 7 14 21 28 5 12 19 26 2 9 16 23 30 6 13 20 27 4 11
1 Upgrade to PlanView V5.2A, Integrate 22d
Customizations,Develop New Modifications
2 Design and Develop Flextimeand OvertimeModules 43d

3 Design and Develop Interfaces To and From 36d

PlanView
4 Conduct Trial Phase 10d

5 Conduct Pilot Phase 10d

6 ImplementPortico 0d 9/28/98 8:

©2007 gantthead.com 4
gantthead.com Project Charter Draft

Project Roles and Personnel

The <Company> Implementation team members are:

Roles – Name / Title Phone E-mail

<Company>
Customer Project
Manager

The <Company> Internal Technical Support team members are:

Roles – Name Phone E-mail

<Company>
PlanView System
Administrator
Oracle Database
Administrator
Network
Administration
Support
Desk Top PC
Support
Facilitator
Web-Server
Support

The PlanView team members are:

Roles – PlanView, Name Phone E-mail

Inc.
Regional Sales <[email protected]>
Manager (Account
Team Member)
Territory Manager <[email protected]>
(Account Team
Member)
Implementation 512-346-8600 <[email protected]>
Manager (Account ext.
Team Member)
Senior Consultant 512-346-8600 <[email protected]>
©2007 gantthead.com 5
gantthead.com Project Charter Draft

Roles – PlanView, Name Phone E-mail

Inc.
ext.
Implementation 512-346-8600 <[email protected]>
Consultant ext.
Trainer 512-346-8600 <[email protected]>
ext.

Constraints
 The system must be cut over into production at the end of an accounting month.

 <Company> has a code freeze each year from mid-December until mid-January. This code
freeze is not related to fiscal year-end, which is March 31 for <Company> The current
planned implementation date is September 28.

 <Company> external (Internet) e-mail is undependable. Critical items should be faxed.

Alternate communication methods in order of priority are through PlanView’s Internet FTP
site, Internet e-mail and PlanView’s BBS.

 Holidays and other work schedule issues: Jean Jones is on holiday from July 30 to Aug 24,
Caroline Smith is not in the office on Fridays, Julie Anderson on holiday from June 13 to
June 21.

 The final test database location for the Trial and Pilot has not been determined.

Project Duration
Key Project Milestones:

Requirements Phase Completion Date

Project Charter Authorized
Project Implementation Schedule Completed
Agreement on To Do List
Environmental Assessment Conducted
Development Phase
PlanView Software Installed and Tested
System Administrator Training Completed
PlanView Parameters Set
Training for Implementers Conducted
Procedures Guide Drafted
Execution Phase
PlanView Repository Populated
Standards Developed
Procedures Guide Finalized
©2007 gantthead.com 6
gantthead.com Project Charter Draft

End User Staff Trained

Reports Produced
Finish Phase
Support Plan Developed
Post Implementation Audit

Project Deliverables
Deliverables for this project are:

 Project Charter

 Environmental Assessment

 Project Implementation Plan

 PlanView Business Needs Analysis

 <Company>’s PlanView Procedures Guide (<Company> responsibility)

 PlanView Software installed on Servers and five (5) Clients by PlanView Staff

 Implementation team feedback on Processes and System Use

 Trained PlanView users:

o 2 PlanView System Administrators (PlanView Staff will train)

o 8 Implementers (PlanView Staff will train)
o 13 Managers (<Company> Staff will train)
o 70 Team Members/Time Reporting training (<Company> Staff will train)

Project Risks
Risks associated with this project are as follows:

 Multiple people acting as customer sponsor; thus no single point of contact.

 The <Company> Support Team staff is turning over. There are only two staff
members and both are leaving in June. No replacements have been selected as of
yet. Recruitment, training and retention of the Support Team could have a significant
impact on <Company>’s implementation. During the implementation PlanView
software support requirements will increase substantially.

Project Authorization
<Company> Authorization:

©2007 gantthead.com 7
gantthead.com Project Charter Draft

Approved By: Date:

<Title> Date:

<Name>

PlanView, Inc. Authorization:

Approved By: Date:

<Title> Date:

<Name>

©2007 gantthead.com 8