Silos are bad. We keep hearing how IT is tribal and divided, with teams that only care about their swim lanes. Sys-admins clash with developers over velocity. Devs don’t take Sec seriously. The storage team doesn’t care about the network. The network team is a bunch of jerks that don’t like anyone. It's a vicious cycle of mistrust and playground cliques.

DevOps hailed as the silo-busting savior, championing unity, emphasizing the purity of code commits and the CI/CD warrior’s path. However, is DevOps truly the liberator or just another silo in disguise: inadvertently reinforcing its own brand of isolation among DevOps teams and engineers?

And what’s worse, this isolation can backfire on the software we produce. Conway’s Law warns us that the way we organize ourselves can shape the software we produce. As silos may end up with poorly designed architectures that accumulate technical debt.

But there's hope. Communities of Practice offer a solution by promoting generative, collaborative innovation, and knowledge-sharing at scale. Join this real-world story to learn how Communities played a crucial role in a vast DevOps transformation, breaking down barriers and driving successful DevSecOps practices throughout our enterprise, and how they can contribute to transforming yours too!