5 Part 5: V-Modell Reference Work Products
5.3 Products
5.3.2 Planning and Control
5.3.2.7 Project Plan
Process module: Project Management
Responsible: Project Leader (when using process module Project Management)
Activity: Planning Project
Participating: Executive, QA Manager, System Architect, Controller, CM Manager, Logistics Manager
Work Product Attributes: initial
Purpose
A sound project plan is indispensable for the safe and coordinated execution of a project. The project plan describes the selected project approach and specifies in detail what must be done, by whom and when. Thus the project plan is the basis for project control. The »Project Leader is responsible for the project plan, which will be prepared and processed in coordination with all stakeholders.
Generates
Assessment of a Process Model (see product dependency 4.1)
Life Cycle Cost Calculation, Commercial Project Status Report, Product Configuration, Measurement Data, Metrics Analysis, Change Decision, Change Status List, Problem/Change Evaluation, Problem Report / Change Request, Work Order, Meeting Document, Final Project Report, Project Progress Decision, Project Management Infrastructure, Project Status Report, Project Diary, Risk List, Estimation (see product dependency 4.13)
Evaluation Report Product Configuration, Evaluation Specification Product Configuration, Qualification Record, Evaluation Report Document, Evaluation Report Process, Evaluation Specification Document, Evaluation Specification Process, Quality Status Report (see product dependency 4.14)
Depends on
Project Proposal, Project Manual (see product dependency 5.1)
Proposal for the Introduction and Maintenance of an Organization-Specific Process Model, Project Manual (see product dependency 5.8)
Organization-Specific Process Model, Process Model Improvement Concept (see product dependency 5.10)
Requirements Specification, Life Cycle Cost Calculation, Risk List, Estimation, Overall System Specification (see product dependency 5.17)
Change Decision, Change Status List, Problem/Change Evaluation, Problem Report / Change Request (see product dependency 5.29)
Project Progress Decision, Project Manual (see product dependency 5.30)
Work Order (see product dependency 5.31)
Project Manual, Project Status Report, Risk List (see product dependency 5.32)
Hardware Implementation, Integration and Evaluation Concept, Software Implementation, Integration and Evaluation Concept, System Implementation, Integration and Evaluation Concept (see product dependency 5.39)
Contract (see product dependency 5.54)
Example Work Products
5.3.2.7.1 Project Execution Plan
The V-Modell specifies the rough structure of the project by determining appropriate »Decision Gates. This subject is intended to plan these decision gates by developing a project execution plan, which will include at least the beginning and end of the project and all decision gates during the project.
Moreover, additional project-specific milestones may be specified if they are relevant for all stakeholders. Contrary to the »Project Execution Plan in the »Project Manual this plan shows all additional project-specific milestones. In contrast to the »Project Manual, it will not specify the V-Modell products (more exactly: »Product Types), but the project-specific »Product Instances for every decision gate and every project-specific milestone. Thus this project execution plan includes the planning of the »Product Configurations to be developed within the scope of configuration management.
5.3.2.7.2 Integrated Planning
The subject Integrated Planning includes the complete project planning process. The other subjects are only different views on Integrated Planning. They show special planning aspects, e.g., quality assurance planning or planning of »Decision Gates.
During project execution, new facts will arise and the planning parameters will become more concrete. The project planning will then be updated accordingly. Number and frequency of project plan updates will be specified in the Project Manual.
The Integrated Planning includes all planning data known at the respective planning time. Specific data as defined in the »Project Manual will be listed for every element to be planned. Planning data include at least deadlines, efforts, persons responsible and personnel and materiel resources.
The integrated planning comprises the planning of the
- »Product Structure, i.e., the »Product Instances and their connections, and the
- project structure or »Activity Structure in form of »Decision Gates, »Work Packages and »Activity Instance.
The V-Modell does not provide for a subdivision into a product structure plan and a project structure plan. In the course of the project, the entire integrated planning must be updated in order to achieve a consistent planning state. For example, a modification of the product structure normally leads to a change of activity models and, thus, of the project structure.
In the V-Modell, the integrated planning is structured as follows:
- The integrated planning includes the planning of all project-specific decision gates.
- The project-specific work packages are subordinate to the decision gates. They are integrated into a »Project Section, i.e., into the period between two decision gates.
- All activities to be executed within the scope of the project are subordinate to the work packages.
- All product models to be produced within the scope of the V-Modell, i.e., delivery items and project-internal product models, are allocated to the activities.
The integrated planning must include all activity models, product models and project-specific decision gates which are defined in the V-Modell and used in the project. Moreover, additional activity models not included in the V-Modell, e.g., training activities for the project staff, may be integrated.
However, deadlines, resources and efforts need not be planned specifically for all activity models. Instead, project-specific »Work Packages including several activity models can be defined, e.g., a configuration management work package. Deadlines, resources and efforts may be planned at the level of these work packages.
If the planning elements are to small, they may be administered in one action list in accordance with the specifications of the »Project Manual, as described in the product »Work Order.
It would be reasonable to use a computer-based project planning tool for the development of the integrated planning process. Various notations are conceivable for displaying the integrated planning, e.g., Gantt chart, network diagram, table, indented list, organizational chart, or MindMap.
5.3.2.7.3 Evaluation Plan Documents
The »Evaluation Plan Documents includes all appropriate document test activities including the corresponding data, e.g., »Preparing Evaluation Specification Document and »Evaluating Document.
The evaluation plan specifies tasks, responsibilities and required resources. It includes a detailed test schedule for every document.
5.3.2.7.4 Integration and Evaluation Plan System Elements
The »Integration and Evaluation Plan System Elements includes all appropriate system-element-specific integration and test activities with the corresponding data, e.g. Integrating System and »Evaluating System Element.
The integration and evaluation plan specifies tasks, responsibilities and required resources. It includes a detailed test schedule for every system element.
5.3.2.7.5 Evaluation Plan Processes
The »Evaluation Plan Processes includes all process test activities with the corresponding data, e.g., »Preparing Evaluation Specification Process and »Evaluating Process.
The evaluation plan specifies tasks, responsibilities and the required resources, e.g., personnel and tools. It includes the detailed test schedule for every process.
5.3.2.7.6 Training Plan
The »Training Plan includes role-specific and project-specific instructions and follow-on training for qualifying project members. The activities to be planned for this purpose are not included in the V-Modell. They must be planned specifically for the respective project.