Project Charter

<Project Name>

Document ID PROJECT CHARTER-v0.1

Version Number 0.1
Issue Date April 01, 2020
Classification Public
 805854690.docx <Customer logo>
Version: 0.1

Copyright Notice

© COMPANYNAME, (original issue year – current issue year)

All Rights Reserved

The information contained in this document is the property of COMPANYNAME. No part of

this document may be reproduced, stored in a retrieval system, or transmitted in any form,
or by any means; mechanical, photocopying, recording, or otherwise, without the prior
written consent of COMPANYNAME. Under the law, copying includes translating into
another language or format. Legal action will be taken against any infringement.

The information contained in this document is subject to change without notice and does
not carry any contractual obligation for COMPANYNAME. COMPANYNAME reserves the right
to make changes to any products or services described in this document at any time without
notice. COMPANYNAME shall not be held responsible for the direct or indirect consequences
of the use of the information contained in this document.

805854690.docx Public Page 2 of 19

 805854690.docx <Customer logo>
Version: 0.1

Revision History
Date Version Description Author (s)
04/01/2020 0.1 Draft Version John Doe

Reviewed By (Customer) Signature Date

The reviewer signoff shall signify the recommendation for acceptance of this document.

805854690.docx Public Page 3 of 19

 805854690.docx <Customer logo>
Version: 0.1

Sign Off

Prepared By Acknowledged By

<Name> <Name>
Title: <Position> Title: <Position>
COMPANYNAME COMPANYNAME
Date: Date:

Accepted By Accepted By

<Name> <Name>
Title: <Position> Title: <Position>
<Customer Company Name > <Customer Company Name >
Date: Date:

805854690.docx Public Page 4 of 19

 805854690.docx <Customer logo>
Version: 0.1

Table of Contents

List of Tables......................................................................................................................6

List of Figures.....................................................................................................................7

1 Executive Summary....................................................................................................8

2 Project Purpose/Justification......................................................................................8

2.1 Business Need.........................................................................................................8

2.2 Business Objectives.................................................................................................9

3 Project Description.....................................................................................................9

3.1 Scope Statement.....................................................................................................9

3.2 Project Objectives and Success Criteria.................................................................10
3.3 Requirements........................................................................................................10
3.4 Constraints............................................................................................................11
3.5 Assumptions..........................................................................................................11

4 Risks.........................................................................................................................11

5 Project Deliverables.................................................................................................12

6 Summary Milestone Schedule..................................................................................12

7 Summary Budget......................................................................................................13

8 Organization and Responsibilities.............................................................................14

8.1 Organizational Chart..............................................................................................14

8.2 Project Sponsors....................................................................................................14
8.3 Project Director.....................................................................................................14
8.4 Project Steering Committee...................................................................................15
8.5 Project Stakeholders..............................................................................................16
8.6 Project Team.........................................................................................................17

9 Project Success Factors.............................................................................................18

Appendix..........................................................................................................................19

805854690.docx Public Page 5 of 19

 805854690.docx <Customer logo>
Version: 0.1

List of Tables
Table 1: Summary milestone schedule..................................................................................................13
Table 2: Summary budget.....................................................................................................................13
Table 3: Project sponsors......................................................................................................................14
Table 4: Key project steering committee members...............................................................................16
Table 5: Key project stakeholders.........................................................................................................17
Table 6: Project team staffing estimate.................................................................................................18

805854690.docx Public Page 6 of 19

 805854690.docx <Customer logo>
Version: 0.1

List of Figures

805854690.docx Public Page 7 of 19

 805854690.docx <Customer logo>
Version: 0.1

1 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.
The executive summary should include an overview of the agency’s business functions. This
information is usually gathered by the BA and should include a summary of services and/or
products delivered, key metrics, agency leadership, employee population and geographical
reach.

For the past several years our company intranet has been subject to numerous external
breaches because of poor information technology (IT) security measures. These incidents
have resulted in approximately $10 million in damages to the company. The Intranet
Security Assurance (ISA) project has been created to address and correct these security
issues and prevent further loss due to external IT security breaches. The project will
integrate improved technology solutions with our current platform in order to establish a
more robust security infrastructure.

2 Project Purpose/Justification

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

2.1 Business Need

