The “Kanban Method” becoming more Agile by getting 2 important practices: TeamLeaderShip and Feedback Loops
A fellow trainer pointed me to this post from David Anderson: “EXTENDING THE FIVE CORE PRACTICES OF KANBAN”
As I’ve identified in presentations and key note speeches I gave in 2010, 2011 and earlier this year, the biggest oversight is leadership. Small acts of leadership from any member of the team need to happen regularly. It is these acts of leadership that make change happen.
So the 6th practice is: Leadership - give permission for ideas and encourage process innovation from any and all team members.
Sounds like building a team ;-)
There is also a need for explicit feedback loops. The Kanban book identifies these at two levels:
- the daily standup meeting at the team and individual contributor level
- and the operations review at the organization and inter-team or across services level
So the 7th practice is: Implement Organizational Feedback using Quantitative Measures of Demand and Capability
Sounds like having short feedback loops is a good thing
Kanban vs. Scrum: Kanban is NOT for Software Development, but Scrum is!
Nice article from fellow Scrum Trainer about the differences between “Scrum” and the “Kanban Method”
- You are applying Kanban to the incorrect context.
- Kanban is modeled more after the assembly line and manufacturing. Scrum is modeled more after creative product design.
- From a Complexity Science view, Kanban is for ‘complicated’ work while Scrum is for “complex” work.
Make sure to understand the difference between “Kanban” and “The Kanban Method”
Stop talking about Kanban, start talking about the work
Digitize your physical board with QR codes
Do you read more about development than you actual develop something?
3 reasons to choose Kanban over Scrum
Great presentation to “grasp” Kanban. It shows how to adapt Kanban in a development project.
Interesting idea. I think it comes down to, that you forget about the process at all, since you are in a “self organizing flow state”.