How to convince your company that DevOps is a transitional mode of operations and the means to a goal instead of goal in itself. What comes after DevOps is “done”? DevOps is like learning to drive and a “DevOps Team” is like a motor cycle driving school. You learn in theory and practice to survive amongst “live traffic”, where other road participants are not very considerate. You have to comply with a lot of regulations. From early on you drive your motor cycle alone and the driving instructor follows you in his car keeping a safe distance. He talks with you via radio and tells you where to pay attention and how to drive. But you drive all alone and by yourself - amongst live traffic. If you hit a tree and die, it is your own fault. If you cause a crash, it is your own fault. Same about learning DevOps. You are responsible for your product in production with “live traffic” and real customers. If you crash your server, it your own fault. If your code quality causes harm to the company, it is your own fault. Your DevOps Coach sits next to you and talks to you while you type away at your screen, like a driving instructor. In the end you prove your driving skills, get your license and ride happily singing full speed into the sunset. Same about DevOps, after a training period you work alone. You build it - you run it. You go full speed ahead and deliver value over value. Who has a bumper sticker claiming “I have a driving license”? That’s why “DevOps Team” is a passing thing and once you qualify you are just an Engineering Team who are fully responsible for their product end to end. No need to put a claim to what is normal, because DevOps is normal. Video: https://youtu.be/N2EWEfhQt2M