Project Charter
Potential Project Name/Title
Start Date
Requested By
Charter Prepared by
End Date
Background & Business Need: State the business problem/issue to solve or what opportunity exists to improve a business
function. What is the current state? Narrative background with drivers for the project.
Project Scope Statement: A concise vision or scope statement that summarizes the purpose and the intent of the project and
describes what the customer (or you) envisions will be delivered. It describes the thing or service that will exist.
Project Objectives/Deliverables: Outline the high-level objectives for the project. What will exist when the project is complete?
Include the benefits of the project, including how the project will benefit the customers or stakeholders.
Boundaries: What will not be included in this project?
1. List the boundaries for this project -- what will not be included in the scope of the effort.
2. List the boundaries for this project -- what will not be included in the scope of the effort.
3. List the boundaries for this project -- what will not be included in the scope of the effort.
Assumptions: What assumptions were made when conceiving this project?
1. Record any assumptions that were made (as opposed to known facts) when conceiving the project.
2. Record any assumptions that were made (as opposed to known facts) when conceiving the project.
3. Record any assumptions that were made (as opposed to known facts) when conceiving the project.
External Dependencies: Note any major external (to the project) dependencies the project must rely upon for success, such as
specific technologies, third-party vendors, development partners, or other business relationships. Also identify any other related projects or
initiatives.
1. Note any major external (to the project) dependencies.
2. Note any major external (to the project) dependencies.
3. Note any major external (to the project) dependencies.
Document1
Page 1 of 2  Version 1.0
Project Charter
Project Risks: List any known risks for the project that could impact the success of the project or should be considered when planning.
1. List any known risks
2. List any known risks
3. List any known risks
Key Stakeholders: List the key stakeholders for the project. Stakeholders are individuals, groups, or organizations that are actively
involved in a project, are affected by its outcome, or can influence its outcome. Indicate their role or interest in the project. These
stakeholders (or representatives) will be invited to participate in a project kick-off session, but do not necessarily need to be on the project
team.
Stakeholder
Role or Interest in the Project
Required Resources: Identify the known resources that management is willing to commit to the project at this time. Human resources
include key individuals, teams, organizations, subcontractors or vendors, and support functions. This is not the place for the detailed team
staff roster for individual names. Identify critical skill sets that team members must have. Other resources could include funding, computers,
other equipment, physical facilities such as buildings and rooms, hardware devices, software tools, and training.
Requested Timeline/Milestones: Include end and start dates and key milestones.
Approvals
Document1
Date
Date
Date
Date
Page 2 of 2  Version 1.0