Flow - A Way Towards DevOps Culture in the Legacy Enterprise

DevOps is a very popular buzzword. Many people associate it with tools like Chef, Puppet, Continuous Deployment etc. But DevOps is really a higher form of agility. It is a blueprint for a great culture and and process between the different groups involved in the delivery pipeline. The big question is how to achieve it. If you are founding a startup today, it can be quite easy to take that blueprint and use it to create your process, hire the right versatile flexible people, and start delivering without any technical/automation debt or friction. But most of us are not founding new startups. Most of us already have a running operation with people, culture, process that matured over the years and despite its flaws is currently the way we do things. Changing that is non-trivial.

For things to change people need to understand WHY change, what we are changing, and we need an effective process for managing the change itself (HOW to change). So what ARE we changing to? DevOps is highly focused on looking at the whole value stream from idea to value and ensuring effective flow through this pipeline.

Kanban is ONE way of HOW to change towards an end to end flow. It starts by visualizing all the work flowing in the pipeline, then managing the flow focusing on finishing things end to end rather than starting in order to stay busy. It continues to what we call the “Work in process Diet” – Straining the flow more and more in order to identify obstacles to tighter and tighter DevOps culture/operation and faster feedback cycles. You can expect to come out of this session with ideas how to take your current operation and DevOpsify it in a safe evolutionary way using the Kanban method as well as an understanding WHY DevOps tools are required as part of this journey.


Outline/Structure of the Talk

  • What is DevOps all about
  • What is Product Development Flow and how it maps to DevOps
  • Kanban as a way to navigate the journey towards Flow and DevOps
  • Examples from the real world of how Kanban/Flow was used to extend agile towards devops


Learning Outcome

  • Understand what is DevOps and the relationship to Lean/Agile
  • Be familiar with the 3 ways that take you towards DevOps culture
  • Understand what needs to change for an "agile" team/organization to enjoy the benefits of DevOps
  • Understand what is Kanban (very brief introduction, not an in depth session)
  • Understand what is Product Development Flow (very brief introduction, not an in depth session)
  • Understand how Flow/Kanban is a very good fit to apply the 3 ways towards DevOps

Target Audience

Development Managers, Operations Managers, Program Managers, Agile Coaches, Managers, Scrum Masters, Project Managers, CIOs, AppDev Managers



schedule Submitted 7 years ago

  • Cindy Bloomer

    Cindy Bloomer - Influencing Organization Change – a Framework for Thinking about and Designing Change Initiatives

    45 Mins

    Studies over the last two decades have shown change initiatives have a high rate of failure to meet expected outcomes, yet traditional change management approaches continue to apply a sequential, step-by-step process in constantly changing environments.   An underlying assumption for these approaches seems to be that the desired end-state is assured, as long as the steps are followed.

    Successful change initiatives in today’s environment will view the “wicked problem” of complex change through an empirical framework based on proven concepts from Organization Development (OD), augmented with tools and techniques from additional disciplines such as Lean, Agile, and Human Systems Dynamics (HSD) to influence changes in thinking and behaving.

    This interactive session includes:

    • Overview of the OD approach to organization change
    • Introduction of a Change Spectrum for visualizing organization change
    • Introduction of an Empirical Framework for designing and implementing change initiatives
    • Introduction and Overview of a few specific diagnostic models from OD, Human Systems Dynamics, and Integral Agile
    • Overview and discussion of a few specific tools and techniques that help shift thinking and behavior


  • 90 Mins

    More and more organizations have already reached some level of Agility. Some of them reached what we call Stable/Recharge which means they stabilized some structure/process that works for them. They had a couple of months or even years to “digest”/”recharge” and are now waking up hungry for the next level. Others got stuck along the way with some process that frustrates them but they didn’t really know what to do with it and just continued to suffer. These ones typically have a grudge towards agile when we meet them. People in these two groups have some common ground - they have a lot to benefit if they get exposed to some practical tips and tricks from the trenches that can help connect “by the book” agile to the day to day reality in the typical organization.

    In this "Agile Boost Camp" session we will give participants ideas/tips for working through typical boost/reset challenges. These tips/ideas are inspired by working in the trenches with real world organizations.

    Each time this session/workshop runs is different because the workshop runs in an agile form where the participants act as the “Product Owners” choosing and customizing the agenda. The trainer brings in the experience and best practices as well as orchestrates the workshop experience.

    Ready for your Boost?


  • Yuval Yeret

    Yuval Yeret - Helping Scaled Agile cross the chasm using pull-based change approaches

    45 Mins

    In fall 2015 there is no question that business agility is required. You will also be hard pressed to find anyone arguing against the core principles of lean/agility or against most of the practices. Many teams are implementing agile with varying levels of success.

    But most enterprise organizations have not yet reached the levels of agility you read about in books or hear about at conferences. As Lean/Agile is crossing the chasm into the mainstream, Scaled Agile approaches like "Scaled Agile Framework (SAFe)" and "Large Scale Scrum (LeSS)" are positioned as the next logical move.

    A big question is HOW to drive this kind of change in the organization. Through stories from the trenches of enterprise change management we will discuss different approaches to change and when each is appropriate. We will see how approaches like evolutionary change , "free market" / "pull based change management" , "invite-based change" help accelerate the journey towards agility across an enterprise without risking its stickiness. I will share some hard-learned lessons that resulted in patterns like “Manager’s first”, “Document/Methodology later”, “Market & wait for Pull”, “Case Study”, “Opt-in vs Mandate”, “Guidebooks OVER guided tours”. 


  • Paul Boos

    Paul Boos / Laura M. Powers - Understanding How Collaboration Improves Productivity

    90 Mins

    We've all heard how we need to collaborate better, but what does this really mean?  What results can I expect to see with better collaboration?  

    This workshop will demonstrate how productivity increases with greater collaboration and how to create better a more collaborative environment.  In the session you will not only have an opportunity to experience this relationship with a relatively simple learning game, but we'll look behind the curtain at the science and how some various behavioral models explain why this relationship exists.  We'll then explore some tactics you can use to help teams collaborate better and close with an exploration of what either helps or hinders collaboration and how you can use this information as well as the game with your teams.

    If you have an interest in improving productivity of your team or the teams you serve, then this is the session for you.

  • David Ehrlich

    David Ehrlich - Implementing Agile to Support the Delivery of Productivity Software in the Federal Governemnt

    45 Mins

    We all know that agile development will increase the likelihood of a good outcome for software development projects.  This talk is a case study describing how a federal government agency partnered with a software vendor to rescue a failing software development project.  The project was an initiative of the head of the agency.  The scope of the project was to enhance the custom software productivity application that has over 2000 users and supports the agency's primary mission.  The following agile practices were implemented which benefited the project.

    Time boxing

    Collective ownership

    Iteration planning

    Daily stand up meetings

    Pair programming

    Active stakeholders

    This was all done on government contract for a firm fixed price.  This session will describe how and why these processes were implemented and how they benefited to project and its stakeholders.