PROJECT CHARTER: < PROJECT NAME>

The purpose of this document is to outline the objectives and scope of this project/workstream and gain approval from all
project stakeholders. This document includes identifying the key stakeholders, the objectives/deliverables, the critical success
factors, the constraints and assumptions, the implementation approach, the risks, the change control process, and the
communication plan for this project. Not all projects require the same level of documentation, so you may not need to or be
able to use all sections of this template.

Note: Instructions for what to include in each section appear in gold italics. Sample text appears in regular black text.

PROJECT (WORKSTREAM) CHARTER:

PROJECT NAME
CONTENTS
Executive Summary...................................................................................................................................................................................2
Project Purpose/Justification....................................................................................................................................................................2
Business Need/Case................................................................................................................................................................................2
Business Objectives................................................................................................................................................................................2
Project Description....................................................................................................................................................................................2
Project Objectives and Success Criteria.................................................................................................................................................3
Requirements..........................................................................................................................................................................................3
Constraints..............................................................................................................................................................................................3
Assumptions............................................................................................................................................................................................3
Preliminary Scope Statement..................................................................................................................................................................4
Key Steakholders & Resources.................................................................................................................................................................4
RA(S)CI Assignments................................................................................................................................................................................5
Project Deliverables...................................................................................................................................................................................7
Project Risks & Mitigation Strategies.....................................................................................................................................................7
Change Management & Communication................................................................................................................................................7
Summary Milestone Schedule..................................................................................................................................................................8
Summary Budget.......................................................................................................................................................................................8
Project Charter Approvals.......................................................................................................................................................................9
Document History......................................................................................................................................................................................9

Page 1 of 7
 PROJECT CHARTER: < PROJECT NAME>

EXECUTIVE SUMMARY
The executive summary should be a high-level summary of what issues or problems the project was created to correct. Typically, the
executive summary also provides the background information and general statements regarding the project’s purpose or justification
which will be covered in more detail in the appropriate section(s) of the charter.

PROJECT PURPOSE/JUSTIFICATION
This section describes the purpose and justification of the project in the form of business case and objectives. The business case
should provide the reasoning behind the need for this project as it relates to a function of the business.

BUSINESS NEED/CASE

Discuss the logic for the Business Need/Case (market demand, organizational need, customer request, technological advance, legal
requirement, ecological impacts, social need, etc). This section should also include the intended effects of the business case (i.e. cost
savings, process improvement, new product development, etc).

The VUMC XYZ project has been created to increase organizational IT security in order to prevent further financial damages
resulting from external security breaches. The costs associated with the successful design and implementation of these security
measures will be recovered as a result of the anticipated reduction in financial damages.

BUSINESS OBJECTIVES

This section should list the Business Objectives for the project which should support the organizational strategic plan.

The business objectives for this project are in direct support of our corporate strategic plan to improve IT security and reduce costs
associated with loss and waste.

 Design and test a new IT security infrastructure within the next 90 days.
 Complete implementation the new IT infrastructure within the next 120 days.
 Reduce the amount of damages by 50% in the first year.

PROJECT DESCRIPTION
This section provides a high-level description of the project. This description should not contain too much detail but should provide
general information about what the project is, how it will be done, and what it is intended to accomplish. As the project moves
forward the details will be developed, but for the project charter, high-level information is what should be provided.

The XYZ project will provide increased security to the company’s IT infrastructure and, more specifically, to the company intranet.
The XYZ project will utilize improved technology in the form of security hardware and software in order to prevent external breaches
of the company intranet. All hardware and software will be integrated into the company’s current IT platforms in order to establish
increased security while allowing all systems and processes to continue without interruption.

Page 2 of 7
 PROJECT CHARTER: < PROJECT NAME>

PROJECT OBJECTIVES AND SUCCESS CRITERIA

Objectives should be SMART: Specific, Measurable, Attainable, Realistic, and Time-bound. The project manager must be able to
track these objectives in order to determine if the project is on the path to success. Vague, confusing, and unrealistic objectives make
it difficult to measure progress and success.

The objectives which mutually support the milestones and deliverables for this project have been identified. In order to achieve
success on the XYZ project, the following objectives must be met within the designated time and budget allocations:

 Develop security solution methodology to present to the CIO within the next 20 days.
 Complete list of required hardware/software which meets budget allocation within the next 25 days.
 Create a simulated solution using all purchased hardware and software to test the solution within the next 60 days.
 Achieve a simulated solution which allows no security breaches and complete testing within the next 90 days.
 Implement the solution across the organization within the next 120 days.

REQUIREMENTS

The project team should develop a list of all high-level project requirements. These requirements are clear guidelines within which
the project must conform and may be a result of input from the project sponsor, customer, stakeholders, or the project team.

This project must meet the following list of requirements in order to achieve success.

 The solution must be tested prior to deployment.

 Solution must be implemented without disruption to operations.

Additional requirements may be added as necessary, with project sponsor approval, as the project moves forward.

CONSTRAINTS

Constraints are restrictions or limitations that the project manager must deal with pertaining to people, money, time, or equipment. It
is the project manager’s role to balance these constraints with available resources in order to ensure project success.

