> Delivering teams deliver on the market cadence.
"delivering teams deliver" -- got that. "... on the market cadence" -- err... market. cadence?
"delivering teams deliver" -- got that. "... on the market cadence" -- err... market. cadence?
If you're building a SaaS app, you can release several times a day and users will not notice and be fine.
If you're building a mobile app, you can release maybe 1-2 times a month and users will be fine. If you push out 3 app store updates every day, that is going against the market cadence.
If you're building software for automated machinery, you can release maybe 1-2 times a year. The market will not accept running updates every night.
Without considering the context of your market, saying things like "we need to be doing more CI/CD" or "we need to be working in 2 weeks sprints" or "we'll be ready to release the new version in 18 months" might not make much sense at all.
http://www.se-radio.net/2015/02/episode-221-jez-humble-on-co...
EDIT: HP is covered roughly minutes 8-10.
Also found this, though I'm having trouble getting the video to load to vet it:
https://www.safaribooksonline.com/library/view/continuous-de...
Is continuous integration and automated testing helpful? Yes. Is the cost/effort to move from a process that can deploy monthly to one than deploy hourly worth it? Well, it depends -- if our customers want software updates once per year, then no, it doesn't particularly matter if "master is ALWAYS deployable" or "no builds are failing" on a given day.
TheCoelacanth made a sibling comment to yours which I think addresses the idea very well:
That is in no way in conflict with CI and automated testing. In fact, it would be very difficult to achieve without them.
But that sentence just means "an effective team delivers in time for a product to be useful."
... now that is 5000 euros for my consulting service.
The idea is that you could release, if you wanted to... but there might be good reason not to want to, in a particular market. For instance, a retailer might time the release of certain features around Christmas or summer clearance.
When it all goes to shit, the person brought in to clear up the mess can just tut and state that the problem was that the team wasn't delivering on the market cadence after all.
Very handy term if you want to sound good but don't actually want to change anything.
> Fluent Delivering teams not only focus on business value, they realize that value by shipping as often as their market will accept it. This is called “shipping on the market’s cadence.”