At Scaled Agile DevOps, we believe keeping track of many frequent releases is just too much cognitive load. We need to “work in small batches." We’ve developed the Release Convoy™ to simplify things. Why try to track dozens or hundreds of releases per week if we can simplify it to one easily managed Release Convoy™?
Other frameworks have tried to coordinate things with more limited transportation metaphors. However, they were constrained to a single direction. With Release Convoys™ we have more options. We can turn left or right or even make a U-turn.
Below are the simple ceremonies required to manage changes the SADMF way!
This is a 5-day meeting held every 6 weeks for planning the next 8 quarters of features to make sure the critical paths are aligned.
In this ceremony anyone wishing to change the priorities set in Convoy Alignment must file a PCR and represent it for approval. This allows the Chief Signals Officer to adjust the Completed vs Committed goal to ensure it does not reflect poorly on the Commodore.
Meeting of the Feature Captains to plan the date when the Release Convoy™ will be assembled.
In the Press Gang step, the Feature Captain will choose between 2 and 20 people from the coding pool to “self-organize” around delivering the next feature. This ensures each Coder is given the opportunity to work on new and interesting things and that all Coders are fully utilized.
We understand that only the most important status updates are given in Standup and that some defects are lower priority than some features. To address this, we use the Post Standup Standup ceremony. Here everyone on the Convoy participates to provide status updates to the Commodore on the lower priority work that is not being worked on.
To ensure no information is lost through insufficient documentation, each Feature Captain will also submit a daily report using the SAD Update form and email it to the Commodore who will consolidate it and file it.
To effectively scale communication, we use the Scrum of Scrum of Scrums. First thing in the morning after the daily scrum, each team selects a Tribute to attend the daily Scrum of Scrums. At 12pm your Tribute attends a Scrum with the Tributes from the other teams. They select a Tribute of Tributes from the Scrum of Scrums who, at 3pm, attends a meeting with the Tribute of Tributes of the Scrums of Scrums from the broader organization. They then reverse the process to pass down direction. May the odds be ever in your favor!
The group of Coders assigned to each feature will implement the requirements they are given as rapidly as possible using the industry best practice, Continuous Isolation. This ensures it can be tested and delivered on the Convoy it is planned for. Once the feature is coded, the Coders can return to the coding pool to await their next adventure!.
To keep the Coders productive, we need them to focus only on coding. For unit testing, the Feature Captain will assign the complete feature to the Unit Testing Team to ensure 100% test coverage.
If two teams validating a change are good, three teams are better! This SIT team tests all of the new features of the Convoy together.
The convoy coordinates transportation of the features that were planned. The Commodore is responsible for keeping the convoy together.
We must Build Quality In by removing things that cause poor quality. In this monthly ceremony we identify and remove the person who created each defect.
It’s normal for a little wear and tear to occur when we are moving so quickly. Defects will accumulate. The Dry Dock is the process of halting feature development for a few weeks so that repairs can be made.
We know that a static organizational structure limits improvement and also becomes boring for some executives. While many outside the SADMF community may propose Value Stream Mapping to identify constraints, we know that the process is time consuming and uses too many Post-Its. To resolve these we introduced the Rota Fortunae ceremony where we “spin the wheel”, restructure, and then see if we are delivering better. If we fail, then we convene a Tribunal to address it.
Before any convoy may “leave port”, it’s critical we make sure that all Scaled Agile DevOps processes have been followed. The Delivery Manifest Review Board is convened on the day the fleet sets sail for a final ceremony. All Feature Captains and all of the people involved with each feature assemble beneath the dias of the DMRB. The DMRB will then carefully review the Convoy Manifest and ask probing questions about backout plans and test coverage. Each Feature Captain will also present their PowerPoint presentation detailing the effort required to build the feature to ensure that the importance of the feature is understood. The DMRB will then approve the Convoy’s release and there will be much rejoicing!