This year at DevOps Days Seattle, I spoke about how often people get stuck in a very shallow implementation of Kanban. In fact, in many things, we often implement a very thin layer of something good but don’t know how to take improvement to a deeper level. First I introduce the audience to a team that has started an improvement initiative, specifically a Kanban implementation, and they’ve seen results, but still aren’t where they want to be. This story progresses throughout the talk in which I share four common indicators of a shallow Kanban implementation and how you can start to wade a little deeper with your process improvements. I give three areas to address, with (hopefully) tactical tips that you can start immediately when you’re back at the office.
