Breaking down silos

///Breaking down silos
Breaking down silos 2018-02-13T12:34:22+00:00


In order to understand the critical mistake being made by a vast number of organizations in regard to implementing DevOps, we must look all the way back to the Waterfall methodology and we will see the same mistake has plagued Agile. When we look at Waterfall we see clear and distinct boundaries between departments that have their own silos. Inside these silos we see departments that own their own tools and processes. The creation of silos results in a lack of collaboration, nonstandard tools and disjointed processes. Agile attempted to bridge these boundaries by breaking down some of the silos and moving individuals out of these silos and into cross functional teams.

If done correctly, Agile can be very successful in breaking down these silos and making organizations more productive and nimble, but the truth is that very few organizations have done Agile correctly. If we are honest, what we see is that we still have these same silos inside the Agile teams. In other words, we have programmers who are responsible for creating the application and quality assurance who is responsible for testing. All of these individuals also still report back to the respective silo management where they receive their directions.

What we see today in the DevOps movement is the trend to follow the same mistakes that were made in Agile, the only difference is that these organizations in their infinite wisdom have decided that it’s a great opportunity to create a brand-new silo called the DevOps department and which has a number of DevOps engineers. This idea for creating a new siloed department is almost a guarantee that these organizations will never see the full benefits that DevOps has to offer and most likely they will fall into the ninety percent failure category that the DevOps movement is seeing.