TEMPLATE: TM-PP-01 (V2.0), PROJECT MANAGEMENT PLAN (24-MAY-2005)
TEMPLATE: TM-PP-01 (V2.0), PROJECT MANAGEMENT PLAN (24-MAY-2005)., This template provides the format and content of a Project Management Plan (PMP) for a mid-sized project (e.g., 5 to 20 staff members). Typically, larger projects will receive explicit direction from the sponsor on planning documentation requirements. Smaller projects may use a scaled-down version of this template. The template is considered flexible enough that it may be used for any type of project.
This document is part of a trilogy of sample documents and templates intended to support the guidance provided by the SSC San Diego Project Management Guide (PMG). Figure A provides an abstract of the PMG\'s project management functions of Initiation, Planning, Control, Execution, and Close Out. As depicted in Figure A, the Planning Function includes the development of plans to facilitate both the Control Function and the Execution Function. Three documents available from the Space and Naval Warfare (SPAWAR) Systems Center (SSC) San Diego Process Asset Library (PAL) Web site at http://sepo.spawar.navy.mil/ are recommended for the implementation of the concepts presented in the PMG. While these documents are not the only means or document selections that can facilitate this process, they are considered a \"Best Practice\" and can be tailored during the Planning Function to guide the Control Function and Execution Function. This trilogy of documents includes those listed below: Trilogy Part 1. Project Management Plan (PMP) Template, TM-PP-01 (this document). Control function planning requires a defined Management Solution, documented in a format such as the IEEE Standard for Software Management Plans, IEEE Std 1058-1998. The PMP addresses such issues as budget, budget control, schedule, schedule control, staffing, risk management, configuration management, quality assurance, and project tracking measurements.
Trilogy Part 2. Product Engineering and Qualification (PE&Q) Process, PR-TS-01. Planning for the Execution function results in documented engineering and qualification processes needed to implement a projectís work product(s). The PE&Q Process represents an example of the level of detail needed for these processes. The PE&Q Process represents one method of defining an engineering process. Other process definition methods could include, but are not limited to, data flow diagrams, Entry-Task-Verification &Validation-Exit (ETVX) diagrams, Integrated Computer Aided Manufacturing Definition (IDEF) 0 or IDEF 3 diagrams for process flow, etc.
Trilogy Part 3. Project Build Plan Template, TM-PP-02. Planning for the functional content of the projectís work product should result in a document as typified by the Project Build Plan Template. This document defines the product content in terms of functional requirements to be delivered, the acceptance criteria, fielding direction, and user training needs. This document could serve as a contract between the acquirer and the supplier for any given deliverable increment of the product. Other build plan methodologies could include, but are not limited to, use of the MIL-STD 498 Data Item Description (DID) for Software Version Description (SVD), or detailed project plans itemizing the product content.
These three documents are an integral part of the SSC San Diego-approved life cycle strategies as defined in A Description of the SSC San Diego Standard Process Assets (SPA). These documents are available on the SSC San Diego PAL Web site along with the SPA itself.
SSC San Diego has assigned the responsibility for this document to the Systems Engineering Process Office (SEPO). SEPO welcomes and solicits feedback from users of this document so that future revisions of this document will reflect improvements, based on organizational experience and lessons learned. Questions or comments regarding this document may be communicated to SEPO via the Document Change Request form located on the next page or submitted online via the SSC San Diego PAL. Updates to this document are performed in accordance with the SEPO Configuration Management Procedure.