Definitely the key to continuous delivery. Devs avoid deploys when they are difficult or risky; deploys are risky when:
Problems can't be rapidly observed (wait until a customer complains is not rapid)
Recovery actions can't be taken quickly (no rollback, no quick path to merge and deploy new code, onerous access/approval processes)
Instead of taking steps to make mistakes no/low impact; gatekeeping steps are layered atop each other to ensure no mistakes are made, simultaneously ensuring that any mistakes that are missed stay for weeks to months (to years) waiting for a fix to make it through the same gatekeepers.
Software Delivery Futurist.
Chief Storyteller at https://perfectscale.io.
CEO and founder at https://otomato.io.
Co-founder at https://stagecentral.io.
Definitely the key to continuous delivery. Devs avoid deploys when they are difficult or risky; deploys are risky when:
Instead of taking steps to make mistakes no/low impact; gatekeeping steps are layered atop each other to ensure no mistakes are made, simultaneously ensuring that any mistakes that are missed stay for weeks to months (to years) waiting for a fix to make it through the same gatekeepers.
Beautifully put! Lack of usable technology or engineering expertise is compensated for by broken culture. That's the situation we are out to fix.