The following constraints pertain to the XYZ project:

 All security hardware and software must be compatible with our current IT platforms.
 All hardware and software must be purchased in accordance with the allocated budget and timeline.
 Two IT specialists and one security specialist will be provided as resources for this project.

ASSUMPTIONS

The project team must identify the assumptions they will be working under as the project goes forward. These assumptions are what
the project manager/team expect to have or be made available without anyone specifically stating so.

The following are a list of assumptions. Upon agreement and signature of this document, all parties acknowledge that these
assumptions are true and correct:

 This project has the full support of the project sponsor, stakeholders, and all departments.
 The purpose of this project will be communicated throughout the company prior to deployment.
 The IT manager will provide additional resources if necessary.

PRELIMINARY SCOPE STATEMENT

Page 3 of 7
 PROJECT CHARTER: < PROJECT NAME>

The preliminary scope statement is a general paragraph which highlights what the project will include, any high-level resource or
requirement descriptions, and what will constitute completion of the project. This preliminary scope statement is exactly that:
preliminary. The scope statement should also include information about what will be considered out of scope for the project. All of
this information will be expanded upon in greater detail as the project moves forward and undergoes progressive elaboration.

The XYZ project will include the design, testing, and delivery of an improved intranet security system throughout the organization.
All employee, hardware, and software resources will be managed by the project team. All project work will be independent of daily
and ongoing operations and all required testing will be done within IT. All project funding will be managed by the project manager up
to and including the allocated amounts in this document. Any additional funding requires approval from the project sponsor. This
project will conclude when the final report is submitted within 30 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 CIO.

KEY STEAKHOLDERS & RESOURCES

This section explicitly states who is assigned as the key stakeholders for the project, their responsibilities, and authority level.
Depending on the organization and scope of the project, the project manager may have varying levels of responsibility and authority
for personnel, project expenditures, and scheduling. If a formal RASCI matrix has been established, it should be included here.

The stakeholders for this program primarily include [insert the institutions, departments or over-arching groups of stakeholders]. The
project will utilize the RACI (Responsible, Accountable, Consulted, and Informed) decision rights model to clearly identify the
relationship between project roles. To ensure synchronicity between this program and the various stakeholders, this program is
organized as follows.

The following are the key stakeholders for the project:

Executive Project Sponsor: if applicable

Project Sponsor:

Operations Leader (AKA Key Department Leader):

Project Team: This team meets [indicate frequency of meetings] and will report to the Executive Sponsor [indicate frequency of
reporting]

Project Manager

PROJECT DELIVERABLES

Page 4 of 7
 PROJECT CHARTER: < PROJECT NAME>

This section should list all of the deliverables that the customer, project sponsor, or stakeholders require upon the successful
completion of the project. Every effort must be made to ensure this list includes all deliverables and project sponsor approval must be
required for adding additional deliverables in order to avoid scope creep.

The following deliverables must be met upon the successful completion of the XYZ project. Any changes to these deliverables must
be approved by the project sponsor.

 Fully deployed intranet security solution

 Technical documentation for intranet security solution
 Recommendation list for future security considerations

PROJECT RISKS & MITIGATION STRATEGIES

All projects have some form of risk attached. This section should provide a list of high-level risks that the project team has
determined apply to this project.

Risk Accountability Contingency

CHANGE MANAGEMENT & COMMUNICATION

This section summarizes how project-related communications will occur, with what frequency.

The Project Sponsor and/or the Executive Steering Committee must approve all scope changes which are recommended by the Project
Team. A complete list of issues and scope change requests is maintained ____________. Any approved scope change request is
incorporated into this Project Charter Document and is logged in the Document History Section of this document.

The process for communicating the various aspects of the project will be:

 Written documentation of all project team meetings to be filed ________________.

 Periodically throughout this effort, project updates are given to appropriate groups as requested [Insert meetings here
identified by the Executive Steering Committee: Department Manager Meeting, (Name) Steering Meeting, (Name)
Leadership Board, etc.].

SUMMARY MILESTONE SCHEDULE

Page 5 of 7
 PROJECT CHARTER: < PROJECT NAME>

This section provides an estimated schedule of all high-level project milestones. It is understood that this is an estimate and will
surely change as the project moves forward and the tasks and milestones and their associated requirements are more clearly defined.
The project Summary Milestone Schedule is presented below. As requirements are more clearly defined this schedule may be
modified. Any changes will be communicated through project status meetings by the project manager.

The following is a detailed list of major planning milestones for this project:

Deliverable Original Current Owner

Milestone End Approved
Date Milestone End
Date

SUMMARY BUDGET
The summary budget should contain general cost components and their planned costs. As the project moves forward these costs may
change as all tasks and requirements become clearer. Any changes must be communicated by the project manager.

The following table contains a summary budget based on the planned cost components and estimated costs required for successful
completion of the project.

Project Component Component Cost

Total

PROJECT CHARTER APPROVALS

Page 6 of 7
 PROJECT CHARTER: < PROJECT NAME>

Role Name Signature Date

Executive Sponsor

Project Sponsor

Project Manager

Operational Leader

DOCUMENT HISTORY

Version Date Author Comments

1.0

2.0

3.0

Final Draft

Page 7 of 7