Skip to main content

Standardized Project Management Plan (PMP)

  • Chapter
  • First Online:
Projektmanagement
  • 33k Accesses

Zusammenfassung

Bei der Durchführung von Projekten handelt es sich in den meisten Fällen um eine komplexe und äußerst vielseitige Aufgabe, bei der es nicht nur um die methodisch richtige Vorgehensweise, sondern auch um den Umgang mit Kunden, Vorgesetzten, Unterauftragnehmer, Lieferanten und Mitarbeitern geht.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Institutional subscriptions

Similar content being viewed by others

Author information

Authors and Affiliations

Authors

22.1 22.11 Appendices

22.11.1 Appendix I: Meeting Plan

A meeting schedule shall be included showing vertically at the x-axis the types of meetings such as:

  • Annual Top-Level Management Meetings

  • Quarterly Program Review Meetings

  • Monthly Progress Meetings

  • Engineering Meetings

  • Quality Meetings

  • Subcontractor/Supplier Coordination Meetings

Horizontally (y-axis) the exact date(s) of scheduled meetings shall be shown.

22.11.2 Appendix II: Narrative Progress Report

Contract N.: Narrative Progress Report

Table 6

22.1 Activities Performed during the Period

In this paragraph you should provide a summary of the activities performed during the reporting period. Although you are free to adopt your own logical organization, please try to follow these guidelines:

  • Be concise

  • Avoid a report that is too structured (like reporting by Work Packages)

  • Do not keep reporting past issues adding new things to old ones, which are not anymore relevant for the time span covered in the report

  • Consider the MPR as a tool to keep the project team aware of the status of the project

  • Be systematic; provide the MPR on time, and not only during the first months. To summarize, the content of the:

    1. I.

      The Prime Contractor must keep track of all ongoing tasks of the project.

    2. II.

      Provision of the MPR is contractually due [date]. The MPR is an important tool to circulate project information within the team to motivate the team to remain keeps active the responsive.

22.2 Deliverables Status List

This section is dedicated to provide an updated snapshot of the deliverable status. Deliverables cover all documents being produced and items being procured in the frame of the contract.

(1) Deliverable Status List: Documents

A summary table reporting the status of the document deliverable list das to be provided; see example below:

Table 7

(2) Deliverable Status of HW and SW

Provide a summary table reporting any updates (if needed) of the deliverable items (Software and Hardware, developed or procured), following the example below:

Table 8

22.3 (3) Problems Encountered and Proposed/Implemented Corrective Actions

Indicate any problem areas that you encountered and any corrective measures that will be taken.

22.4 (4) Planned Activities for Next Period and Outstanding Issues

Provide a short summary of the activities you plan to undertake for the next period and of any issue that needs to be resolved during project execution.

22.1 22.11.3 Appendix III: Schedule Progress

The following procedure applies to the project for progress reporting. The Template is to be used for the monthly communication of the progress status for the active Wok Packages. See steps to be taken:

  1. 1.

    All due dates are derived from the master schedule.

  2. 2.

    On a monthly basis the subcontractor will have to fill out the Actual Start Date and the Expected Completion Date.

  3. 3.

    In case of a negative variance (delay) the subcontractor will have to estimate whether this delay has an impact on the work package completion date, and/or if so if this delay will impact other work packages.

  4. 4.

    If there is an impact as defined in 4, this must be clearly identified. The impact on other events is to be mentioned.

  5. 5.

    Steps for recovering the delay have to be identified by a recovery plan.

  6. 6.

    It is the required to updated schedules on a monthly basis. Teleconferences are to be held on a biweekly basis or as appropriate.

22.1 22.11.4 Appendix IV: Cost Report

The following procedure applies to the project for cost reporting. The cost reporting allies at company and WP level by using the reported financial data from subcontractors and WP managers of the Prime Contractor. See explanation below:

  1. 1.

    Subcontractors shall collect and document WP cost information of the project. These timesheets needs to be referenced to the appropriate Work Packages.

  2. 2.

    On a monthly basis the summarized WP man-hours shall be prepared and submitted to the project PMO.

  3. 3.

    The hourly rates for labor services have to be agreed with the financial department.

  4. 4.

    Any procurement that is related to the project shall as well be marked in the corresponding field under the Work Package and month of procurement.

  5. 5.

    It is imperative to keep all related documentation for procurements, special cost and work sheets. The Customer will perform audits for which the documentation is required.

  6. 6.

    On a monthly basis the completed Cost Reporting Template shall be send to PMO of the Prime Contractor for review. The Prime Contractor will summarize the inputs on a monthly basis for review by the Customer.

  7. 7.

    The summarized monthly spending will serve as reference for payment of milestones.

22.1 22.11.5 Appendix V: Sample Change Notice

Following Fig. 22.5 provides a sample Contract Change Notice.

Fig. 22.5

Sample Contract Change Notice

22.2 22.12 Acronyms and Abbreviations

AI:

Action Item

AIL:

Action Item List

AIV:

Assembly, Integration and Verification

AR:

Acceptance Review

BPR:

Bi-weekly Progress Report

CAC:

Cost at Completion

CAS:

Cost Account Structure

CCB:

Change Control Board

CCN:

Contract Change Notice

CDR:

Critical Design Review

CDRL:

Contractual Data Requirements List

CEO:

Company Executive Officer

CI:

Configuration Item

CIDL:

Configuration Item data List

COF:

Contract Officer

CTC:

Cost to Completion

ECP:

Engineering Change Proposal

FD:

Formal Document

ICD:

Interface Control Document

IMP:

Information Management Plan

MCP:

Manpower and Cost Plan

MIS:

Management Information System

MOU:

Memorandum Of Understanding

MPB:

Master Program Bar chart

MPR:

Monthly Progress Report

PCM:

Program Control Manager

PDR:

Preliminary Design review

PM:

Program Manager

PMP:

Program Management Plan

PMO:

Program Management Office

PAB:

Program Advisory Board

PSFT:

People Soft

PT:

Product Tree

QCM:

Quality Control Manager

QPR:

Quarterly Progress Report

QR:

Qualification Review

RID:

Review Item Discrepancy

RN:

Running Number

ROF:

Regulatory Officer

RSR:

Risk Status Report

SCM:

Subcontractor Manager

SOW:

Statement of Work

SRR:

System Requirements Review

TEM:

Technical Manager

TS:

Technical Specification

WA:

Work Authorization

WBS:

Work Breakdown Structure

WPD:

Work Package Description

Rights and permissions

Reprints and permissions

Copyright information

© 2017 Springer-Verlag GmbH Deutschland

About this chapter

Cite this chapter

Madauss, BJ. (2017). Standardized Project Management Plan (PMP). In: Projektmanagement. Springer Vieweg, Berlin, Heidelberg. https://doi.org/10.1007/978-3-662-54432-7_22

Download citation

  • DOI: https://doi.org/10.1007/978-3-662-54432-7_22

  • Published:

  • Publisher Name: Springer Vieweg, Berlin, Heidelberg

  • Print ISBN: 978-3-662-54431-0

  • Online ISBN: 978-3-662-54432-7

  • eBook Packages: Computer Science and Engineering (German Language)

Publish with us

Policies and ethics