Introducing Kanban Into an Existing Scrum Implementation
Scrum and Kanban Like Chocolate and Peanut Butter
There doesn't seem to be much material specifically geared towards introducing Kanban into an existing Scrum implementation as opposed to going from non-Agile to Kanban. So, I've decided to write a short and concise guide to folding Kanban practices and principles into an existing Scrum implementation called "Scrum and Kanban Like Chocolate and Peanut Butter." I will write the guide via a series of blog entries over the coming weeks. I hope you will follow along with me, asking questions and offering feedback.
Who is "Scrum and Kanban Like Chocolate and Peanut Butter" Intended For?
The first question is: when does it make sense to introduce Kanban where Scrum is already in use? It turns out that is a very complicated question. Rather than answer that question, I'm just going to gear my posts towards folks that match a certain set of circumstances. My material for introducing Kanban into an existing Scrum implementation is geared towards folks for which the following is true:
- You have already been doing Scrum for 6-9 months
- There is a general feeling that things are going better than before Scrum was introduced
- You are using user stories
- You have a definition for "done"
- Your user stories are relatively short with no stories that take longer than 1/2 of the iteration to get to done
- Most stories are "done" at the end of the iteration
- You have an iteration length of 4 weeks or less
- You have a cross-functional (though not necessarily self-managed or co-located) team
- If there is a "business unit" that previously served as "the customer" then you've integrated the business unit and software team at least to the point that there is a product owner on the team which talks to the customer of the business unit, and the business unit is no longer considered to be the customer for the software team.