Previous Next V-Model Official Homepage by IABG  
PM Homepage  
8.5.2 Project Plan (PPl)  


  • Introduction
  • Document Index
  • Document Structure
  • Links to V-Model the Mailinglist
  • Introduction

    The Project Plan comprises planning and specification of the realization of the project, scheduling, and resource planning for all submodels. It is an instrument for planning, steering and control by the project management.

    Document Index

    1. General Information
    2. Project Realization
          2.1. Product Structure Plan
          2.2. Process Organization
    3. Efforts Plan and Time Schedule
          3.1. Preliminary Plan
                3.1.1. Efforts (Planned and Actual) for SD/QA/CM/PM Activities
                3.1.2. Deadlines (Planned and Actual) for SD/QA/CM/PM Activities
                3.1.3. Milestone Plan
                3.1.4. Baselines
                3.1.5. Phase Reviews
                3.1.6. Delivery and Supply Deadlines
          3.2. Detailed Plan
                3.2.1. Planned Values
                3.2.2. Actual Values
    4. Resource Plan
          4.1. Staff
          4.2. Resources
                4.2.1. Infrastructure
                4.2.2. Equipment and Load of HW, System SW and Tools
                4.2.3. Devices
    5. Risk Considerations
          5.1. Risk Estimation
          5.2. Measures to Lessen or Prevent Risks

    Document Structure

    1. General Information

    See schema 1. General Information.

    2. Project Realization

    This chapter contains a description of the product structure of the development product that is the basis for the organization of the project realization.

    2. 1. Product Structure Plan

    All products known at a certain planning stage are identified; their interdepencies (structure) are specified. In this connection, it is important to check the consistency with the Configuration Identification Document (CID).

    Two different aspects have to be covered in the description: the documentation of the System generated during the development stages (requirements, design, etc.) and the technical structure of the System (SW Modules, SW Components, etc.).

    This chapter contains both the products defined as part of the contract and the "internal" products.

    2. 2. Process Organization

    The generic activities stated in the c are allocated to the products specified in the product structure plan. This is an instantiation of the activities. For example, it is no longer referred to the activity "Detailed Design", but exactly to activity "Detailed Design of SW Component xy". In order to plan and control the project realization, the instantiated activities have to be represented in their interrelationships.

    3. Efforts Plan and Time Schedule

    This plan determines which tasks have to be realized to what date and what effort should be made.

    3. 1. Preliminary Plan

    This plan is oriented at the instantiated main activities and contains the corresponding planning data in a first approximation.

    3. 1. 1. Efforts (Planned and Actual) for SD/QA/CM/PM Activities

    The time required will be determined for all project activities (even for the PM itself!).

    Before starting with the activities, the planned efforts must be given here. After completing the activities the time actually used will be compared with the planned time; this can be done by using a table or diagram.

    3. 1. 2. Deadlines (Planned and Actual) for SD/QA/CM/PM Activities

    The planned deadlines will be determined by means of the time required and the specified dependencies of the activities. After completing the activities, the comparison between planned and actual time consumed will be given, just as above, in a tabular or graphic way.

    3. 1. 3. Milestone Plan

    Important deadlines will be made into milestones, e. g. the completion of the design, the realization of a prototype or a system part. The completion of a baseline also defines a milestone.
    (See Mail 0284-Re: Projektplan (284))

    3. 1. 4. Baselines

    Products representing a defined starting point for subsequent development steps, subcontracts or further developments are combined into a baseline. A baseline defines a break-off point for the project. It is to be stated here which baselines are required and which products are allocated to these baselines.
    (See Mail 0284-Re: Projektplan (284))

    3. 1. 5. Phase Reviews

    The schedule, personnel and organizational planning of the Phase Reviews is defined:

    3. 1. 6. Delivery and Supply Deadlines

    This chapter has to list all those deadlines which also refer to external project groups, i. e. deliveries of products to the customer, supplies from subcontractors, common activities (e. g. proof tests) of several contractors, provision of products to subcontractors, etc. The following must be answered: who delivers to whom, what is delivered, when and how it is delivered.

    3. 2. Detailed Plan

    This plan details the preliminary plan, down to the deepest activity level specific to the project.

    In order to compare the planned effort with actual effort and time used it would be advisable to generate a table or diagram. This way, prognostics about the future course of the project can be made, and management decisions can be documented.

    3. 2. 1. Planned Values

    This must contain the specification of the planned efforts and deadlines. The planned efforts mainly refer to staff. With regard to planned deadlines will be defined.

    3. 2. 2. Actual Values

    This chapter contains actual efforts and actual deadlines (start and end). The actual values of efforts or deadlines must be delivered by all participating in the project.

    4. Resource Plan

    Resources comprise the staff and technical resources.

    4. 1. Staff

    The project activities will be allocated to the available staff members, corresponding to their qualification, classification qualification and availability.

    4. 2. Resources

    It will be defined which resources will be used, when and to what extent the resources will be required. This planning must correspond to the course of the project, and its deadlines have to be observed and updated.

    4. 2. 1. Infrastructure

    This comprises, e. g., offices, meeting rooms, telephone, telefax, copiers, blackboards.

    4. 2. 2. Equipment and Load of HW, System SW and Tools

    This lists the individual components of the development and assessment environments as well as, for example, the required network, direct line to the customer.

    4. 2. 3. Devices

    If special devices are required for the project then they have to be listed here.

    5. Risk Considerations

    5. 1. Risk Estimation

    Based on the project planning and the technical feasibility studies any risk-prone situations will be protocoled and analyzed with regard to their possible effects and the probability of their occurring.

    5. 2. Measures to Lessen or Prevent Risks

    All measures applying to the project which can prevent problems must be listed. The measures must be rated for priority on the basis of their suitability, i. e. how they prevent the problems. Furthermore, appropriate measures which can compensate for problems that have already occurred must be listed.

    Links to the V-Model Mailinglist

    Mail 0595 - Re: Unterstützung der Betriebseinführung (595)
    Mail 0591 - Durchführungsentscheidung (591)
    Mail 0589 - Produktbibliothek & KM-Plan: Wo steht die Produktliste ? (589)
    Mail 0322-KM 1.1: KM-Plan erstellen (322)
    Mail 0287-Re: Projektplan (287)
    Mail 0284-Re: Projektplan (284)
    Mail 0283-Re: Projektplan (283)
    Mail 0277-Re: Projektplan (277)
    Mail 0274-Projektplan (274)
    Mail 0173-Re: QS-Plan nach V-Modell 97 (173)

    Previous Next This page online  •  GDPA Online  •  Last Updated 18.Aug.2002 by C. Freericks