> Companies that have, "A team that defines the standards, processes, practices, frameworks or architectures that other teams must follow," are amongst the lowest performers. Reversed: companies that lack this, amongst the high performers.
(formatting edited)
1) I'd like to see real data behind this claim. (feels very anecdata and I have reversely correlated anecdata)
2) Companies that have large codebases or large developer populations and don't have any of these things are often headed for disaster.
That's from the state of DevOps surveys. Those aren't causal and define performance oddly.
I'd speculate that companies that benefit from that sort of standardization probably don't care about blindly maximizing deploys/day (maybe nightly plus emergencies is enough) or minimizing time from coding started to deployment finished (maybe a better starting point is when the request is first made, or maybe they're optimizing for development throughout instead).
(formatting edited)
1) I'd like to see real data behind this claim. (feels very anecdata and I have reversely correlated anecdata)
2) Companies that have large codebases or large developer populations and don't have any of these things are often headed for disaster.