Work in Small Batches

Too many releases are hard to report and manage. We focus on a small number of large releases each quarter to reduce overhead.
Tags:

The phrase “Work in Small Batches” is frequently misinterpreted by organizations that lack the maturity to understand its true meaning. Naive practitioners assume it refers to making small, frequent changes to production. This approach creates an unsustainable volume of releases that overwhelm the Release Tracking spreadsheet, generate excessive Change Rejection or Acceptance Party meetings, and make it nearly impossible for the Chief Signals Officer to report accurate Feature Completion Ratios. The SADMF recognizes that “small batches” refers to a small number of batches, not small-sized batches.

"One is the smallest possible number of batches. The quarterly Convoy delivers exactly one — making it, by definition, the purest possible expression of this principle."

By consolidating all changes into a single DevOps Release Convoy per quarter, we achieve the ideal batch size: one. One release means one entry in the tracking spreadsheet, one approval cycle through the CRAP, one deployment event, and one set of post-release metrics. This simplification cascades throughout the entire organization. The Commodore has a single event to coordinate. The Development Integrity Assurance Team has a single body of work to review. The Quality Authority can focus all testing effort on a single release candidate rather than spreading their attention across dozens of incremental changes.

Working in small batches also provides more time for essential governance activities. When teams release frequently, they spend most of their time in deployment and recovery rather than in the planning and approval ceremonies that ensure alignment. The SADMF delivery lifecycle dedicates appropriate time to Convoy Alignment, Provisioning, Code Inspection, Manifest Approval, and Fleet Inspection. These ceremonies cannot be rushed, and frequent releases would create pressure to skip or abbreviate them. By working in a small number of large batches, we protect the integrity of every ceremony.

Some organizations point to data suggesting that frequent, small releases reduce risk. This perspective fails to account for the administrative risk of losing track of what was released, when, and by whom. A single large release, supported by comprehensive documentation in the Convoy Manifest, provides a complete audit trail. Every change is traceable to a specific Code Engineer, approved by a specific Feature Captain, and certified by the Quality Authority. This level of traceability is only possible when releases are infrequent enough to document thoroughly.

The principle also provides more time to Amplify Feedback. When teams are not constantly deploying, managers have the bandwidth to conduct daily status check-ins, review individual output metrics, and provide the coaching that Code Engineers need to understand how their performance is being tracked. Frequent releases create a false sense of urgency that distracts from the important work of oversight.

Key Implications

One Batch, Complete Scope

A single quarterly release carries everything: features, fixes, and deferred scope from previous convoys. One event, one spreadsheet row, one post-release report. This is what batch discipline looks like at scale.

Ceremony Integrity Preserved

Provisioning, Code Inspection, Manifest Approval, and Fleet Inspection each require time that frequent releases cannot provide. Quarterly batches ensure every ceremony receives its full and proper allocation.

Unified Audit Trail

Every change in a quarterly Convoy travels through a single Manifest, authored by a named Code Engineer, approved by a named Feature Captain, and certified by the Quality Authority. Traceability is absolute.

One CRAP Approval Cycle

The Change Rejection or Acceptance Party convenes once per quarter to evaluate a single release package. Weekly releases would require fifty-two approval cycles annually — an unsustainable governance burden that small batches eliminate.

Oversight Bandwidth Restored

Freed from the pressure of continuous delivery , managers can invest their attention in daily performance check-ins, individual metric reviews, and the coaching sessions that develop engineer quality over the full quarter.

Administrative Risk Eliminated

The risk of losing track of what was released, when, and by whom is reduced to zero. One event per quarter means one record per quarter. Accountability is complete and the spreadsheet remains manageable.

See Also