pm7 Project Plan hri07e
note: this page is not compliant with hri07e CDID km3 and needs to be revised
1.0 Title: PROJECT PLAN
2.0 Purpose: A project plan presents a graphical representation of a project that illustrates the complexity and duration of a project as well as the order in which tasks should be performed. A well presented project plan can be a very effective as the basic tool for describing the project and can replace much more wordy versions sometimes presented in proposals.
3.0 Recommended Usage: Project Plans should be created for all but the most trivial of projects, even those having as few as 5 or 6 activities.
4.0 Frequency: A draft or preliminary plan should be created prior to preparation of any proposals. An "Approved" version should accompany the final contract or letter of offer. After the project begins the plan should be revised at each milestone, or at any time it becomes apparent that it no longer represents what is happening in the project, or every 6 months ; whichever is less.
5.0 Reference Documents:
CDID03 - Statement of Work (SOW)
CDID04 - Task Summary
6.0 Responsibility: The IRAP Client Project Manager is responsible for the accuracy, coordination and timeliness of all project plans including those of sub-contractors, even where the sub-contractor has been assigned to produce their own plans.
7.0 Ownership: Project Plans are the intellectual and physical property of the client or his sub-contractor unless otherwise negotiated.
8.0 CONTENTS:
Any standard type of chart (CPM, GANTT,etc.) is acceptable or negotiable.
Data normally found on the plan includes, but is not necessarily limited to:
- Task (or sub-project or sub-task, etc. as applicable) ID no.
- Task Label (i.e. 2 or 3 words or mnemonics)
- Time scale
- Project references & titles
- Revision Date & Status
- Task Status indication (as of revision date)
- Milestone ID's and Labels
and might also include - (provided there is room)
- Task Responsibility ID (with legend if not obvious)
- Task Dependencies
- Estimated, Actual, Forecast hours (as of revision date)
Data shown in the Task Summary forms (CDID04) need not be repeated on the plan except for Project references and Task ID's. For IRAP purposes, milestone events should relate to the invoicing for the project and coincide with project reports.