Captain's Mast
A formal hearing for those who dare to suggest the plan should change
Standing Ceremonies are the DevOps Release Convoy™ ceremonies that operate independently of any particular convoy phase. While Planning Ceremonies, Execution Ceremonies, and Reflection Ceremonies are tied to specific moments in the convoy lifecycle, Standing Ceremonies run continuously — some on fixed schedules, others on an as-needed basis — providing the governance structures and accountability mechanisms that hold the convoy together from start to finish.
Change Adjudication Convening — Operates on a fixed biweekly cadence, independent of Convoy phase, serving as the standing gate through which all changes must pass before inclusion in any fleet. The biweekly schedule ensures that no change ever waits more than two weeks for a hearing, and no change ever bypasses deliberation.
Tribunal — Maintains organizational health through accountability. The Tribunal convenes whenever sufficient evidence of process non-compliance, delivery shortfall, or attitude misalignment has been accumulated. Its timing is independent of the convoy cycle, ensuring that accountability is never delayed by the schedule.
Rota Fortunae — Provides periodic restructuring to ensure that no organizational structure becomes too comfortable. The Rota Fortunae operates on its own cadence, independent of convoy phases, reflecting the SADMF principle that the wheel of organizational fortune must turn continuously to prevent stagnation.
Captains’ Mast — Addresses priority challenges and escalations that cannot wait for a scheduled ceremony. Captains’ Mast may be convened at any point during the convoy cycle when a Feature Captain requires immediate arbitration.
Standing Ceremonies complement but do not replace the phase-specific ceremonies. Practitioners should consult the appropriate phase ceremony pages for the ceremonies that govern each stage of the convoy lifecycle:
A formal hearing for those who dare to suggest the plan should change
The biweekly ceremony in which the CRAP formally convenes to render its judgment on every proposed change to the software estate
Driving organizational improvement through random restructuring
Building quality in by identifying and removing the person responsible for each defect