Megan Quinn’s post on Development Cadence starts off really strong:
The hallmark of a well-run development engine is a development cadence that is brisk in bringing new products to market without burning out its builders.
And then it only gets better from there. Her point about being “flexible on scope, fixed on time” is spot on:
One way to establish a good development cadence is to commit to a predictable launch schedule and avoid slipping by pushing out features, not time. Some organizations commit to launching every month with the notion of ticks (small feature releases/fixes) and tocks (bigger, marketable moments).