Back to Beautiful Delivery Standards index <–

Last update: 16 feb 2021

NOTE: copied and tweaked from gove.uk service manual : https://www.gov.uk/service-manual/service-standard/

Introduction

Teams should work together in a collaborative way. An individual team member should be able to release the whole system without any other support and dependency from other teams.

The responsibility of the build process is to integrate (CI) the code and other changes with each other in a controlled and validated way.

Common actions during a build are: merge changes, compile code, validate via unit and other tests, check quality and package, prepare the system for deployment, provide feedback and traceability with work.

Why it’s important

Transparency everywhere.

Traceability is key when selecting tools for keeping up with work. Traceability from idea to running system and back via feedback should be supported by the team-tools in an integrated and automated way.

What it means

• Transparency in the process.
• Tractability from idea to running bits.
• Feedback on running systems incorporated by default.
• Operational data collected continuously by the platform.
• Business usages data continuously gathered by the system.
• A release contains references to finished work, test results, release triggers and has a version.