Delivery cadence

Q: How deeply does Think Like a Software Engineering Manager cover delivery cadence?

Defines cadence and explains its operational benefits, but does not specify a numerical release frequency.

As explained in Think Like a Software Engineering Manager

Deployment cadence is the regularity and planned frequency with which software changes are released.

Delivery cadence is the regular, planned frequency of releasing software changes to production. A steady cadence keeps changes from accumulating and makes deployments easier to manage than a single big-bang release. section 12.2.4

A regular cadence helps teams:

Prevent large batches of unreleased changes from accumulating in preproduction. section 12.2.4
Isolate problems more easily when a deployment fails. section 12.2.4
Promote a smoother and more efficient deployment process through team agreement. section 12.2.4

A boring deployment

A robust delivery process makes releases routine: the team clicks a few buttons, changes go live, and the deployment produces little drama. Automation and automated change control support this consistency. section 12.2.4

How Think Like a Software Engineering Manager covers it

Cover of Think Like a Software Engineering Manager

liveBook manning.com

Read Think Like a Software Engineering Manager on liveBook Get the book at manning.com

Related concepts

cognitive loadmeasures · Cognitive load is the mental effort required to process information, retain it in working memory, or perform a task.
releaseconfigures · A software release is a version or set of changes made available to intended recipients for deployment or use.
modernization initiativemeasures · A modernization initiative is a planned effort to update existing software, technology, architecture, or organizational capabilities to meet current needs.

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.