Continuous Delivery and DevOps - A Quickstart Guide - Third Edition

Changing people's perceptions with pudding

Getting the grass roots to understand this concept should be quite simple when compared to other parts of the business that are, by their very nature, risk-averse.

I'm thinking here of the QA teams, senior managers, project and program managers, and so on. There are a few ways to convince them that risks are being controlled, but the best way is via using the proof of the pudding methodology:

1. Pick a small change and ensure that it is well-publicized around the business
2. Engage the wider business, focusing on the risk-averse, and ensure they are aware; also invite them to observe and contribute (team stand-ups, planning meetings, and so on)
3. Ensure that the engineers working on the change are also ...