|
<br />'lot
<br />
<br />Revised March 24, 2005
<br />
<br />Project Management Plan - Small Project
<br />(Short Form Instructions)
<br />
<br />.11
<br />
<br />1. Objectives: A sentence or phrase which describes the product of this work. A review, a report, a study,
<br />collection of data, a model, an inspection, a design specification, etc.
<br />
<br />2. Scope of 'Work: A sentence or two describing what, when, where, how, how much, and by whom.
<br />
<br />3. Schedule: A list of milestones and who is responsible. Note: can put items and dates that the client is
<br />responsible for providing to which the schedule is dependent.
<br />
<br />4. Financial Plan: A list of tasks, TSC Groups, or tasks and groups and their associated staff days and
<br />non-labor costs. Note: if earned value is to be performed, a second form will be necessary. There is a
<br />range of EV forms and spreadsheets depending on the size and complexity of the project.
<br />
<br />5. Roles and Responsibilities: A list of the key players and their titles and roles. Use separate table when
<br />more than one or two: Project Engineer, Project Technical Specialist, Group Representative, Group
<br />Managers, Team Members, etc.
<br />
<br />6. Quality Control: Describes the quality control process. Client review of work in progress, peer
<br />review, pt:er reviewer, checker, etc.
<br />
<br />:1
<br />
<br />.'.'.
<br />"
<br />'I
<br />
<br />7. Change Management: Describes the change control process to include: forms to be used, thresholds
<br />of change for schedule and budget, use of contingency funding, contingency funds forms, update to
<br />service agreement, etc.
<br />
<br />8. Communication: Lists regularly scheduled team meetings, conference calls, and status reports.
<br />Describes the content, frequency, and distribution of status reports.
<br />
<br />9. Risk Mal1lagement: Identifies potential risks which might affect the project, assesses the impact, and
<br />assigns responsibility for risk.
<br />
<br />10. Project Closeout: Describes what, who, when, how. Identifies how the final product will be delivered,
<br />final reports, feedback survey, team debriefing meeting, client closeout meeting, project records,
<br />financial closeout, etc. Note: may use TSC Project Closeout checklist for reference.
<br />
<br />11. Signatun:s: Must have the Team Leader, Team Leader Supervisor, and Client Contact signatures.
<br />Client Sponsor signature is optional, but strongly advised.
<br />
<br />~ote: Use attachments where more detail is needed. Reference attachments in their appropriate sections.
<br />
<br />Ii
<br />.:
<br />
|