Several months ago our software team decided to dive into the Scrum process. What we were doing before that simply wasn't working. The project had unstable delivery dates and we knew something needed to change.
Fast forward about four months and we're going to take a shot at using Kanban and leave Scrum behind. Quite surprising since I blogged that Scrum was a pretty good development methodology. Why change if Scrum is so great? Did Scrum fail? Is Kanban that much better? Is Kanban Better than scrum? Read on fellow Kaizenista.
Why Change To Kanban?
The developers that I work with are professionals at their core. For us we want to deliver code, we want to make an impact. We want a consistent process that brings us maximal results. We want a process that aides our development and doesn't impede it.
I work for the world's largest motorcycle parts and accessories dealer. The code we right is in high demand, we want to get it out to the world as soon as possible. Scrum imposes sprints and releases (several sprints) on the team. We found that we don't work that way. If a feature is "done, done, done" we promote it to production we don't wait for an arbitrary end of sprint. This seems to fit better with Kanban.
Secondly we want to reduce lead times, see features get implemented quicker. While we saw a huge improvement with the adoption of scrum, the idea of a pull system versus a sprint backlog would have meant shorter lead time in several cases in the recent past.
There are other reasons, but they all point to our desire to produce more. Upper management has been quite pleased with scrum. They see consistent work being accomplished and goals being met and the team quite happy. I had a discussion with my boss today about Kanban and was initially hesitant given only four months of using scrum. He was thrilled with the idea of us working in ways to improve the process.
Did Scrum Fail?
I was asked my thoughts on a similar question on the drive home tonight by Chris Missal. I absolutely don't think Scrum failed. Scrum was a huge improvement and has shown us that it is okay to experiment and tweak with processes. Had we adopted Kanban several months ago rather than first going through Scrum I believe our Kanban process would not have gone over well. Quite simply we wouldn't have done it right. Now, after having worked in Scrum, we're transitioning to Kanban to address very specific points where we see waste.
Is Kanban Better than Scrum?
Nope, Scrum is a perfectly fine solution and I don't have a negative thing to say about it. For us Kanban seems to work more the way we work.
It's like putting on a tennis shoes to go golfing in then later trading in the tennis shoes for a pair of golf spikes. The spikes are better than tennis shoes but the tennis shoes are better than nothing (barefoot).
It's a better fit. For the way our process flows and how we work, Scrum was like golfing in tennis shoes, it was an improvement but there are better optimizations to be made. If Scrum is working for you, great. For us we wanted to try Kanban.
How are you Going to Start?
First, we don't know much about Kanban. No one on our team carries certification like I do with Scrum. Therefore we're going to leverage you, the community, and our passion to learn and improve. We're going to use post's from great authors and teachers like Derick Bailey who posted yesterday (very well timed Derick) about "How To Get Started With Kanban In Software Development". We're going to become student of Kanban and more importantly process improvement. Ultimately I don't want the fear of something new to stop of from trying something that could help us. You have to experiment, tweak, and never be satisfied where you sit, you can always improve something.
I'll keep you all posted as we go forward. My hope is that the improvement we saw with Scrum will be magnified and we'll see similar improvements with Kanban.
Will keep you posted.
08-06-2009 10:25 PM