This is my fourth post in a series I’m writing about impedance to doing continuous delivery. Click these links for earlier parts about the trials of Infrastructure, Solution Complexity and COTS products.
On the subject of Continuous Delivery where the intention is to fail fast, it’s actually rather sloppy of me to defer talking about people my fourth blog on this. When it comes to implementing Continuous Delivery there is nothing more potentially obstructive than people. Or to put things more positively, nothing can have a more positive impact than people!
Here are my top 4 reason that people could cause impedance.
#1 Ignorance A lack understanding and appreciation of Continuous Delivery even among small but perhaps vocal or influential minority can be a large source of impedance. Many Developers and Operators (and a new species of cross-breeds!) have heard of Continuous Delivery and DevOps, but often Project Managers, Architects, Testers…
View original post 817 mots de plus