Execution Ceremonies

The ceremonies that govern active development, quality assurance, communication, and release authorization during the convoy execution phase
Tags:

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

  1. Coding — Code Engineers implement features within the fixed timebox using Continuous Isolation.
  2. Code Inspection — The Code Standards Enforcement Team validates compliance before any code may proceed.
  3. Testing — The Quality Authority validates all code independently of the engineers who wrote it.
  4. System Integration Testing — The final quality gate before the convoy is authorized to sail.
  5. Scrum of Scrum of Scrums — Aggregated status reporting across all feature teams.
  6. Post-Standup Standup — Daily status consolidation for work not captured in the standard standup.
  7. Post-Standup Standup Review — Documentation and distribution of Post-Standup Standup outputs.
  8. Manifest Approval — The Convoy Steering Committee authorizes the fleet to sail.

See Also