PROJECT CHARTER TEMPLATE

This Project Charter Template is free for you to copy and use on your project
and within your organization. We hope that you find this template useful and
welcome your comments. Public distribution of this document is only permitted
from the Project Management Docs official website at:
www. P roject M anagement D ocs.com
PROJECT CHARTER
<PROJECT NAME>
COMPANY NAME
STREET ADDRESS
CITY, STATE ZIP CODE
DATE
Project Charter Tempate
!!!"ProjectMa#a$eme#tDoc%"com
TA&LE O' CONTENTS
!C"T#$ %"MM&'(.....................................................................................................................)
P'*+CT P"'P*%,+"%T#-#C&T#*.....................................................................................................)
/usiness .eed,Case....................................................................................................................................................)
/usiness *bjecti0es....................................................................................................................................................)
P'*+CT D%C'#PT#*......................................................................................................................)
Project *bjecti0es and %uccess Criteria.....................................................................................................................1
'e2uirements..............................................................................................................................................................1
Constraints..................................................................................................................................................................1
&ssumptions................................................................................................................................................................3
Preliminary %cope %tatement......................................................................................................................................3
'#%4%................................................................................................................................................3
P'*+CT D5#$'&/5%..................................................................................................................6
%"MM&'( M#5%T*. %C7D"5...................................................................................................6
%"MM&'( /"D8T..........................................................................................................................6
P'*+CT &PP'*$&5 '9"#'M.T%...............................................................................................:
P'*+CT M&.&8'.........................................................................................................................:
&"T7*'#;&T#*................................................................................................................................<
=
Project Charter Tempate
!!!"ProjectMa#a$eme#tDoc%"com
E(EC)TI*E S)MMARY
The e>ecuti0e summary should be a high?le0el summary of what issues or problems the project
was created to correct. Typically@ the e>ecuti0e summary also pro0ides the bacAground
information and general statements regarding the projectBs purpose or justification which will be
co0ered in more detail in the appropriate sectionCsD of the charter.
-or the past se0eral years our company intranet has been subject to numerous e>ternal breaches
because of poor information technology C#TD security measures. These incidents ha0e resulted in
appro>imately E=F million in damages to the company. The #ntranet %ecurity &ssurance C#%&D
project has been created to address and correct these security issues and pre0ent further loss due
to e>ternal #T security breaches. The project will integrate impro0ed technology solutions with
our current platform in order to establish a more robust security infrastructure.
PROJECT P)RPOSE+J)STI'ICATION
This section describes the purpose and justification of the project in the form of business case
and objecti0es. The business case should pro0ide the reasoning behind the need for this project
as it relates to a function of the business.
&,%-#e%% Nee.+Ca%e
Discuss the logic for the /usiness .eed,Case CmarAet demand@ organizational need@ customer
re2uest@ technological ad0ance@ legal re2uirement@ ecological impacts@ social need@ etcD. This
section should also include the intended effects of the business case Ci.e. cost sa0ings@ process
impro0ement@ new product de0elopment@ etcD.
The #%& project has been created to increase organizational #T security in order to pre0ent
further financial damages resulting from e>ternal security breaches. The costs associated
with the successful design and implementation of these security measures will be reco0ered
as a result of the anticipated reduction in financial damages.
&,%-#e%% O/ject-0e%
This section should list the /usiness *bjecti0es for the project which should support the
organizational strategic plan.
The business objecti0es for this project are in direct support of our corporate strategic plan to
impro0e #T security and reduce costs associated with loss and waste.
? Design and test a new #T security infrastructure within the ne>t GF days
? Complete implementation the new #T infrastructure within the ne>t =)F days
? 'educe the amount of damages by 6FH in the first year
PROJECT DESCRIPTION
This section pro0ides a high?le0el description of the project. This description should not contain
too much detail but should pro0ide general information about what the project is@ how it will be
done@ and what it is intended to accomplish. &s the project mo0es forward the details will be
de0eloped@ but for the project charter@ high?le0el information is what should be pro0ided.
)
Project Charter Tempate
!!!"ProjectMa#a$eme#tDoc%"com
The #%& project will pro0ide increased security to the companyBs #T infrastructure and@ more
specifically@ to the company intranet. The #%& project will utilize impro0ed technology in the
form of security hardware and software in order to pre0ent e>ternal breaches of the company
intranet. &ll hardware and software will be integrated into the companyBs current #T platforms in
order to establish increased security while allowing all systems and processes to continue
without interruption.
Project O/ject-0e% a#. S,cce%% Cr-ter-a
*bjecti0es should be %M&'T: %pecific@ Measurable@ &ttainable@ 'ealistic@ and Time?bound.
The project manager must be able to tracA these objecti0es in order to determine if the project
is on the path to success. $ague@ confusing@ and unrealistic objecti0es maAe it difficult to
measure progress and success.
The objecti0es which mutually support the milestones and deli0erables for this project ha0e
been identified. #n order to achie0e success on the #%& project@ the following objecti0es must
be met within the designated time and budget allocations:
? De0elop security solution methodology to present to the $P of Technology within the
ne>t )F days
? Complete list of re2uired hardware,software which meets budget allocation within the
ne>t )6 days
? Create a simulated solution in the #T lab using all purchased hardware and software to
test the solution within the ne>t :F days
? &chie0e a simulated solution which allows no security breaches and complete testing
within the ne>t GF days
? #mplement the solution across the organization within the ne>t =)F days
Re1,-reme#t%
The project team should de0elop a list of all high?le0el project re2uirements. These
re2uirements are clear guidelines within which the project must conform and may be a result
of input from the project sponsor@ customer@ staAeholders@ or the project team.
This project must meet the following list of re2uirements in order to achie0e success.
? The solution must be tested in the #T lab prior to deployment
? %olution must be implemented without disruption to operations
&dditional re2uirements may be added as necessary@ with project sponsor appro0al@ as the
project mo0es forward.
Co#%tra-#t%
Constraints are restrictions or limitations that the project manager must deal with pertaining
to people@ money@ time@ or e2uipment. #t is the project managerBs role to balance these
constraints with a0ailable resources in order to ensure project success.
The following constraints pertain to the #%& project:
? &ll security hardware and software must be compatible with our current #T platforms
1
Project Charter Tempate
!!!"ProjectMa#a$eme#tDoc%"com
? &ll hardware and software must be purchased in accordance with the allocated budget
and timeline
? Two #T specialists and one security specialist will be pro0ided as resources for this
project
A%%,mpt-o#%
The project team must identify the assumptions they will be worAing under as the project
goes forward. These assumptions are what the project manager,team e>pect to ha0e or be
made a0ailable without anyone specifically stating so.
The following are a list of assumptions. "pon agreement and signature of this document@ all
parties acAnowledge that these assumptions are true and correct:
? This project has the full support of the project sponsor@ staAeholders@ and all departments
? The purpose of this project will be communicated throughout the company prior to
deployment
? The #T manager will pro0ide additional resources if necessary
Pre-m-#ar2 Scope Stateme#t
The preliminary scope statement is a general paragraph which highlights what the project
will include@ any high?le0el resource or re2uirement descriptions@ and what will constitute
completion of the project. This preliminary scope statement is e>actly that: preliminary. &ll
of this information will be e>panded upon in greater detail as the project mo0es forward and
undergoes progressi0e elaboration.
The #%& project will include the design@ testing@ and deli0ery of an impro0ed intranet security
system throughout the organization. &ll personnel@ hardware@ and software resources will be
managed by the project team. &ll project worA will be independent of daily and ongoing
operations and all re2uired testing will be done in the #T laboratory. &ll project funding will
be managed by the project manager up to and including the allocated amounts in this
document. &ny additional funding re2uires appro0al from the project sponsor. This project
will conclude when the final report is submitted within 1F days after the intranet security
solution is tested and deployed throughout the organization@ all technical documentation is
complete and distributed to the appropriate personnel@ and a list of future security
considerations is complete and submitted to the $P of Technology.
RIS3S
&ll projects ha0e some form of risA attached. This section should pro0ide a list of high?le0el
risAs that the project team has determined apply to this project.
The following risAs for the #%& project ha0e been identified. The project manager will determine
and employ the necessary risA mitigation,a0oidance strategies as appropriate to minimize the
liAelihood of these risAs:
? Potential disruption to operations during solution deployment
? >ternal threats breaching intranet security 0ia new methods
3
Project Charter Tempate
!!!"ProjectMa#a$eme#tDoc%"com
PROJECT DELI*ERA&LES
This section should list all of the deli0erables that the customer@ project sponsor@ or staAeholders
re2uire upon the successful completion of the project. 0ery effort must be made to ensure this
list includes all deli0erables and project sponsor appro0al must be re2uired for adding additional
deli0erables in order to a0oid scope creep.
The following deli0erables must be met upon the successful completion of the #%& project. &ny
changes to these deli0erables must be appro0ed by the project sponsor.
? -ully deployed intranet security solution
? Technical documentation for intranet security solution
? 'ecommendation list for future security considerations
S)MMARY MILESTONE SCHED)LE
This section pro0ides an estimated schedule of all high?le0el project milestones. #t is understood
that this is an estimate and will surely change as the project mo0es forward and the tasAs and
milestones and their associated re2uirements are more clearly defined.
The project %ummary Milestone %chedule is presented below. &s re2uirements are more clearly
defined this schedule may be modified. &ny changes will be communicated through project
status meetings by the project manager.
Summary Milestone Schedule List key project milestones relative to project start.
Project Milestone Target Date
(mm/dd/yyyy
Project Start 01/01/20xx
Complete Solution Design 01/21/20xx
Acquire Hardware and Software 01/2/20xx
Complete Solution Simulation wit! "ew Hardware/Software 0#/01/20xx
Complete Solution Simulation and $esting 0%/01/20xx
Deplo& Solution 0'/01/20xx
Project Complete 0'/1'/20xx
S)MMARY &)D4ET
The summary budget should contain general cost components and their planned costs. &s the
project mo0es forward these costs may change as all tasAs and re2uirements become clearer.
&ny changes must be communicated by the project manager.
The following table contains a summary budget based on the planned cost components and
estimated costs re2uired for successful completion of the project.
6
Project Charter Tempate
!!!"ProjectMa#a$eme#tDoc%"com
Summary !udget List component project costs
Project "omponent "omponent "ost
Personnel (esources )110*000
Hardware )%'*000
Software and +icensing ),'*000
-$ +a. Preparation )1'*000
Total #$%&'(((
PROJECT APPRO*AL RE5)IREMENTS
The organization must understand when the project has reached a successful completion. These
criteria must be clear and should be accepted by whoe0er will sign?off on the projectBs closeout.
*nce signed?off by the authorized person@ the project is deemed appro0ed and is successful as
long as it has met all of the agreed upon re2uirements.
%uccess for the #%& project will be achie0ed when a fully tested intranet security solution@ and all
technical documentation@ is fully deployed throughout the company within the time and cost
constraints indicated in this charter. &dditionally@ this measure of success must include a
recommendation list for future security considerations as we fully anticipate the necessity of this
solution to e0ol0e in order to pre0ent future threats. %uccess will be determined by the Project
%ponsor@ Mr. +im Thomas@ who will also authorize completion of the project.
PROJECT MANA4ER
This section e>plicitly states who is assigned as the PM@ their responsibility@ and authority le0el.
Depending on the organization and scope of the project@ the project manager may ha0e 0arying
le0els of responsibility and authority for personnel@ project e>penditures@ and scheduling.
+ohn Doe is named Project Manager for the duration of the #%& Project. Mr. DoeBs responsibility
is to manage all project tasAs@ scheduling@ and communication regarding the #%& project. 7is
team@ consisting of two #T specialists and one security specialist will be matri> support from the
#T department. Mr. Doe will coordinate all resource re2uirements through the #T department
manager@ +ane %now. Mr. Doe is authorized to appro0e all budget e>penditures up to@ and
including@ the allocated budget amounts. &ny additional funding must be re2uested through the
Project %ponsor@ +im Thomas. Mr. Doe will pro0ide weeAly updates to the Project %ponsor.
:
Project Charter Tempate
!!!"ProjectMa#a$eme#tDoc%"com
A)THORIZATION
This section pro0ides the names and authorization@ once signed@ for the project to mo0e forward
in accordance with the information contained in this charter.
&ppro0ed by the Project %ponsor:
IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII Date:IIIIIIIIIIIIIIIIIIII
JProject %ponsorK
JProject %ponsor TitleK
This free Project Charter Template is brought to you by www.ProjectManagementDocs.com
<