Release
The Release process is valid for component, product, and system releases, including limited releases such as roll-ups and expansion packs. It deploys new functionality into production - continuously or on demand - and ensures that all R&D deliverables are ready to release.
Process Overview
Principles
- Establish release content and associated parts to be released.
- Determine the delivery media type for the release.
- Manage the maturity of the release through the release stages.
- Ensure readiness of the release documentation (3rd-party clearance, cyber security assessment, export control, standards, certificates, etc.).
- Ensure product release approval before delivery.
- Provide a release note detailing key characteristics of the release.
Activities
Artifacts
| Artifact | Description | RACI | Receiver | Comments |
|---|---|---|---|---|
| Project Description & Plan | "Project Plan" focused on a release | See IPM process | R&D | Responsibility of IPM |
| Document Control Plan | List of documents corresponding to a release. Two variants - one for the project, and one for user manuals. | See IPM process | R&D | Responsibility of IPM |
| Release Version | Software/hardware version for release. | (R): Release Owner (A): Stream Owner (C): - (I): - | Operations | - |
| User Documentation | End-user documentation about system, product, or application. | (R): Product Owner (A): Product Manager (C): Development Team, Product Owner, Test Lead, Safety Engineer (I): Configuration Manager | PPM | - |
| Release Notes | Summary of the release content, major issues and work-around. | (R): Release Owner (A): Stream Owner (C): Development Team, Ex Representative, Release Owner, Technical Coordinator, Test Lead, Safety Engineer, Product Manager (I): Configuration Manager, Ex Component Responsible | Operations | - |
| Certificates | Certificates for the releases (Safety, UL, CSA, GM, CE, etc.). | (R): Release Owner (A): - (C): - (I): - | PPM | Responsibility of Certificates |
| Export Control Artifacts | Provide the basic information for ECCN classification. | See RACI for details. | PPM | PPM responsible, input from R&D |
| 3rd-party IP Risk Analysis | Legal evaluation of the risks from 3rd-party intellectual property. Also called "Freedom to Operate" or "Clearance". | See Intellectual Property process | R&D, PPM | Responsibility of Intellectual Property |
| IP Risk Register | Record project IP risks; update according to gate status. | See Intellectual Property process | R&D | Responsibility of Intellectual Property |
| IP Strategy Report | Project-specific report identifying key areas to focus IP protection efforts on. | See Intellectual Property process | R&D, PPM | Responsibility of Intellectual Property |
| OSS Scan & Clearance Report | OSS Clearance report from Black Duck. | (R): Release Owner (A): Stream Owner (C): - (I): - | Stream Owner | Responsibility of 3rd-Party and OSS |
| Security Assessment Report | Approved security assessment reports for the release. | (R): Cyber Security Engineer (A): Head of Cyber Security (C): Head of Cyber Security (I): 3rd party SW engineer, Architect, Development Team, Product Owner, Release Owner, Stream Owner | PPM | Responsibility of Cyber Security |
| Beta Version | Software/hardware version for beta installation. | (R): Release Owner (A): Stream Owner (C): - (I): - | PPM | - |
| Beta Site Test Report | Feedback from the beta-site is recorded in a test report. | (R): Release Owner (A): Stream Owner (C): - (I): - | PPM | PPM responsible, input from R&D. |
| Field Upgrade Plan | Plan for upgrading beta sites to the released system and products. | (R): Release Owner (A): Stream Owner (C): - (I): - | PPM | PPM responsible input from R&D. |
Dependencies
References
- TBD
Related
Owner: Release Team