Notes on Applicability
The following documents have been found useful by many project initiating organizations. Some practitioners favoring light methodologies will use a minimal subset of the suggested list and mostly in abbreviated format. Other organizations will complement with more detailed documents. In any case, it is intended to serve as a guide and a checklist to the Project Manager, and not as a norm.
The presentation has been structured according to Process Groups for lack of a better way.
It is expected that most document contents are not static and will be updated and expanded during the course of the project.
Click a document name to visualize/print the suggested Table of Contents (TOC).
Initiating
This is the initial authorizing document. The Project Charter formally recognizes the existence of the project. It covers the business needs addressed by the project and a summary description of the proposed solution.
The Project Charter is normally issued by a high-level manager external to the project. It authorizes the Project Manager to use organizational resources for project planning activities.
Planning
The Project Plan is an approved collection of documents used to manage project execution.
The Project Plan should be expected to change over time as additional and more specific information becomes available. Certain elements, like performance measurement baselines and WBS, will generally change following a formal process in response to an approved scope change.
The Project Schedule as well as the Subsidiary Management Plans are normally issued as separate documents to facilitate the day to day use and a more frequent update cycle.
The level of detail could vary from document to document depending on the initiating organization accepted norm or the use of specific development models (Agile model).
Scope Statement (Creative Brief)
Work Breakdown Structure (WBS)
Project Schedule
Subsidiary Management Plans
Scope Management Plan
Schedule Management Plan
Cost Management Plan
Quality Management Plan
Staffing Management Plan
Training Plan
Communications Management Plan
Risk Management Plan
Contingency Plan
Procurement Management Plan
Content Management Plan
Site Maintenance Plan
Configuration Management Plan
Executing
Web Strategy Report
This document covers the Web site structure and why it is so organized.
It is used during the Maintenance Phase to insure continuity in the original goals and avoid architectural drift.
To complement the Architecture Style Guide, the maintainers are also provided with a distinct, more technically oriented Design Style Guide issued separately.
This document covers the graphical treatments of the Web site.
This Style Guide is essential to maintain visual design consistency during the Production Phase as well as the Maintenance Phase.
It is started early and created in part by the Graphic Design Team and completed by the Technology Team during the Production Phase.
Internationalization Design Standards
Lessons learned
Controlling
Performance Reports
Minutes of Meetings
Change Orders
Anomaly Reports
Closing
Contract Files
Formal Project Acceptance
Project Archives