Doc Number XXXX Ver 1.
0
Print Date 11/1/22
Page Page 1 of 8
Project Charter
Project Project Name Date Creation Date
Created By Your Name Phone Email
Mission • Expand all the rows as necessary to include your text. However the whole document should probably
be no longer than 2 pages.
• You may also want to replace the Key Consulting logo with the project’s logo.
• Not all the sections listed here may be needed on a particular project. There may also be items you
need to include that are not listed here.
• Many of these items listed will be visited in more detail when you start planning. The objective of
the charter is to document the information as it is known at the beginning of the project – not to
get into the planning itself.
• Delete the blue instruction text as you move through the form.
• The mission, vision, or goal, for the project should be documented in this row. What is the project?
Objectives • Why is it important to achieve the project mission? What do you hope to achieve? What is the
purpose or business justification? What value will the project bring to the organization? Who
benefits?
• How will you know the project is done?
Deliverables • What will the project actually produce? These should be measurable items. Nouns.
• Make sure to include all the Deliverables that will be needed for a successful project.
Stakeholders • Who will be involved in, or impacted by the project? List individuals, departments, organizations etc.
• Think about stakeholders within your organization, and in the community at large.
Roles and • Who will be the Project Sponsor? The Project Manager?
Responsibilitie • Who will be on the project team, and what will be their role on the team?
s
Approach • What will be the major phases/steps for the project?
Assumptions • What high-level assumptions have already been made about the project?
• Have any assumptions been made about available funding or schedules?
Communications • What will be the main, initial, channels of communication?
• Do you anticipate any communication problems that should be clarified here?
• How often will the team meet?
Risks • What high-level risks have already been identified? (Risks are uncertain events that may occur.)
• What may prevent you from completing the project successfully?
Challenges • What conditions/situations, if any, are known to exist right now that will challenge the project?
Documentation • Where will project documentation be kept?
Boundaries • Are there specific items that are NOT within the scope of the project?
Decision • What will be the decision making process(es) for the project?
Making Process
Signatures • You may want to ask people to sign an agreed-upon final version of the charter to document everyone’s
agreement.
PC01 Version 3.1 © Key Consulting Inc www.consulting.ky
Comments or suggested improvements should be sent to
[email protected] Project Charter –
Second Example
GENERAL PROJECT INFORMATION
Project Name Project ID/Number
Date Prepared
Project Sponsor
Project Manager Program Manager
Team Members
Other Key Stakeholders
SCOPE STATEMENT
Business Need and Problem Statement
The ABACUS program team is incorporating the Horseshoe House into the Brand-
Forehand organization so that it can increase Project Share and grow the business.
The ABACUS team responsible for the integration of the Horseshoe House is
experiencing challenges in communication, both geographical and technical. There
is a need for the team to work from a standardized technological platform and
software base and allow team members to communicate without face-to-face
meetings.
RA07_Project Charter-TEMPLATE.doc
Page 2 of 8
Project Charter –
Second Example
Project Goals and Objectives (Deliverables)
• Install Microsoft Office 2007 on 90% of team member desktops within one
month of Sponsor approval and funding, and 100% by end of second month
after approval.
• All team members will be trained in coordination with the installation of
Microsoft Office.
• Install Microsoft Office SharePoint Server (MOSS) 2007, and distribute the
server URL so that clients can access it within one month of project approval.
• Reduce travel costs by 25% within three months of project completion.
• Reduce communication costs by 20% within three months of project completion.
• Replace 50 computers so that all computers can run Microsoft Office 2007.
Benefits
Team members will:
• Have to travel less, and regain productive time.
• Will see savings on phone costs
• Will reduce confusion and ineffective communication through the
standardization and centralization of calendars, email, and document
storage.
• Newer computers will speed other operations, reduce
maintenance requirement, and increase productivity (?)
Metrics
• Number of upgraded computers
• Number of trips by ABACUS team members
• Travel costs
• Number of trained ABACUS team members
RA07_Project Charter-TEMPLATE.doc
Page 3 of 8
Project Charter –
Second Example
SUPPORTING DETAIL
Cost
A budget of $155,000 is allocated, however, the current estimated costs will include
these Rough Order of Magnitude estimates (with a variance of +/- 25%).
• Hardware ($3000*50)
• Software ($6000+$40,000)
• Consulting ($125 * 160)
• Internal Costs ($85*400)
• Project Manager time ($85*320)
• Travel and Expenses ($10,000)
• Midnight Bowling ($400)
High-Level Phases (Project Lifecycle)
Detailed Plan
Develop
Deploy
Support
Critical Milestone Date(s) – include desired end date
• PA+1 week = Planning Complete
• PA+2 weeks= MOSS installed
• PA+ 3 weeks = Pilot Install Complete and Computers installed
• PA+4 weeks = 90% Software installed and users trained
• PA+8 weeks = 100% software installed and users trained
RA07_Project Charter-TEMPLATE.doc
Page 4 of 8
Project Charter –
Second Example
Constraints/Assumptions
• The estimated number of computers to be replaced is correct (50).
• The estimates provide by Khan Dewitt are applicable to the B-F
environment.
• Saving are related to current travel and communications requirements and
conditions. Additional requirements for travel not related to current
communication requirements may cause travel to increase, and will not be
counted in measurements for savings.
• Help Desk has adequate resources available to install computers
• Sponsor will communicate this project as a priority that will take precedence
over other current projects.
•
• Purchasing already has agreements with Brazilian and Mexican vendors.
• SOW can be achieved with TECH systems, and Kahn Dewitt can start on PA+ 1
day.
• Funds are available for project immediately.
• All project team members who travel have valid passports.
Risks
• Brazilian computers may cost approximately 30% more than the US
computers and must be purchased with a Brazilian vendor.
• Mexican computers may cost more than the US computers, and must
be purchased from a Mexican vendor.
RA07_Project Charter-TEMPLATE.doc
Page 5 of 8
Project Charter –
Second Example
ADDITIONAL INFORMATION
Sponsor Responsibilities
• Provide funding on a timely basis
• Clear the path for project execution by communicating with organization
• Be supportive and flexible
• Protect the integrity of the project objectives
• Follow defined change control procedures
• Attend midnight bowling session
• Be designated driver
Program Manager Responsibilities
• Provide at least 40 hours of Nick Burns times, and emphasize the importance
of the project.
• Identify risks and assist in response and contingency planning
• Identify potential conflicts between this project and other program projects
• Assist in communicating with ABACUS team members
• Participate in pilot
Project Manager Responsibilities
• Communicate weekly
•
•
Links to Other Projects
We agree that this is a viable project, and we will support it.
Date: Date:
Project Manager Program Manager
Date:
Sponsor
RA07_Project Charter-TEMPLATE.doc
Page 6 of 8
New York University
Project Charter Template – Third Example
PROJECT CHARTER
1. General Project Information
Project Name:
Executive Sponsors:
Department Sponsor:
Impact of project:
2. Project Team
Name Department Telephone E-mail
Project Manager:
Team Members:
3. Stakeholders (e.g., those with a significant interest in or who will be significantly affected by this project)
4. Project Scope Statement
Project Purpose / Business Justification Describe the business need this project addresses
Objectives (in business terms) Describe the measurable outcomes of the project, e.g., reduce cost by xxxx or increase quality to yyyy
Deliverables List the high-level “products” to be created (e.g., improved xxxx process, employee manual on yyyy)
Submitted by: [Name] Page 7 of 8
For assistance in using this template, contact NYU’s Office of Learning and Organizational Development at 212-998-
1250.
New York University
Project Charter Template – Third Example
Scope List what the project will and will not address (e.g., this project addresses units that report into the Office of Executive
Vice President. Units that report into the Provosts Office are not included)
Project Milestones Propose start and end dates for Project Phases (e.g., Inception, Planning, Construction, Delivery) and other major
milestones
Major Known Risks (including significant Assumptions) Identify obstacles that may cause the project to fail.
Risk Risk Rating (Hi, Med, Lo)
Constraints List any conditions that may limit the project team’s options with respect to resources, personnel, or schedule (e.g.,
predetermined budget or project end date, limit on number of staff that may be assigned to the project).
External Dependencies Will project success depend on coordination of efforts between the project team and one or more
other individuals or groups? Has everyone involved agreed to this interaction?
5. Communication Strategy (specify how the project manager will communicate to the Executive Sponsor, Project Team
members and Stakeholders, e.g., frequency of status reports, frequency of Project Team meetings, etc.
6. Sign-off
Name Signature Date
(MM/DD/YYYY)
Executive Sponsor
Department Sponsor
Project Manager
7. Notes
Submitted by: [Name] Page 8 of 8
For assistance in using this template, contact NYU’s Office of Learning and Organizational Development at 212-998-
1250.
