A well-written charter establishes a clear, compelling and shared vision for a new project. This template helps to define project parameters and output and authorize project kickoff.
This form is for documenting any proposed changes to the scope, timeline or budget for a project, including the reasons and impacts if the changes are approved or denied.
Resource forecasting can be used to list anticipated project resource (staffing) needs and to track confirmation of these allocations for the required duration during a project. This template is used to map out and secure project resource (staffing) commitments.
A project schedule is a tool that lists all project milestones, activities and deliverables with associated owners and timelines to completion. A complete schedule helps to communicate the overall effort and duration of a project.
Defining roles among the project team helps identify who is ultimately responsible for managing specific project tasks and establishes a common set of expectations around project accountabilities.
The RAID Log is a single spreadsheet with separate tabs to address the four groups of information related to risks, action items, issues and decisions (RAID). This is a common tool for managing the day-to-day activities of a project.
The purpose of the kickoff is to launch the new project and introduce the team roles and responsibilities to achieve the project objectives and goals.
A meeting agenda is a list of meeting objectives, participants and items that the participants wish to accomplish during the meeting. This template will assist in organizing topics for a productive discussion.
Meeting notes help with communication across the project. This template identifies helpful hints and guidance for keeping record of important discussions and action items.
An essential step of closing out a project is the review and final approval of deliverables completed by various project stakeholders. It may be useful to begin the development of this table once deliverables are identified in the charter and complete the table during the “close” phase.
A project post-mortem, or project closeout, is conducted at the end of the project in order for the project team to review their work and collect lessons learned.