The project charter is the first step in initiating a project. It collects essential information for the project into a single document and includes these sections:
1) Problem / opportunity statement:
In 25 words or less, summarize the problem or opportunity you propose to address. This statement provides a basis for the rest of the document. Write this in terms of the organizational problem discovered, not in terms of the solution needed
2) Proposed Solution:
This is the solution you propose to address the problem or opportunity identified above. A project has one goal that gives purpose and direction to the project. This will be used as a continual point of reference for any questions that arise regarding scope or purpose. This section should be written in language that is easy for everyone to understand. It describes what will be implemented, corrected, installed, replaced or otherwise addressed to solve the problem
3) Scope and strategy:
How will you complete this project? What is your strategy for completion?
What tools will you use? Will you procure or otherwise acquire hardware, software or people services?
Are there alternative methods that you ruled out? Why?
What should be considered as NOT in scope?
4) Objectives and Deliverables:
Objectives and deliverables are a detailed version of the purpose. They outline what will be accomplished in the scope of the project as well as what won’t be accomplished
Think of objectives as steps needed to complete the project
Think of deliverables as artifacts of the objects. Some objects may have multiple deliverables
5) Success Criteria:
This is the measurable business value resulting from doing this project
What state must exist for the campus to say the project was a success?
Address quantitative and tangible business benefits in terms of what will be improved, what problems will be reduced or what benefit will this be to the College
6) Constraints and Limitations:
Inter-dependencies with other projects
Date constraints
Government, Industry or College regulatory requirements
Skill set requirements, level of experience required, customer, etc.
7) Risks and Opportunities:
Identify any factors that can affect the outcome of the project including major dependencies on other events or actions
These factors can affect deliverables, success, and completion of the project
Record anything that can go wrong during this project and the probability
8) Resources needed Estimates:
Startup and one-time expenses? Equipment needed? Resources needed after project is completed to maintain? Do you have access to resources currently to fill these needs, or do you have a plan to acquire them?
9) Expected Benefits:
List direct tangible benefits
Will this project reduce the need for future projects?
Are there any indirect benefits outside of solving the problem statement?
Additionally, there is a Governance Justification sections to the charter that speaks to how the project will provide benefit to the College based on the rubric. When charters are rated by the ESAC membership, it is these Governance Justification criteria that are primarily used to provide a rating.