Creating a Project Charter

profileextaga
BUS530Unit3WordProjectCharterTemplate3.pdf

Doc Number XXXX

Version XX

Print Date 7/17/21

Page Page 1 of 1

Key Consulting Inc, 4848 Railroad Ave NE, Seattle, WA 98105 www.consulting.ky (206) 523-1927 Ver 3.1 ©Copyright 2003

Project Charter

Project Project Name

Created By Your Name Date Creation Date

Phone Your Phone Number Email Your Email

Mission Instructions:

▪ 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 included 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, 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 by executing the project?

Deliverables What will the project actually produce? These should be measurable items.

Stakeholders Who will be on the team? Who is the project sponsor? What other stakeholders have already been identified? Include contact information if possible.

Roles and Responsibilities

Are there some roles/responsibilities that need to be clarified now before the detailed planning begins? Are you clear on your responsibilities as the project manager?

High-Level Work Breakdown Structure

How will the project being structured at a high-level? WBS is similar to an outline of a project. High-level WBS divides project scope into manageable chunks that a project team can understand.

Project Milestone List a reference point that marks a major event in a project

In-scope and out of scope

Define the boundaries of a project. Document what will and will not be included in this project.

Assumptions What high-level assumptions have already been made about the project?

Communications What will be the main channels of communications? Do you anticipate any communication problems that should be clarified here? How often will the team meet?

Risks What are main high-level risks that have already been identified?

Documentation Where will project documentation be kept? How will it be kept up-to-date?

Boundaries Are there specific items that are NOT within the scope of the project?

Budget Include the total amount of money that is allocated for the project to use.