Project Management Documentation - AV
Project documentation needs to be prepared and maintained for appropriate governance and to satisfy process aspects and regulatory requirements. However, the AV Program is organized differently than traditional long-term development projects which pose a challenge on the project documentation set-up.
This section is intended to cover “project management” documentation, not technical documentation.
"Project documents" will exist on 3 different levels:
Stream/“Product”/Component Documentation
- Defined for a “product” or set of components, e.g. AV HMI.
- Shall be updated on demand every time that there is a change in the agreed way of working.
- Shall be reviewed to be up-to-date and to cover all necessary aspects, every time a new release is committed to (M2).
- Shall be updated and re-approved at least once every 24 months (update of living documentation).
Technology Development Project Documentation
- Defined as per the Technology Development Project set-up, e.g. yearly for software projects and deliverable-driven for hardware projects.
- Shall be created and approved as per the project’s gates (G0, G2, etc.)
- Shall be updated and re-approved on demand every time that there has been a change or new committed releases (subprojects) have been added as part of the project scope.
Project Deliverables Documentation
- Defined for a committed release or subproject, e.g. AV HMI for 800xA xP0.
- Shall be created and approved as per the subproject’s milestones (M0, M2, etc.)
- Shall be updated on demand through the subproject’s lifetime (typically M2 to M5).
In case of a Stream/Product Quality Plan: make sure that the plan is up to date and applicable to the scope agreed for your subproject (e.g. 800xA 7.0 xP0). If something is missing, incomplete, or unclear, then update the Stream/Product Quality Plan accordingly.
Organize project documentation
Suggestions on how to organize project documentation for software development as per the categories above:
