I’ve been pretty silent on this blob the past few weeks. Starting a new job is quite a tow.
After doing Kanban for over a year at my previous gig, and enjoying it, it was quite natural for me to introduce it to my new teams.
The first team that jumped into it (from scrum) decided -on its own- to put a presentation for the other teams after a few weeks.
Unfiltered tidbits:
- Stand ups differ – going story by story, not based on individuals
-
Less Rules: No roles prescribed, More Dynamic
-
Backlog more Flexible
- Pros: Better Team Focus, Less Meetings More Time to Deliver, More Flexible Work Process
- Cons: Less Structure Could Cause issues with Some People
- How Its Working Out: Feels Good, Increased Our Collaboration, Communication Has Increased, Forces Follow Up to Eliminate Blockers
The team loves the reduced prescription list. This may only be a sign that they like change – this is a proactive team.
Half of my teams have now introduced Kanban changes to their scrum. Some have directly abandoned iterations and everything coming with them, some have simply added limits and changed a few things.
Having David Anderson in the office for a few days was a big catalyst. BTW, Check out his new book on Kanban.
PS: for the picture in the post? I don’t know. Ask my team. They put it in their presentation


