Kanban learnings - Running multiple projects hides impediments
Kanban learnings part #2
Basically the orgininal Kanban board:
Was reduced to:
Was reduced to:
Mattias Skarin's blog
Kanban, Lean and Agile mysteries
Recent Responses 
- Sverker the Reindeer...
Yes - He is back! :) ( Nice to see you Johan :) - Sverker the Reindeer...
...found a scrum paper on the developer's notice board at work, with the name "Mattias Skarin" written on it. - Re: The book is out!
Great book, good work Mattias! ;o) - Re: West vs. Japan
There are many ways of doing improvements. My point is, the attitude we have towards doing improvements, is one of the first blockers. Here we have much to learn. - Re: West vs. Japan
In scrum you usually have demo+retrospective one day and next sprint planning the day after/next week. Have you tried to have the demo one day. And retrospective + sprintplanning the next day? - Re: Four strategies for dealing with breaking WIP limits
Cool! of course interested in where you went to from there :) (at some later stage) - Re: Four strategies for dealing with breaking WIP limits
Nice post Mattias; we're starting to use Kanban for our software maintenance. We basically use the overflow concept for work that meets the criteria of an "emergency". We allw that work to overtake what was originaly a work in progress. Once that is d... - Re: Speaker at Lean Conference, Atlanta 2010
Rock 'n roll! I'll miss the conference unfortunately. My wife and I have a release that I don't want to miss, after a 9 month iteration :o) - Re: Why cycle time can tell you more than velocity
Cool! - Re: Why cycle time can tell you more than velocity
Hello Mattias, tour post is very interesting. So I've translated it in french: Pourquoi le temps de cycle peut-il en dire plus que la vélocité ? Regards, Fabrice - Re: Your Scrum is running fine, right?
Very good post, highly interesting! - Re: Scrum team converts to Kanban
The team does estimation and daily standup pretty much Scrum like. So it is kind of a Hybrid right now. What is changed is: - limit work in progress continuously instead of sprint commitment - burndown is towards release not sprint - weekly Kaizen (co... - Re: Scrum team converts to Kanban
I think they aren't solving their problems :) Unfortunately, Scrum doesn't help you with that. And this can be hard. You need a place to start. That is where Kanban provided use, it helped the team, Product Owner and Manager to agree on what issue to ... - Re: Scrum team converts to Kanban
Mattias, without knowing more about the team I would argue that a team whose burndown looks that that for three consecutive sprints are not doing Scrum in the first place? - Re: Scrum team converts to Kanban
Which changes has the second team made to their process to consider this a conversion from SCRUM to Kanban? If they still have sprints and burn-down charts, why is it Kanban? Thanks! - Re: Scrum team converts to Kanban
I guess a blog post follow up to explain the changes made. They weren't many, just better flow and WiP visibility to the team. What I found striking was that team ended up in this new situation without any active coaching. They just watched another te... - Re: Scrum team converts to Kanban
Not excluded of course :) After all, this was just one sampling, so not scientifically reliable data yet. - Re: Scrum team converts to Kanban
I (believe) it is because they got better WiP transparency. - Re: Scrum team converts to Kanban
> I don't get it. Why was the burn down different when the team converted to Kanban? Small WIP effect I think. - Re: Scrum team converts to Kanban
Same here? What else did you do? Just because you changed the name of the process it does not make it better? I'm intressted in how you used the burndown chart for Kanban? i love the BC but I haven't found a good way to use it properly in my Kanban teams.