Document List
Overview
Use documents from the list as needed and applicable to your project. Full documentation is categorized/chosen according to Project Sizing Matrix Tool.
Complete List
The complete set of deliverables is included in the subsequent table, listed by project phase.
Phase: INITIATION
Stakeholder Matrix includes all persons and representatives directly involved, impacted or with some level of interest in the project and its outcome.
RACI describes the participation by various roles in completing tasks or deliverables for a project.
Phase: PLANNING
Project scope is the part of project planning that involves determining and documenting a list of specific project goals, deliverables, features, functions, tasks, deadlines, and ultimately costs. In other words, it is what needs to be achieved and the work that must be done to deliver a project.
This document is used to track risks and issues, including impact, response strategy and preventive actions. It could also include probability and impact grade, which derives in a risk score.
The following are sample documents for budget tracking within a project.
This deliverable has a matrix format, structuring communication types needed (meetings, reports, conference calls, etc.), their objectives, frequency, medium, audience, owners and corresponding deliverables.
Phase: EXECUTION AND CONTROL
The Project Plan is a formal, approved document used to guide both project execution and project control. The primary uses of the plan are to document planning assumptions and decisions, facilitate communication among stakeholders, and document approved scope, cost, and schedule baselines. By showing the major products, milestones, activities and resources required on the project, it is also a statement of how and when a project's objectives are to be achieved.
The project manager creates the plan following input from the project team and key stakeholders. The plan should be agreed on by at least the project team and its key stakeholders.
The Project Transition to Operations and Support Plan is used to ensure that deliverables of the project will be brought to and remain in full operational status, integrated into ongoing operations and maintained in a sustainable manner.
TBD
- IT Transition to Operations Document
Cutover refers to the phase when the project goes into production. Project cutover is an activity which is actually the series of tasks that are performed to deploy the components from the development/Pre-production environment to the Production environment and activate them.
Backout is an IT approach that specifies the processes required to restore a system to its original or earlier state, in the event of failed or aborted implementation.
Phase : CLOSURE
This should be the last document of the project, listing objectives and justifications, remaining issues and statuses, maintenance plans, project improvements, and a project close check-list.
Change Management Document
Detailed report with recently completed and delayed tasks, including issues list and actions to correct them. This document should also include announcements and reminders of project meetings.
Meeting Minutes
This document includes meeting dates (time, location), materials, and list of attendees, key decisions, and action items.