[scott_w]

Read above: Accelerate and The State of DevOps are two reads.

From experience, across teams, we deploy probably 20x a day and we're actively trying to deploy more often. Our customer NPS scores are pretty high and our change failure rate is low. We're also a very successful B2B SaaS.

[Scubabear68]

Assuming an 8 hour day, that’s a deployment every 24 minutes, and that’s not good enough?

Why in Earth wouldn’t you coordinate releases? Seems like utter chaos.

[igetspam]

Have you taken the time to read any of the reference material? Have you looked at any of the actual data? Are you aware of how CD with trunk based development works?

You're making assertions that imply you haven't considered anything but your own bias. Your question only works if you have no understanding of how these things actual function

The goal is to reduce the amount of time it takes for a change to land in production. Your eight hour work day implies you have developers only in a single location too, instead of the distributed work force most of us have now.

You seem to be (blissfully?) unaware of how high performing organizations operate.

[scott_w]

Where is your data to backup your assertion that it’s “chaos?” What research can you cite in opposition to the information I’ve provided?

Where are the customer satisfaction surveys that say deploying to production multiple times a day is making their experience worse? Where are the articles showing deploying more reduces revenue? Where is the link between more deployments and reduced reliability?

We’ve provided our evidence, now put up our shut up.