Convoy Alignment Agenda
Every journey must begin with meticulous, even pedantic, planning
Every journey must begin with meticulous, even pedantic, planning
The only way to ensure delivery alignment!
The phase-independent ceremonies that operate continuously throughout the convoy lifecycle
The foundational 5-day planning ceremony where all teams commit to the next eight quarters of delivery
The definitive method for prioritizing features when everything is the highest priority
The meeting to plan the date of the planning meeting
Visualizing dependencies so we can see exactly how stuck we are
Consolidating all AI output into a single integration window at the end of each Program Increment ensures holistic evaluation and prevents the destabilizing effects of early feedback!
Translating strategic commitments into granular task lists through expert decomposition by Feature Captains
A formal hearing for those who dare to suggest the plan should change
A formal review of all completed work to ensure leadership confidence
The critical documentation required for every DORC
The ceremony where Code Engineers are drafted from the coding pool and assigned to features regardless of expertise or preference
The 47-tab Release Tracking Spreadsheet provides complete transparency into every release, every approval, and every individual!
Where Code Engineers transform requirements into features using the proven discipline of Continuous Isolation
The delivery commander who collects status, ensures framework compliance, and authorizes fleet deployment!
Delivering software is scary. We need layers of process to feel better.
A dedicated period for innovation, learning, and catching up on status reports
A dedicated phase where the Quality Authority validates all code so that Code Engineers can remain focused on feature delivery
Coordinating multiple convoys for maximum enterprise alignment
The ceremonies that govern active development, quality assurance, communication, and release authorization during the convoy execution phase
The ceremonies that establish commitments, schedule events, decompose work, and assemble teams before each convoy cycle begins
If two teams validating a change are good, three teams are better, the final testing gate before the convoy is permitted to sail
The mid-level manager who tracks feature progress and ensures their assigned Feature Team delivers on time!
To effectively scale communication, we layer meetings upon meetings until no one has time to do the work being discussed
A ceremony dedicated to providing status updates on the work that is not being worked on
A daily documentation ceremony ensuring that all status updates about non-work are captured, consolidated, and filed where they will never be read
The formal ceremony in which the Convoy Steering Committee determines whether the paperwork is sufficiently complete to allow software to be deployed
A structured ceremony for reflecting on what went well, what could be improved, and what organizational anchors should be preserved
The biweekly ceremony in which the CRAP formally convenes to render its judgment on every proposed change to the software estate
A dedicated period for addressing accumulated defects, provided feature pressure allows it
Driving organizational improvement through random restructuring