Features of PDP Compared with the Past

In the past, successful activities were not documented formally and passed along to other programs. Each program followed a unique process for product development. The Product Delivery Process consolidates the necessary practices of our past and builds on them. This provides a standard process for each program to use as a framework for teams to customize their own implementation plan.

The table below compares features of PDP with processes prior to PDP.

Prior to PDPPDP
  • The General Program Manager had fiscal responsibilities.
  • The program Chief Engineer has overall Quality, Cost, and Delivery responsibilities.
  • The process was approached phase by phase.
  • The process is viewed as a whole. The work for all phases is integrated.
  • The downstream focus was the next step or phase.
  • The downstream focus is the end user customer and the production intent design.
  • Numerous hand-offs of responsibility were required because different people worked in each phase.
  • The subsystem leader has the responsibility from Pre-Concept through Maintenance with activities focused within the PDT.
  • The program team was small in the early phases with gradual build up of functional support. Requirements were viewed one at a time, following the sequence of events. This resulted in numerous design iterations to incorporate each requirement separately.
  • There is front loading in the process. Putting people and resources into the early phases so that many activities can be planned early and in parallel. Multiple customer requirements can be considered simultaneously because process actions are integrated.
  • Process monitoring was less structured and inconsistent.
  • Guidelines provided for PDTs to monitor progress and perform self assessment. MDP provided for management review and agreement to continue program.
  • No formal training plan. No consistent effort to provide new skills.
  • Training provided on process requirements and systems to meet program needs.
  • Enablers were created when the need was recognized.
  • Enablers are emphasized upfront.
[PREVIOUS] [CONTENTS] [NEXT]