I was on the phone recently with Stacy, a dev team manager. During our conversation, I shared the concept of using relative card positioning, or stack ranking, to show the priority of items of a queue on a kanban board. Personally, I have used this tactic very successfully in the past as it provides visual cues to both the doers that need to know what’s next, as well as to the requestors of work who want to know when we’ll get to their item. When I finished explaining, Stacy said, “Yes, we’ve tried that in the past but we don’t do it anymore. The problem was that requestors got upset that their item was number five in our queue.”
Every week, before our Lean Coffee in Seattle, there is an unofficial social gathering called #prelean. I value this gathering tremendously as it is a time to get together with peers to learn and build deeper relationships. A staple at #prelean, Adam Yuret is one of my closest friends as well as an amazing consultant. A couple of weeks ago, Adam brought up a topic that sounded controversial: “Do Teams Matter?” For someone who has always been a vocal advocate for their teams in the past, my gut reaction was “Of course they matter! Don’t be so cynical.” But, as the conversation went on, I found my perspective widening quite a bit.
I had a great time at the DevOps Enterprise Summit last year so I decided to submit a few talks for the 2016 event. As this was the event in which I gave my inaugural conference presentation at in 2015, I was thrilled to be invited back!
In my talk for this year’s event I wanted to try something new. Many people struggle to get through, and understand, the excellent “Principles of Product Development Flow” by Don Reinertsen. I wanted to see if I could take a crack at putting a core concept or two in terms that were most accessible to a larger audience. As with any first iteration of something, there are many adjustments I’ll make going forward, but hopefully you and the attendees of the actual talk will find value in this presentation. Enjoy!