I always took this to be obvious, but I think I saw what might count as an admission in this AWS Devops Training slide text:"Developers change things quickly, release often, and measure success by the rate of delivery. Operations are driven by maintaining stability of the application. Frequent releases are a cause for concern of the stability and reliability of the application on the supported platforms, especially during high network traffic."Another bit of text later on seems to have a typo -- i.e. a bug -- which is just funny:"With DevOps, you can quickly while retaining control and preserving compliance.  Use automated compliance policies, fine-grained controls, and configuration management techniques. Monitor for security incidents and adjust your configurations and software as needed. For example, using policy as code you can define and then track compliance at scale."It's mainly interesting to me because, of the 18Z pro-Agile articles and the 19Z anti-Agile articles I've read, none seemed to talk about this aspect of Agile -- end product reliability.Granted, this AWS course is about 'Devops' -- its culture and processes and tools -- not 'Agile' -- but Devops, to me, is driven by Agile, CI/CD, etc.If it is true that Agile leads to, or can lead to, or has a higher risk of leading to, less reliable software, then I would like to see some more truth in advertising going forward.And, if there is a way to Sprint but still maintain or even increase the reliability of the end product (over/instead of a non-Agile dev process), I'd like to know what those techniques/safeties are.