On Agile teams, it is common for events or activities to happen based on a regular, predictable rhythm. In software development, one of the most common manifestations of a cadence is the Scrum notion of running consecutive iterations (Sprints) that last for a consistent amount of time (two weeks, for example). Another example of a cadence could be deploying code to a target environment based on a reasonably consistent, often script-driven, time-based pattern.
Related Media
Cadence Video
Cadence Podcasts
Cadence Example
Related Subjects
Acknowledgements
Authored by Philip Rogers
Photo by Lee Pigott on Unsplash
Agile World Resources are provided as free resources to anyone seeking to learn more and are shared under a creative commons attribution license. This means if you use a resource elsewhere you must name Agile World Publishing as the source, who the author is, and the photo creator (if used).