The Project Charter

After you have submitted a Web Help Desk Project request, the next step is to work with the appropriate ITS Project Manager and staff to complete a Project Charter. You can use go/itsprojectcharter to get the official Project Charter template. Then make a copy with a new name, the title of your project from the Web Help Desk Project title and make sure to add Project Charter at the end. This charter should be saved in a folder with the same name as a Google doc in the ITS Projects folder in Google.

Below are the various major sections of the Project Charter. Some are mandatory but others you may not need; we do ask that you do not remove unneeded sections but simply put NA next to them if they are not applicable. The more information you can add to the Project Charter, the better ITS can serve your needs. Producing the Charter is very much an iterative process.

The following sections in the Project Charter can be copied from the completed Web Help Desk project ticket: Project Title, Date Needed, Project Vision & Outcome, Project Justification and Organizational Goals.

Technical Specification: Describe in detail the infrastructure, system, or software that has been chosen to fulfill the functional requirements above. Include an effort and duration estimate.

Project Team: Identify the roles that exist for the project, and who is assigned to the roles if they are known. List the roles even if a person to fill the role has not yet been identified. You can also list the project stakeholders.

Project Deliverables: Here you can break down even further the Requirements and Features needed in order to complete the project goals and objectives.

Risks & Assumptions: What are the assumptions you have made, risks and issues and contingency plans to handle them and the constraints that may hinder completion of the project.

Work Breakdown Structure: In this section, usually the Technical lead doing the actual work will use the Project Deliverables and break them down into the technical work components needed to meet the features.

High Level Milestones: Here the team will place the High Level schedule milestone dates.

Communications: Here the team should list stakeholders and their requirements for communicating information about the project and the frequency of those communications.

Vendor: If you project needs to use an outside vendor there are listed in this section assessments to determine the capabilities and gather information on how well the vendor can meet Middlebury’s requirements.

Budget Statement: Here place any budget information as needed by your Project.

Information Security: All project that are being done should take the time to contact InfoSec to determine if there are any concerns and or issues for security.


These sections of the charter can be completed by the Technical Lead, the Functional Lead and or the Project Manager. Usually Charters are a team effort. But the responsibility of completing the Charter lies in the hands of the Project Manager.