At the beginning of the year, I introduced Kanban to two Scrum teams I worked with as a ScrumMaster and one problem I faced was how to integrate tasks into the Kanban board. Practicing Scrum for more than one year, the teams were used to tasks and refused to drop them, because they saw tasks as very helpful in order to see there progress and synchronize their work. I agreed with the team and didn’t want to change to much in order to avoid resistance as much as possible, but at the time it seemed there was no room for tasks and stories on a Kanban Board. Of course we found a first solution and started to advance from there, but somehow I wasn’t able to write it down, until yesterday.
That’s because I received an email from a friend, an Agile Coach, asking me for advice on how to tackle pretty much the same problems I had when starting to use Kanban with the Scrum teams. Needless to say I answered his questions and I guessed there are probably more people out there having trouble with integrating tasks into their Kanban System. So I decided to finally revive my blog and share my experiences in switching from Scrum to Kanban and hopefully help others with it and maybe get some more ideas and feedback. Here is my solution to how to integrate tasks known from Scrum into a Kanban board.