Discuss the logic for the Business Need (market demand, organizational need, customer
request, technological advance, legal requirement, ecological impacts, social need, etc).

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

805854690.docx Public Page 8 of 19

 805854690.docx <Customer logo>
Version: 0.1

2.2 Business Objectives

This section should list the Business Objectives for the project which should support the
organizational strategic plan. This section should also include the intended effects of the
business case (i.e. cost savings, process improvement, new product development, etc).

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

3 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 ISA project will provide increased security to the company’s IT infrastructure and, more
specifically, to the company intranet. The ISA 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.

3.1 Scope Statement

The 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 scope statement is exactly that: preliminary. All of this information will be
expanded upon in greater detail as the project moves forward and undergoes progressive
elaboration. The scope statement will include what is in scope and what is not in scope.

805854690.docx Public Page 9 of 19

 805854690.docx <Customer logo>
Version: 0.1

The ISA project will include the design, testing, and delivery of an improved intranet security
system throughout the organization. All personnel, 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 in the IT laboratory. All project funding will
be managed by the Senior Project Director 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 VP of Technology.

3.2 Project Objectives and Success Criteria

Objectives should be SMART: Specific, Measurable, Attainable, Realistic, and Time-bound.
The Senior Project Director 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 ISA project, the following objectives must
be met within the designated time and budget allocations:
 Develop security solution methodology to present to the VP of Technology within
the next 20 days
 Complete list of required hardware/software which meets budget allocation within
the next 25 days
 Create a simulated solution in the IT lab 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

3.3 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.
805854690.docx Public Page 10 of 19
 805854690.docx <Customer logo>
Version: 0.1

 The solution must be tested in the IT lab 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.

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

The following constraints pertain to the ISA 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

3.5 Assumptions
The project team must identify the assumptions they will be working under as the project
goes forward. These assumptions are what the Senior Project Director/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

4 Risks

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.

805854690.docx Public Page 11 of 19

 805854690.docx <Customer logo>
Version: 0.1

The following risks for the ISA project have been identified. The Senior Project Director will
determine and employ the necessary risk mitigation/avoidance strategies as appropriate to
minimize the likelihood of these risks:
 Potential disruption to operations during solution deployment
 External threats breaching intranet security via new methods

5 Project Deliverables

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

6 Summary Milestone Schedule

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 Senior Project Director.

805854690.docx Public Page 12 of 19

 805854690.docx <Customer logo>
Version: 0.1

Summary Milestone Schedule – List key project milestones relative to project

start.
Project Milestone Target Date
(mm/dd/yyyy)
 Project Start 01/01/2010
 Complete Solution Design 01/21/2010
 Acquire Hardware and Software 01/26/2010
 Complete Solution Simulation with New 03/01/2010
Hardware/Software
 Complete Solution Simulation and Testing 04/01/2010
 Deploy Solution 05/01/2010
 Project Complete 05/15/2010
Table 1: Summary milestone schedule

7 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 Senior Project Director.

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

Summary Budget – List component project costs

Project Component Component Cost
 Personnel Resources $110,000
 Hardware $45,000
 Software and Licensing $75,000
 IT Lab Preparation $15,000
Total $245,000
Table 2: Summary budget

805854690.docx Public Page 13 of 19

 805854690.docx <Customer logo>
Version: 0.1

8 Organization and Responsibilities

Below is the organizational chart for the project, followed by a description of the roles and
responsibilities for each position.

8.1 Organizational Chart

*Insert Org Chart

8.2 Project Sponsors

The Project Sponsors will provide overall guidance to the project and provide senior-
management direction as needed. Specifics of the role include:

 Actively champion the project and monitor project progress

 Maintain thorough understanding of the project
 Provide senior-level support and guidance
 Assist in removing obstacles to success
 Approve changes to project scope, timing, budget, and charter, as appropriate
 Empower the project team to make decisions
 Make strategic-level decisions and resolve issues in a timely manner

Project Sponsors are:

Name Role

Table 3: Project sponsors

8.3 Project Director

Assigned Project Director
The assigned Senior Project Director for the [Project Name] Project is {Senior Project
Director’s Name.}

805854690.docx Public Page 14 of 19

 805854690.docx <Customer logo>
Version: 0.1

