Coding
Where Code Engineers transform requirements into features using the proven discipline of Continuous Isolation
Execution Ceremonies
The ceremonies that govern active development, quality assurance, communication, and release authorization during the convoy execution phase
Execution Ceremonies govern the active development phase of the DevOps Release Convoy™. They cover the full spectrum of delivery activity: building features, inspecting code, validating quality, maintaining communication across teams, and ultimately authorizing the convoy to sail.
These ceremonies must be completed in the prescribed order. Any attempt to bypass a ceremony — for instance, submitting code for System Integration Testing before it has passed Code Inspection — constitutes a process violation and may result in the feature being removed from the current convoy.
Execution Ceremony Sequence
- Coding — Code Engineers implement features within the fixed timebox using Continuous Isolation.
- Code Inspection — The Code Standards Enforcement Team validates compliance before any code may proceed.
- Testing — The Quality Authority validates all code independently of the engineers who wrote it.
- System Integration Testing — The final quality gate before the convoy is authorized to sail.
- Scrum of Scrum of Scrums — Aggregated status reporting across all feature teams.
- Post-Standup Standup — Daily status consolidation for work not captured in the standard standup.
- Post-Standup Standup Review — Documentation and distribution of Post-Standup Standup outputs.
- Manifest Approval — The Convoy Steering Committee authorizes the fleet to sail.
See Also
- Execution Phase for the full execution phase overview
- Planning Ceremonies for the ceremonies that precede execution
- Beyond the Convoy for the reflection ceremonies that follow
Code Inspection
A rigorous compliance review ensuring all code meets the exacting standards maintained by the Code Standards Enforcement Team
Testing
A dedicated phase where the Quality Authority validates all code so that Code Engineers can remain focused on feature delivery
System Integration Testing
If two teams validating a change are good, three teams are better, the final testing gate before the convoy is permitted to sail
Scrum of Scrum of Scrums
To effectively scale communication, we layer meetings upon meetings until no one has time to do the work being discussed
Post-Standup Standup
A ceremony dedicated to providing status updates on the work that is not being worked on
Post-Standup Standup Review
A daily documentation ceremony ensuring that all status updates about non-work are captured, consolidated, and filed where they will never be read
Manifest Approval
The formal ceremony in which the Convoy Steering Committee determines whether the paperwork is sufficiently complete to allow software to be deployed