Despite its incredible rise in industry mindshare and its age (coming up on six years now), DevOps is a movement that continues to defy definition. Due, in part, to its definition- and manifesto-resistant community, organizations often begin their "DevOps transformation initiatives" without a clear understanding of why they're doing aspects of it, what benefits they will truly realize, and how it's different than strategies the industry has deployed before it (Agile, anyone?). This lack of clarity can also create an environment where the practioners may not be clear on situations "the DevOps" is, in fact, ill equipped to address.
In this talk, we'll examine the dichotomy between DevOps' lack of definition and the commonalities between so many organizations' DevOps journeys. We'll dig into why so many of these rollouts contain strong threads of Lean thinking and why Kanban is such an oft-deployed tool to facilitate the "DevOps transition," to reveal DevOps' actual killer application: organizational visibility.
We'll look at the areas DevOps, through the concrete practices we do talk about, brings visibility to organizations and why that is so powerful in modern software shops. We'll also look at organizational corners that DevOps doesn't necessarily shine a light on, but we can use its core techniques to build even more resilient, agile organizations.