Role
The Senior Project Director is the person responsible for developing, in conjunction with the
Project Sponsor, a definition of the project. The Senior Project Director then ensures that the
project is delivered on time, to budget and to the required quality standard. This person
ensures the project is effectively resourced and manages relationships with a wide range of
groups, including all project contributors.

Responsibilities
The is responsible for managing the work of the project, allocating and utilizing resources in
an efficient manner and maintaining a co-operative, motivated and successful team. The
responsibilities of the Senior Project Director include the following;

 Recruiting project staff and consultants.

 Managing and leading the project team.
 Managing co-ordination of the partners and working groups engaged in project
work.
 Detailed project planning and control including:
 Developing and maintaining a detailed project plan.
 Managing project deliverables in line with the project plan.
 Recording and managing project issues and escalating where necessary.
 Resolving cross-functional issues at project level.
 Managing project scope and change control and escalating issues where necessary.
 Monitoring project progress and performance.
 Providing status reports to the Project Sponsor(s).
 Managing project training within the defined budget.
 Liaison with, and updates progress to, project steering board/senior management.
 Managing project evaluation and dissemination activities.
 Final approval of the design specification.

8.4 Project Steering Committee

Project Steering Committee members are any person or group who is to provide overall
guidance as needed to assure that the program/project meets the goals and objectives. This
committee is comprised of Executive and Business Sponsor and designated stakeholders
representing the affected organizational units.

805854690.docx Public Page 15 of 19

 805854690.docx <Customer logo>
Version: 0.1

Responsibilities

 Reviews and approves program/project deliverables

 Resolves issues or assists with issue resolution when escalation is required
 Supports project resources requirements
 Assists with risk mitigation and helps remove project barriers
 Provides direction on major decisions during project execution, such as change
requests, trade-offs between cost/time/scope, and resource-availability conflicts

Key Project Steering Committee members are:

Name Role

Table 4: Key project steering committee members

8.5 Project Stakeholders

Project Stakeholders are any person or group who has interests which may by impacted,
either positively or negatively, by the performance or completion of the project. The Key
Project Stakeholders identified for the [Project Name] Project are actively involved within
the project and as a result may exert influence over the project's objectives and outcomes.
To account for stakeholder involvement, project deliverables shall require stakeholder
review and approval as appropriate.

Key Project Stakeholders are:

Name Role

805854690.docx Public Page 16 of 19

 805854690.docx <Customer logo>
Version: 0.1

Name Role

Table 5: Key project stakeholders

8.6 Project Team

The [Project Name] Project Team will provide the day-to-day operation of the project and
will:

 Serve as full-time participants on the project

 Participate/lead specific project tasks in accordance with the project plan
 Facilitate work sessions and conduct interviews, as appropriate
 Ensure adequate project documentation is created and maintained
 Perform development of assigned deliverables, and ensure deliverables are
completed on schedule
 Actively participate in developing project work products, refining business
processes, and in developing, implementing and testing system requirements
 Anticipate problems proactively and make recommendations for improvements
 Resolve issues in a timely manner per the project issue escalation policy
 Actively participate in Project Team meetings and status reporting activities
 Review project deliverables in accordance with deliverable review process

Project Team Staffing Estimate

Project Role Participation

Estimate

Project Director 1

Agency Project Manager (if applicable)

805854690.docx Public Page 17 of 19

 805854690.docx <Customer logo>
Version: 0.1

Project Role Participation

Estimate

Table 6: Project team staffing estimate

Participation Estimate: The estimated number of FTEs who will serve on the project within
the given role.

9 Project Success Factors

The organization must understand when the project has reached a successful completion.
These criteria must be clear and should be accepted by whoever will sign-off on the project’s
closeout. Once signed-off by the authorized person, the project is deemed approved and is
successful as long as it has met all of the agreed upon requirements. If there are either
qualitative or quantitative (metrics) measures that the Agency is trying to achieve by
implementing this project, list them here.

Success for the [Project Name] will be achieved 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. Additionally, this measure of success
must include a recommendation list for future security considerations as we fully anticipate
the necessity of this solution to evolve in order to prevent future threats. Success will be
determined by the Project Sponsor, Mr. Jim Thomas, who will also authorize completion of
the project.

805854690.docx Public Page 18 of 19

 805854690.docx <Customer logo>
Version: 0.1

Appendix

805854690.docx Public Page 19 of 19