🎯 Key Takeaways for quick navigation: [02:07] 💡 Kanban originated from manufacturing in the 1950s. [03:16] 🎯 David Anderson used Kanban at Microsoft and achieved great success. [04:08] 👁️ Visualization is one of the most well-known aspects of Kanban, but it wasn't introduced until 2007. [05:03] 🚗 Kanban systems were originally used in the Toyota Production System to track the production of car doors. [07:16] ⚖️ Kanban is about understanding the demand on your teams and matching it with their capability. [07:59] 👥 Kanban teams are focused on understanding how much work they have and whether they have the teams to be able to fulfill that. [09:07] 🎯 Kanban principles include understanding and focusing on customer needs, and managing the work and letting people self-organize around it. [10:17] 💡 Start with what you do now is a core Kanban principle. This means that Kanban is not about changing the way you work, but about understanding how you are working now and seeing how you can adopt Kanban over time. [11:43] 🤝 Kanban is about collaboration and everyone in the organization taking responsibility for improvement. [13:24] 📊 To be technically Kanban, you need to visualize your work and understand the demands and the capability of your organization. [15:28] 💡 Start with what you do now. Use a static analysis to identify the current state of your workflow. [15:56] 📝 A typical Kanban system for software development includes a number of state columns, buffers, and swimlanes. [17:34] ➡️ Cards should only move forward in one direction. [18:03] 📜 Define explicit policies for your Kanban system, such as definitions of done and column rules. [18:58] 🎯 Use your Kanban visualization to identify problems and make decisions. [22:37] ❓ Lead time and cycle time are often confused, but in Kanban, lead time is the time from "ready" to "deploy", while cycle time is the time spent actively working on a task. [22:52] 💡 Whip limits are work-in-progress limits that help teams focus on getting work done rather than having too much work in progress at any given time. [23:36] 💰 The value part of the Kanban board is the "tests onwards" section, where all the work that has been invested in is ready to be delivered. This is where teams should focus their efforts, as it is where the most value can be created. [24:30] 👥 Kanban daily standups are different from Scrum daily standups in that they are more facilitated and focused on getting work out the door. [26:09] 🎨 Kanban boards can be customized to meet the needs of the team. This can include using different colors, swimlanes, buffers, and other visual elements. [30:11] 🎯 Kanban helps us to focus on finishing things and balance the board. [31:09] 💰 Multitasking costs money because people put it down and pick it up, they look, they send reminders, etc. [32:57] 💡 Littles law is a relationship between three things: lead time, work in progress (WIP), and throughput. [34:05] 👥 To improve throughput, you can either improve the lead time or add more people to the team. [36:38] ⏳ Start with whatever you think is appropriate and gradually reduce whip limits over time. [53:18] 💡 Discovery Kanban is a method for flowing changes using mini Kanban boards. [53:36] 🔄 Inspect and adapt is an agile principle that emphasizes continuous improvement. [54:03] 🧪 Validate your changes to ensure that they are having the desired effect. [54:18] 🎯 Focus on improving the biggest problem first. [55:14] 💡 Evolve over time and learn from your mistakes.
Excellent presentation (especially after the 14 minute mark). THANK YOU. I was happy to hear I'm not wasting time by keeping a physical and digital version of board.
Hi, First of all, Thank you for the great explanation, this is really a great information and will help me a lot, i have a question for yo please regarding the flow efficiency % formula, could you please elaborate on what is the work time Vs. lead time? it might be an old video, hope you can answer me, Thank you
Small correction, you said that 'inspect and adapt is actually an agile thing' , its actually a scrum thing specifically. I'm not sure what the man in the audience yelled out.
Excellent. Just excellent! Thanks for sharing it.
🎯 Key Takeaways for quick navigation:
[02:07] 💡 Kanban originated from manufacturing in the 1950s.
[03:16] 🎯 David Anderson used Kanban at Microsoft and achieved great success.
[04:08] 👁️ Visualization is one of the most well-known aspects of Kanban, but it wasn't introduced until 2007.
[05:03] 🚗 Kanban systems were originally used in the Toyota Production System to track the production of car doors.
[07:16] ⚖️ Kanban is about understanding the demand on your teams and matching it with their capability.
[07:59] 👥 Kanban teams are focused on understanding how much work they have and whether they have the teams to be able to fulfill that.
[09:07] 🎯 Kanban principles include understanding and focusing on customer needs, and managing the work and letting people self-organize around it.
[10:17] 💡 Start with what you do now is a core Kanban principle. This means that Kanban is not about changing the way you work, but about understanding how you are working now and seeing how you can adopt Kanban over time.
[11:43] 🤝 Kanban is about collaboration and everyone in the organization taking responsibility for improvement.
[13:24] 📊 To be technically Kanban, you need to visualize your work and understand the demands and the capability of your organization.
[15:28] 💡 Start with what you do now. Use a static analysis to identify the current state of your workflow.
[15:56] 📝 A typical Kanban system for software development includes a number of state columns, buffers, and swimlanes.
[17:34] ➡️ Cards should only move forward in one direction.
[18:03] 📜 Define explicit policies for your Kanban system, such as definitions of done and column rules.
[18:58] 🎯 Use your Kanban visualization to identify problems and make decisions.
[22:37] ❓ Lead time and cycle time are often confused, but in Kanban, lead time is the time from "ready" to "deploy", while cycle time is the time spent actively working on a task.
[22:52] 💡 Whip limits are work-in-progress limits that help teams focus on getting work done rather than having too much work in progress at any given time.
[23:36] 💰 The value part of the Kanban board is the "tests onwards" section, where all the work that has been invested in is ready to be delivered. This is where teams should focus their efforts, as it is where the most value can be created.
[24:30] 👥 Kanban daily standups are different from Scrum daily standups in that they are more facilitated and focused on getting work out the door.
[26:09] 🎨 Kanban boards can be customized to meet the needs of the team. This can include using different colors, swimlanes, buffers, and other visual elements.
[30:11] 🎯 Kanban helps us to focus on finishing things and balance the board.
[31:09] 💰 Multitasking costs money because people put it down and pick it up, they look, they send reminders, etc.
[32:57] 💡 Littles law is a relationship between three things: lead time, work in progress (WIP), and throughput.
[34:05] 👥 To improve throughput, you can either improve the lead time or add more people to the team.
[36:38] ⏳ Start with whatever you think is appropriate and gradually reduce whip limits over time.
[53:18] 💡 Discovery Kanban is a method for flowing changes using mini Kanban boards.
[53:36] 🔄 Inspect and adapt is an agile principle that emphasizes continuous improvement.
[54:03] 🧪 Validate your changes to ensure that they are having the desired effect.
[54:18] 🎯 Focus on improving the biggest problem first.
[55:14] 💡 Evolve over time and learn from your mistakes.
Excellent presentation (especially after the 14 minute mark). THANK YOU. I was happy to hear I'm not wasting time by keeping a physical and digital version of board.
Glad you enjoyed it!
Hi, First of all, Thank you for the great explanation, this is really a great information and will help me a lot, i have a question for yo please regarding the flow efficiency % formula, could you please elaborate on what is the work time Vs. lead time? it might be an old video, hope you can answer me, Thank you
Small correction, you said that 'inspect and adapt is actually an agile thing' , its actually a scrum thing specifically. I'm not sure what the man in the audience yelled out.