Skip to main content

Standardized Project Management Plan (PMP)

  • Chapter
  • First Online:
Projektmanagement
  • 29k 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

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 119.00
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Author information

Authors and Affiliations

Authors

Appendices

Appendices

22.1.1 Appendix A: 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.1.2 Appendix B: Narrative Progress Report

Date:

indicate the date of publication of the report

Period Covered:

indicate the two dates marking the reporting period

Author:

Project Manager Name (Company)

Contributions:

Contributor A (Company A)

 

Contributor B (Company B)

22.1.3 Appendix C: 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 theMPRas 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 Contractor must keep track of all ongoing tasks of the project

    2. II.

      Provision of theMPRis contractually due [date]. TheMPRisanimportant tool to circulate project information within the team to motivate the team to remain active.

22.1.4 Appendix D. Status List of Deliverables

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.

  • Deliverable Status List: Documents

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

Document Deliverables List

Type of Document

Title

Rev.

File type

First Date of Publication

Last date of Publication

Report

Pilot System Architecture

1.1

MS Word

05 Jan 2001

08 Jun 2001

Report

Pilot Utilization Plan

1.2

Acrobat PDF

03 Jan 2001

05 Jun 2001

Web Page

PROGRAM Web Page

 

HTML

04 May 2001

04 May 2001

  • Deliverable Status List: 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:

22.1.5 Appendix E: 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 Work 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, 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.6 Appendix F: 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 Contractor. See explanation below:

  1. 1.

    Subcontractors shall collect and document WP cost information of the project. These timesheets need 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 sent to PMO of the Contractor for review. The 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.7 Appendix G: Sample Change Notice

Following Fig. 22.5 provides a sample Contract Change Notice.

Fig. 22.5
figure 5

Sample contract change notice

22.1.8 Appendix H: 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

© 2020 Springer-Verlag GmbH Deutschland, ein Teil von Springer Nature

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

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

Download citation

  • DOI: https://doi.org/10.1007/978-3-662-59384-4_22

  • Published:

  • Publisher Name: Springer Vieweg, Berlin, Heidelberg

  • Print ISBN: 978-3-662-59383-7

  • Online ISBN: 978-3-662-59384-4

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

Publish with us

Policies and ethics