Intro to Kanban - AgileDayChile2011 KeynoteChileAgil
This document provides an introduction to Kanban, including what it is, why it would be used, and its origins and principles. Kanban is a pull-based system that uses visualization techniques like boards and limits on work-in-progress to regulate flow. It originated from the Toyota Production System and can be overlaid on software development processes. The document outlines how Kanban was implemented at one company and discusses scaling Kanban to larger projects. It also explains how Kanban encourages continuous improvement through evolutionary changes and how these principles form the Kanban Method for adopting Lean practices.
The document discusses Kanban, a Lean methodology based on visualizing workflows. It describes Kanban concepts like limiting work-in-progress and measuring lead times. The document then outlines several experiments using a Kanban game with roles like squares maker and triangles maker. Finally, it provides overviews of key Kanban techniques including cumulative flow diagrams and visualizing workflows.
Finding a way to do things more efficiently is important - no matter what business you are in or what kind of projects you do.
Check out the basic Kanban principles that might change the way you work.
Good luck!
This document provides an introduction to Kanban basics for beginners. It discusses the origins of Kanban in the Toyota Production System and how it was adapted for software development. The core Kanban principles are visualized workflow, limiting work in progress, and continuous improvement. Examples are given of how to apply these principles, such as using minimal marketable features and Little's Law to deliver faster. Prioritizing work based on business value, cost of delay, and resource availability is also covered. The document concludes with references and recommendations for further learning about Kanban.
Kanban is the simplest approach which is currently used in software development. Since Kanban prescribes close to nothing there are often a lot of basic questions about the method.
The presentation depicts what Kanban is generally using Scrum as a reference point. Then it presents a series of situations to answer basic questions about working with Kanban
Kanban 101 workshop by John Goodsen and Michael Sahota.
This covers everything you will need to know to play Russell Healy's Kanban Game: visualizing the work, metrics, and creating explicit policies.
Slides are available on request. Please email me.
This document provides an introduction to Kanban, an agile methodology that focuses on visualizing and limiting work-in-progress to continuously improve workflow. It defines Kanban and how it was inspired by lean manufacturing practices. The core practices of Kanban are outlined, including defining and visualizing the workflow, limiting work-in-progress, measuring and managing flow, making process policies explicit, and using models to suggest improvement. An example Kanban board is demonstrated. Finally, the document discusses how to build a Kanban process by defining queues and work items, setting work-in-progress limits, establishing delivery cadence, and continually improving the process through Kaizen.
This document provides an overview of Kanban concepts and how to visualize workflows using Kanban boards. It demonstrates how to transform a simple task list into a Kanban board with statuses, queues, work-in-progress limits, and swim lanes for priorities. Additional concepts covered include identifying and addressing bottlenecks, handling wait times, limiting team member activities, creating forecasts, linking boards for Scrum, personal Kanban boards, and using a board for a cross-functional team.
Intro to Kanban - AgileDayChile2011 KeynoteChileAgil
This document provides an introduction to Kanban, including what it is, why it would be used, and its origins and principles. Kanban is a pull-based system that uses visualization techniques like boards and limits on work-in-progress to regulate flow. It originated from the Toyota Production System and can be overlaid on software development processes. The document outlines how Kanban was implemented at one company and discusses scaling Kanban to larger projects. It also explains how Kanban encourages continuous improvement through evolutionary changes and how these principles form the Kanban Method for adopting Lean practices.
The document discusses Kanban, a Lean methodology based on visualizing workflows. It describes Kanban concepts like limiting work-in-progress and measuring lead times. The document then outlines several experiments using a Kanban game with roles like squares maker and triangles maker. Finally, it provides overviews of key Kanban techniques including cumulative flow diagrams and visualizing workflows.
Finding a way to do things more efficiently is important - no matter what business you are in or what kind of projects you do.
Check out the basic Kanban principles that might change the way you work.
Good luck!
This document provides an introduction to Kanban basics for beginners. It discusses the origins of Kanban in the Toyota Production System and how it was adapted for software development. The core Kanban principles are visualized workflow, limiting work in progress, and continuous improvement. Examples are given of how to apply these principles, such as using minimal marketable features and Little's Law to deliver faster. Prioritizing work based on business value, cost of delay, and resource availability is also covered. The document concludes with references and recommendations for further learning about Kanban.
Kanban is the simplest approach which is currently used in software development. Since Kanban prescribes close to nothing there are often a lot of basic questions about the method.
The presentation depicts what Kanban is generally using Scrum as a reference point. Then it presents a series of situations to answer basic questions about working with Kanban
Kanban 101 workshop by John Goodsen and Michael Sahota.
This covers everything you will need to know to play Russell Healy's Kanban Game: visualizing the work, metrics, and creating explicit policies.
Slides are available on request. Please email me.
This document provides an introduction to Kanban, an agile methodology that focuses on visualizing and limiting work-in-progress to continuously improve workflow. It defines Kanban and how it was inspired by lean manufacturing practices. The core practices of Kanban are outlined, including defining and visualizing the workflow, limiting work-in-progress, measuring and managing flow, making process policies explicit, and using models to suggest improvement. An example Kanban board is demonstrated. Finally, the document discusses how to build a Kanban process by defining queues and work items, setting work-in-progress limits, establishing delivery cadence, and continually improving the process through Kaizen.
This document provides an overview of Kanban concepts and how to visualize workflows using Kanban boards. It demonstrates how to transform a simple task list into a Kanban board with statuses, queues, work-in-progress limits, and swim lanes for priorities. Additional concepts covered include identifying and addressing bottlenecks, handling wait times, limiting team member activities, creating forecasts, linking boards for Scrum, personal Kanban boards, and using a board for a cross-functional team.
The document provides an overview of Kanban workflow concepts including:
1) Assignables like user stories, features, tasks, and bugs which define the work and its status.
2) Evaluating business value and severity to prioritize work, and estimating effort for user stories using a points system.
3) Standard statuses for work including backlog, planned, in progress, in review, in testing, and done to track progress through the workflow.
4) Additional rules like only working on one item at a time, not starting work without a ticket, and reporting impediments to the project manager.
This document provides an introduction to Kanban, including:
1. The background and origins of Kanban in lean manufacturing.
2. The key elements of the Kanban method including visualizing workflow, limiting work-in-process, managing flow, establishing explicit policies, improving collaboratively through kaizen, and implementing feedback loops.
3. Tools that can be used to implement Kanban and references for further reading on Kanban.
The document provides an introduction to Kanban, which is a set of ideas from lean thinking for managing knowledge work. It outlines the six core properties of Kanban: 1) visualizing work, 2) limiting work-in-progress, 3) managing flow, 4) making policies explicit, 5) implementing feedback loops, and 6) making continuous evolutionary improvements. The document emphasizes that Kanban promotes evolutionary, not revolutionary, change and respect for the current process.
Implementing Kanban to Improve your WorkflowJennifer Davis
Tutorial from LOPSA East
System, network, and security senior engineers manage intricate relationships ensuring that everything from simple tasks to complex projects gets completed in a timely manner. In this workshop, we will talk about using agile processes to identify, visualize, and improve work.
Outline:
Overview of the kanban process. What is kanban?
Identify common problems.
Define common terminology explicitly.
Work through common problems as a group using kanban.
Identify metrics for improvement.
Review, next steps, additional resources.
At the end of this tutorial, attendees will have a solid understanding of kanban and agile processes to take back to their environments.
Kanban is a scheduling and workflow management system developed at Toyota in the 1940s. It uses visual cues like cards or notes to manage workloads and optimize workflow. Kanban focuses on limiting work-in-progress to avoid bottlenecks. Teams use physical or online Kanban boards to visualize workflows, track work status, and improve processes through metrics like throughput and work-in-progress. Setting up Kanban involves mapping current workflows, visualizing work, focusing on continuous flow, and limiting work-in-progress using work-in-progress limits.
Kanban is a visual project management system originally used in Toyota's manufacturing process. It uses cards or images on a board to visualize workflow from one stage to the next and limit work-in-progress to avoid bottlenecks and focus on continuous flow. The core principles are to visualize workflow, limit WIP, focus on flow, and drive continuous improvement. Kanban and Scrum are both agile methods but Kanban allows continuous workflow while Scrum uses sprints and fixed roles. Key benefits of Kanban include improved visibility, collaboration, and productivity through waste reduction.
This file introduces the principle of Kanban and pull system. In the rest of the file, we concentrate on Kanban and introduce the types of Kanban, six rules for an effective kanban system, the number of Kanban card and kanban circulation.
In this presentation, Roni explains the basics of Kanban and the principles governing the application of Kanban for process improvement. We also look at a comparison between Scrum and Kanban and visit the basic differences between them.
It includes pointers telling what’s wrong with the current system, history of Kanban, introduction to Kanban, benefits of using Kanban, practices used in Kanban, principles of Kanban, how is Scrum different from Kanban. The tutorial begins with details about the current system and what’s wrong with it. It includes pointers like burnout, low throughput, unidentified bottlenecks, too much work which tell what’s wrong with the current system.
Followed by is a section about the history of Kanban which includes points like how the name originated, who discovered it, design, visual signals, based on which system. Resulting in an introduction section which talks about Kanban, what method it uses, scheduling system, what it consists of, amount of work, identification etc. Next comes the benefits section which includes the benefits of using Kanban like helps in visualizing the system, allows to evaluate, identify bottlenecks, establish trust in process etc.
Afterwards there is a section about Kanban practices. It includes practices used in Kanban like visualize, limit WIP in each phase of development, managing flow by keeping it under monitor, make policies explicit, improve collaboratively through the use of scientific models and some terms like lead time, cycle time, throughput etc. Moreover, it also includes the board for easy visualization, story card for keeping track, charts for measurement, control charts to measure average time taken for each task, cumulative flow diagrams showing relative amount of work.
Then comes the principles of Kanban. It includes principles which should be used in Kanban like agree to pursue incremental, evolutionary change, optimize what already exists, respect the current process, roles, responsibilities, leadership at all levels to empower the workforce to bring about change. The last section of this tutorial is Scrum vs Kanban. It explains how scrum is different from Kanban by giving pointers like Scrum prescribes roles, time boxed iterations, backlog items must fit, limit WIP in a different way. It also includes pointers giving reason why it shouldn’t matter because emphasis should be on the goal and not the tool.
Kanban method in four easy steps. Enjoy kanban.
Kanban in 4 easy steps is one of the most popular Kanban presentations. Learn how to successfully implement Kanban in your business process or life. Get to know basic Kanban principles and to see how easily you can improve your productivity using Kanban boards.
While Kanban is gaining more and more traction in the tech industry, we start to experience the same challenges as when the popularity of Agile started to rise. People get interested and ask "What is this Kanban thing I see popping up everywhere?". As soon as they learn the basics about it, the human brain does what it always does when processing information. It compares to what it already knows. This is where we lose our ability to learn something without prejudice. We come up with arguments why these new idea are not as good as the ones we are used to. In this presentation, I will cover 5 of the most common arguments against Kanban and explain why they are flawed, by exploring Kanban in depth. You will learn how to respond to these questions and get a more profound knowledge on the foundations of Kanban.
The document discusses Scrum, an agile framework for managing product development. It describes Scrum roles like Product Owner and Scrum Master. Key Scrum events are also outlined such as sprint planning, daily standups, sprint demos and retrospectives. Benefits of Scrum mentioned are rapid development, transparency and embracing change.
STATIK (Systems Thinking Approach to Introduce Kanban) es un enfoque exploratorio y colaborativo para implementar Kanban. Ayuda a entender la demanda y las dinámicas actuales, para diseñar y poner en marcha un modelo Kanban de trabajo que permita elevar la eficiencia y calidad en el servicio a través de la cultura y las técnicas de la mejora continua.
También es una buena herramienta para descubrir todos los servicios que proporciona un equipo, sus flujos de trabajo y su alineación con el propósito y las expectativas del cliente.
The document describes a single-card Kanban system with a figure showing the flow of materials through different stages of production including receiving, fabrication, storage, and assembly lines. Kanban cards are used to signal the need to replenish materials and allow containers to move between stages only when authorized by a card. The key aspects of Kanban systems are also summarized such as only moving full containers with a card and not exceeding authorized production levels.
This document provides an overview of Kanban, an agile project management methodology. It begins with limitations of current systems like bottlenecks and bugs. Kanban was developed at Toyota to visualize workflow using cards on boards. It aims to limit work-in-progress by pulling work instead of pushing it. Key principles include incremental change and respecting current processes. Practices include visualizing workflow, limiting work-in-progress, managing flow, and improving collaboratively. Benefits are simplicity, reduced waste and costs, while limitations include difficulty resizing cards as demand changes. The document concludes with a quote from a project manager praising Kanban's visibility into the project status.
Kanban is a scheduling and inventory control system used in lean manufacturing that focuses on limiting work-in-progress. It was developed by Toyota to improve production flow and involves visualizing and limiting work, continuously improving processes, and focusing on smooth workflow. Kanban boards make work visible and help teams collaborate to improve communication, identify issues, and empower self-managed processes.
Kanban is a lean production system that uses visual signals to manage material flow. It aims to minimize waste through a pull-based system where downstream demand triggers upstream production. Developed by Toyota in the 1950s and based on supermarket replenishment techniques, kanban uses cards or other visual signals to authorize material movement between processes in a just-in-time manner. This helps control inventory levels and avoid overproduction by signaling needs for replenishment only when demanded by the next downstream process.
Scrum is an agile framework that focuses on delivering working software in short iterations called sprints, typically 2-4 weeks. Self-organizing teams work to complete items from a prioritized backlog list. Daily stand-up meetings and sprint planning, review, and retrospective ceremonies provide transparency and opportunities to inspect and adapt the process as needed. The framework aims to rapidly deliver business value through flexible and collaborative teamwork.
Pawel Brodzinski introduces the concept of Portfolio Kanban as a backdoor to organizational evolution. Portfolio Kanban addresses problems that arise from taking on too many concurrent projects, including context switching costs, lower quality work, and emergencies. It uses a visual board to manage total capabilities, commitments, and work in progress limits across all projects. Implementing Portfolio Kanban can result in fewer ongoing projects, fewer emergencies, healthier team work environments, and more slack time for teams.
Just In Time and Lean Operation Chapter PresentationSINGHZEE
This document provides an overview of lean operations and just-in-time (JIT) manufacturing. It discusses that JIT aims to produce goods with minimum lead time and lowest cost by eliminating waste. Toyota popularized JIT techniques like reducing setup times and implementing kanban systems. Key aspects of JIT include eliminating waste, reducing variability, and improving throughput by pulling materials based on demand. JIT requires close supplier partnerships and scheduling to achieve small lot sizes and low inventories. The document outlines tactics to implement JIT principles in both manufacturing and service industries.
Using lean to reduce prototype lead time 2006Chris Baichoo
The document discusses Watlow Batavia's efforts to reduce lead times for custom heating part prototypes from 12 weeks to 6 weeks using Lean concepts. It outlines four Kaizen events from 2003-2006 that standardized processes, created dedicated prototype cells, and reduced waste. As a result, productivity increased 34% from 2003-2006, sales doubled, and lead times were cut in half, improving competitiveness and ensuring the division's survival.
The document provides an overview of Kanban workflow concepts including:
1) Assignables like user stories, features, tasks, and bugs which define the work and its status.
2) Evaluating business value and severity to prioritize work, and estimating effort for user stories using a points system.
3) Standard statuses for work including backlog, planned, in progress, in review, in testing, and done to track progress through the workflow.
4) Additional rules like only working on one item at a time, not starting work without a ticket, and reporting impediments to the project manager.
This document provides an introduction to Kanban, including:
1. The background and origins of Kanban in lean manufacturing.
2. The key elements of the Kanban method including visualizing workflow, limiting work-in-process, managing flow, establishing explicit policies, improving collaboratively through kaizen, and implementing feedback loops.
3. Tools that can be used to implement Kanban and references for further reading on Kanban.
The document provides an introduction to Kanban, which is a set of ideas from lean thinking for managing knowledge work. It outlines the six core properties of Kanban: 1) visualizing work, 2) limiting work-in-progress, 3) managing flow, 4) making policies explicit, 5) implementing feedback loops, and 6) making continuous evolutionary improvements. The document emphasizes that Kanban promotes evolutionary, not revolutionary, change and respect for the current process.
Implementing Kanban to Improve your WorkflowJennifer Davis
Tutorial from LOPSA East
System, network, and security senior engineers manage intricate relationships ensuring that everything from simple tasks to complex projects gets completed in a timely manner. In this workshop, we will talk about using agile processes to identify, visualize, and improve work.
Outline:
Overview of the kanban process. What is kanban?
Identify common problems.
Define common terminology explicitly.
Work through common problems as a group using kanban.
Identify metrics for improvement.
Review, next steps, additional resources.
At the end of this tutorial, attendees will have a solid understanding of kanban and agile processes to take back to their environments.
Kanban is a scheduling and workflow management system developed at Toyota in the 1940s. It uses visual cues like cards or notes to manage workloads and optimize workflow. Kanban focuses on limiting work-in-progress to avoid bottlenecks. Teams use physical or online Kanban boards to visualize workflows, track work status, and improve processes through metrics like throughput and work-in-progress. Setting up Kanban involves mapping current workflows, visualizing work, focusing on continuous flow, and limiting work-in-progress using work-in-progress limits.
Kanban is a visual project management system originally used in Toyota's manufacturing process. It uses cards or images on a board to visualize workflow from one stage to the next and limit work-in-progress to avoid bottlenecks and focus on continuous flow. The core principles are to visualize workflow, limit WIP, focus on flow, and drive continuous improvement. Kanban and Scrum are both agile methods but Kanban allows continuous workflow while Scrum uses sprints and fixed roles. Key benefits of Kanban include improved visibility, collaboration, and productivity through waste reduction.
This file introduces the principle of Kanban and pull system. In the rest of the file, we concentrate on Kanban and introduce the types of Kanban, six rules for an effective kanban system, the number of Kanban card and kanban circulation.
In this presentation, Roni explains the basics of Kanban and the principles governing the application of Kanban for process improvement. We also look at a comparison between Scrum and Kanban and visit the basic differences between them.
It includes pointers telling what’s wrong with the current system, history of Kanban, introduction to Kanban, benefits of using Kanban, practices used in Kanban, principles of Kanban, how is Scrum different from Kanban. The tutorial begins with details about the current system and what’s wrong with it. It includes pointers like burnout, low throughput, unidentified bottlenecks, too much work which tell what’s wrong with the current system.
Followed by is a section about the history of Kanban which includes points like how the name originated, who discovered it, design, visual signals, based on which system. Resulting in an introduction section which talks about Kanban, what method it uses, scheduling system, what it consists of, amount of work, identification etc. Next comes the benefits section which includes the benefits of using Kanban like helps in visualizing the system, allows to evaluate, identify bottlenecks, establish trust in process etc.
Afterwards there is a section about Kanban practices. It includes practices used in Kanban like visualize, limit WIP in each phase of development, managing flow by keeping it under monitor, make policies explicit, improve collaboratively through the use of scientific models and some terms like lead time, cycle time, throughput etc. Moreover, it also includes the board for easy visualization, story card for keeping track, charts for measurement, control charts to measure average time taken for each task, cumulative flow diagrams showing relative amount of work.
Then comes the principles of Kanban. It includes principles which should be used in Kanban like agree to pursue incremental, evolutionary change, optimize what already exists, respect the current process, roles, responsibilities, leadership at all levels to empower the workforce to bring about change. The last section of this tutorial is Scrum vs Kanban. It explains how scrum is different from Kanban by giving pointers like Scrum prescribes roles, time boxed iterations, backlog items must fit, limit WIP in a different way. It also includes pointers giving reason why it shouldn’t matter because emphasis should be on the goal and not the tool.
Kanban method in four easy steps. Enjoy kanban.
Kanban in 4 easy steps is one of the most popular Kanban presentations. Learn how to successfully implement Kanban in your business process or life. Get to know basic Kanban principles and to see how easily you can improve your productivity using Kanban boards.
While Kanban is gaining more and more traction in the tech industry, we start to experience the same challenges as when the popularity of Agile started to rise. People get interested and ask "What is this Kanban thing I see popping up everywhere?". As soon as they learn the basics about it, the human brain does what it always does when processing information. It compares to what it already knows. This is where we lose our ability to learn something without prejudice. We come up with arguments why these new idea are not as good as the ones we are used to. In this presentation, I will cover 5 of the most common arguments against Kanban and explain why they are flawed, by exploring Kanban in depth. You will learn how to respond to these questions and get a more profound knowledge on the foundations of Kanban.
The document discusses Scrum, an agile framework for managing product development. It describes Scrum roles like Product Owner and Scrum Master. Key Scrum events are also outlined such as sprint planning, daily standups, sprint demos and retrospectives. Benefits of Scrum mentioned are rapid development, transparency and embracing change.
STATIK (Systems Thinking Approach to Introduce Kanban) es un enfoque exploratorio y colaborativo para implementar Kanban. Ayuda a entender la demanda y las dinámicas actuales, para diseñar y poner en marcha un modelo Kanban de trabajo que permita elevar la eficiencia y calidad en el servicio a través de la cultura y las técnicas de la mejora continua.
También es una buena herramienta para descubrir todos los servicios que proporciona un equipo, sus flujos de trabajo y su alineación con el propósito y las expectativas del cliente.
The document describes a single-card Kanban system with a figure showing the flow of materials through different stages of production including receiving, fabrication, storage, and assembly lines. Kanban cards are used to signal the need to replenish materials and allow containers to move between stages only when authorized by a card. The key aspects of Kanban systems are also summarized such as only moving full containers with a card and not exceeding authorized production levels.
This document provides an overview of Kanban, an agile project management methodology. It begins with limitations of current systems like bottlenecks and bugs. Kanban was developed at Toyota to visualize workflow using cards on boards. It aims to limit work-in-progress by pulling work instead of pushing it. Key principles include incremental change and respecting current processes. Practices include visualizing workflow, limiting work-in-progress, managing flow, and improving collaboratively. Benefits are simplicity, reduced waste and costs, while limitations include difficulty resizing cards as demand changes. The document concludes with a quote from a project manager praising Kanban's visibility into the project status.
Kanban is a scheduling and inventory control system used in lean manufacturing that focuses on limiting work-in-progress. It was developed by Toyota to improve production flow and involves visualizing and limiting work, continuously improving processes, and focusing on smooth workflow. Kanban boards make work visible and help teams collaborate to improve communication, identify issues, and empower self-managed processes.
Kanban is a lean production system that uses visual signals to manage material flow. It aims to minimize waste through a pull-based system where downstream demand triggers upstream production. Developed by Toyota in the 1950s and based on supermarket replenishment techniques, kanban uses cards or other visual signals to authorize material movement between processes in a just-in-time manner. This helps control inventory levels and avoid overproduction by signaling needs for replenishment only when demanded by the next downstream process.
Scrum is an agile framework that focuses on delivering working software in short iterations called sprints, typically 2-4 weeks. Self-organizing teams work to complete items from a prioritized backlog list. Daily stand-up meetings and sprint planning, review, and retrospective ceremonies provide transparency and opportunities to inspect and adapt the process as needed. The framework aims to rapidly deliver business value through flexible and collaborative teamwork.
Pawel Brodzinski introduces the concept of Portfolio Kanban as a backdoor to organizational evolution. Portfolio Kanban addresses problems that arise from taking on too many concurrent projects, including context switching costs, lower quality work, and emergencies. It uses a visual board to manage total capabilities, commitments, and work in progress limits across all projects. Implementing Portfolio Kanban can result in fewer ongoing projects, fewer emergencies, healthier team work environments, and more slack time for teams.
Just In Time and Lean Operation Chapter PresentationSINGHZEE
This document provides an overview of lean operations and just-in-time (JIT) manufacturing. It discusses that JIT aims to produce goods with minimum lead time and lowest cost by eliminating waste. Toyota popularized JIT techniques like reducing setup times and implementing kanban systems. Key aspects of JIT include eliminating waste, reducing variability, and improving throughput by pulling materials based on demand. JIT requires close supplier partnerships and scheduling to achieve small lot sizes and low inventories. The document outlines tactics to implement JIT principles in both manufacturing and service industries.
Using lean to reduce prototype lead time 2006Chris Baichoo
The document discusses Watlow Batavia's efforts to reduce lead times for custom heating part prototypes from 12 weeks to 6 weeks using Lean concepts. It outlines four Kaizen events from 2003-2006 that standardized processes, created dedicated prototype cells, and reduced waste. As a result, productivity increased 34% from 2003-2006, sales doubled, and lead times were cut in half, improving competitiveness and ensuring the division's survival.
This document provides an overview of lean management principles and concepts. It discusses the origins and philosophy of lean management, including key terms like value-added activities and waste elimination. Push and pull scheduling methodologies are compared. Kanban is introduced as a just-in-time production planning and control tool. Continuous improvement processes and commonly used tools like 5S, kaizen, and quality circles are outlined. Organizational challenges to implementing lean management like cultural resistance and the importance of top management support are also highlighted.
The document discusses Kanban, a lean manufacturing system used to limit work in progress. It begins by providing background on the competitive business environment and need for companies to be responsive, flexible, and profitable. It then explains how Toyota originally used Kanban cards to limit inventory and align production with demand. The document defines key Kanban terms and concepts like withdrawal Kanban, production Kanban, work in process, pull systems, and takt time. It also contrasts Kanban with traditional MRP systems. Overall, the summary discusses how Kanban aims to optimize workflow and align production to customer demand through visual signals and limits on work in progress.
This document provides an introduction to Lean principles, methodology, tools and terminology. It discusses what Lean is, its history and key principles. Lean is a way to pursue value and eliminate waste from daily processes. This results in lower costs, reduced cycle times, fewer defects, improved customer satisfaction and employee morale. The document outlines various Lean concepts and tools, including the eight wastes, 5S, visual management, Kaizen (continuous improvement), standard work and mistake-proofing. It emphasizes identifying value, mapping value streams, establishing flow and pull, and seeking perfection through eliminating waste.
This document discusses lean based software development. It defines lean as maximizing customer value while minimizing waste. The ultimate goal is to provide perfect value to the customer through a waste-free process. Lean principles include optimizing the entire value stream, eliminating waste, building quality in, learning constantly, keeping processes improving, and engaging everyone. The document also discusses applying lean concepts like value stream mapping, takt time, and kanban to software development. It outlines seven principles of lean software development and defines various types of waste in software projects.
The document discusses lean production and the Toyota Production System. It defines lean production as using minimal inventories of raw materials, work in process, and finished goods while eliminating waste. The Toyota Production System is based on eliminating waste and respecting people. The seven types of waste are identified as overproduction, waiting time, transportation, processing, inventory, motion, and defects. Key aspects of lean implementation include value stream mapping, pull systems using kanban, continuous improvement, and respect for employees.
The document summarizes an intern's end of assignment report at Eaton Corporation in Waukesha, Wisconsin. Over the course of the internship, the intern assisted with an ISO audit to receive less than 3 findings, disposed of expired paint while updating inventory records, updated lead times for vendors in the system, implemented digital printing to reduce decal lead times, and designed a new layout for the paint shed. The intern gained experience with inventory management, purchasing, and continuous improvement systems and processes during plant tours and projects.
Kanban for software development - Get more with lessManoj K G
Kanban is a lean methodology originally used in Toyota's production system to visualize workflow and limit work-in-progress. It has since been adapted for software development to optimize flow and delivery of value to customers. The core Kanban practices include visualizing the workflow, limiting work-in-progress, managing flow, making process policies explicit, and improving collaboratively. Implementing Kanban for software development can provide advantages like increased teamwork, collaboration, and continuous process improvement through a kaizen culture.
DevOps adoption can provide quantifiable returns on investment through improved productivity and quality. Implementing DevOps practices in phases allows organizations to first achieve continuous testing, then continuous delivery, reducing cycle times. Automating processes like builds, testing, and deployments across development, QA and production environments increases staff capacity. Earlier defect detection through practices like "shift left" testing also reduces repair costs. Case studies show potential annual savings of millions from these effects. A DevOps adoption roadmap and workshops can help organizations assess current capabilities and identify high-impact practices to prioritize for their needs.
Transitioning to Kanban: From Theory to PracticeTechWell
You're familiar with agile and, perhaps, practicing Scrum. Now you're curious about Kanban. Is it right for your project? How does Kanban differ from Scrum and other agile methodologies? From theory to practice, Gil Irizarry introduces Kanban principles and explains how Kanban's emphasis on modifying existing processes rather than upending them results in a smooth adoption. Instead of using time-boxed units of work, Kanban focuses on continuous workflow, allowing teams to incrementally improve and streamline product delivery. Explore how to move from Scrum to Kanban with new, practical techniques that can help your team quickly get better. Discover the use of cumulative flow diagrams, WIP (work-in-progress) limits, and classes of services. In a hands-on classroom exercise, you'll help create a value stream map, determine process efficiency, and experience techniques from the Kanban toolset. Come and grow your agile repertoire in the Kanban way.
This document provides an introduction to Lean Six Sigma for Black Belt candidates. It outlines the goals of the Black Belt training program which are to understand and apply Lean Six Sigma tools and methods to solve problems, improve performance and achieve goals. The DMAIC process of Define, Measure, Analyze, Improve and Control is described as the model that will be applied to projects during the training. The training typically occurs over 4-6 months using a learn and apply approach with coached projects solving real problems in the organization.
Know about Just-In-Time and Lean manufacturing system. Find benefits and difference between JIT and Lean Manufacturing by Nilesh Arora, a founder of AddValue Consulting Inc.
The document discusses challenges with new product development and how lean principles can help address them. It provides examples of product development failures from Samsung, Coca-Cola, and Titanic due to issues like poor planning, lack of risk assessment, and not considering safety. Tesla is shown as successfully applying lean with different models at various volumes and prices. Key lean concepts discussed include simultaneous engineering, chief engineers, and visual management boards (Oobeya). Goodyear Tire is highlighted as improving on-time delivery from 27% to 90% and cycle time from 100 to 30 days by applying lean through matrix organization and other methods.
- Just-in-Time (JIT) and Total Quality Control (TQC) aim to improve efficiency and quality by reducing waste. JIT exposes problems while TQC eliminates constraints.
- JIT uses a pull system, small batch sizes, continuous flow, and kanban cards to minimize inventory and response times. TQC follows the plan-do-check-act cycle to continuously improve processes.
- The seven types of waste include overproduction, waiting time, transportation, inventory, unnecessary motion, defects, and excess processing. JIT and TQC work together to maximize customer value while using resources efficiently.
A Masterclass on Data Warehouse Automation Heath Turner
The document discusses a master class presentation on data warehouse automation using TimeXtender software. It introduces data warehouse automation as a new technology that can speed up the data warehouse development lifecycle through automation. TimeXtender claims to automate extract, transform, load processes and improve quality while reducing costs. Case studies and customer testimonials are presented to demonstrate how TimeXtender has delivered faster, better, and cheaper results for clients.
Lean Production can be defined as an integrated set of activities designed to achieve high-volume production using minimal inventories (raw materials, work in process, and finished goods).
The Toyota Production System
All work shall be highly specified as to content, sequence, timing, and outcome
Every customer-supplier connection must be direct, and there must be an unambiguous yes-or-no way to send requests and receive responses
The pathway for every product and service must be simple and direct
Any improvement must be made in accordance with the scientific method, under the guidance of a teacher, at the lowest possible level in the organization
This document discusses release cycles and delivery roadmaps. It provides guidance on designing well-balanced release cycles that consider constraints. Key points include defining a catalog of release cycles for different user story families, qualifying development steps as value-added or non-value added, assessing current cycles based on workload and lead time, and leveraging techniques like parallelization, continuous integration, and continuous improvement to reduce lead times. The goal is to balance steps for an acceptable ROI and define SLAs for each user story family's release cycle.
Modern production management tools discussed include JIT, Kanban, Kaizen, ISO, and Poka Yoke. JIT aims to minimize waste through just-in-time production that pulls materials as needed. Kanban uses visual signals like cards to control production flow. Kaizen focuses on continuous improvement. ISO standards help ensure quality. Poka Yoke uses mistake-proofing devices. Key aspects of each tool are outlined, such as how Kanban cards signal production needs and the benefits of ISO certification.
Kanban India 2022 | Ravi Shankar | DevOps CI-CD Pipeline is automated Kanban!LeanKanbanIndia
The document discusses how CI/CD pipelines parallel Kanban principles and processes. It explains that both Kanban and CI/CD pipelines aim to streamline workflow, reduce bottlenecks, and provide transparency through stage-by-stage work movement. The CI/CD pipeline inherently follows a value stream approach with a WIP limit of 1, planned reviews between stages, and aims to ensure smooth integration and delivery through automation. While CI/CD is often seen as a technology solution, it is actually underpinned by strong Lean and Kanban principles. Both methods bring similar business benefits like reduced costs, faster delivery, and improved customer satisfaction.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
This presentation provides valuable insights into effective cost-saving techniques on AWS. Learn how to optimize your AWS resources by rightsizing, increasing elasticity, picking the right storage class, and choosing the best pricing model. Additionally, discover essential governance mechanisms to ensure continuous cost efficiency. Whether you are new to AWS or an experienced user, this presentation provides clear and practical tips to help you reduce your cloud costs and get the most out of your budget.
Nunit vs XUnit vs MSTest Differences Between These Unit Testing Frameworks.pdfflufftailshop
When it comes to unit testing in the .NET ecosystem, developers have a wide range of options available. Among the most popular choices are NUnit, XUnit, and MSTest. These unit testing frameworks provide essential tools and features to help ensure the quality and reliability of code. However, understanding the differences between these frameworks is crucial for selecting the most suitable one for your projects.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Digital Marketing Trends in 2024 | Guide for Staying AheadWask
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
2. What is Kanban
• Japanese term for “signboard”
• A process first introduced by Taiichi Ohno in mid 20th century for Toyota
Production System.
• Taiichi introduced Kanban cards as “order cards”
• restock parts “just in time”
• reducing the inventory of unused parts
• improving production flow
• Real World examples
Introduction To Kanban
3. Benefits
• Improved quality
• Faster turnaround
• Identification and elimination of bottlenecks
• Reduction of wait time/ queue time
• Improved teamwork
• Reduction of waste
• Self managed team
Introduction To Kanban
4. Core Principles
Introduction To Kanban
Visualize your workflow
Limit your Work In Progress (WIP)
Manage flow
Make Process Policies Explicit
Improve Collaboratively - Kaizen
5. Littles Law
• According to John Little, the MIT Professor, The total number of customers
in a queueing system (L) is equal to the rate at which customers arrive and
enter the system (λ) multiplied by the average time per customer in the
queue (W).
L = λW
or
W = L / λ
• In software development this can be equated to
Number of WIP items = Lead Time to complete a WIP Item
Value added time spent on the WIP item
Introduction To Kanban
6. Work In Progress (WIP)
Introduction To Kanban
Issue
Reported
(15 mins)
Issue
Prioritization
(1 hour)
Develop a Fix
for the issue
(2 hours)
Test the fix/
patch
(3 hours)
Prepare fix
for release
(45 mins)
Production
Deployment
(1 hour)
4 days wait 5 days wait 4 days wait 4 days wait 4 days wait
Efficiency: 8 hours / 176 hours = 4.54% Limit WIP to 10
From Little’s Law: WIP = 176 / 8 = 22 items New Lead Time = WIP (10) * Value added time (8) = 80 hours
New Efficiency = 8 hours / 80 hours = 10%
Value added time - 8 hours
Wait Time – 21 days/ 168 hours
Lead Time – 176 hours
7. Work In Progress (WIP) cont.
Introduction To Kanban
Value added time - 8 hours
Wait Time – 21 days/ 168 hours
Lead Time – 176 hours
WIP – 22 Items
Efficiency – 4.54%
Increase Throughput
• Hire enough resources to reduce the Lead time to
80 hours
• Lets assume that the value added time is still the
same
• New Efficiency = 8 hours / 80 hours = 10%
Reduce WIP Items
• Reduce WIP items to 10
• We know from Little’s law
WIP = Lead Time / Value added time
or
Lead Time = WIP * Value added time
• New Lead time = 10 * 8 hours = 80 hours
• New Efficiency = 8 hours / 80 hours = 10%
10. Getting Started
• Establish your value stream – Backlog/ Design/ Dev/ Testing/
Deployment/ Complete
• Make your backlog explicit
• Prioritize your backlog
• Limit your WIP
• Have a column with blocked items
• Retrospect/ Reflect on tasks to improve process after completion
• Revisit Prioritization (JIT prioritization) every time you are done with a
current task and have capacity to add new items to the Doing
Introduction To Kanban
11. Prioritization – Time Management Matrix
Introduction To Kanban
Important
Urgent
Quality Quadrant
Important
But Non-urgent
Quadrant of Waste
Neither Important
Nor Urgent
Mission Critical
Quadrant
Important &
Urgent
Deception Quadrant
Not important
But Urgent
12. Microsoft Case Study 2004
Introduction To Kanban
Product Owners
PM 1 PM 2
PM 3 PM 4
DEV QA
Backlog
Deployment
155 days
13. Microsoft Case Study 2004 cont.
Steps taken by the new manager
• Visualize the work flow (diagram on prior slide)
• Analyze existing policies
• Estimation policy – new requests had to be estimated within 48 hours
• Minor changes policy – took priority and had expedited dev & test phase
• Prioritization policy – Backlog was prioritized once every month
Introduction To Kanban
14. Microsoft Case Study 2004 cont.
Changes enforced by the new manager
1. Stop estimating
2. Limit the Work-In-Progress
3. More Frequent Prioritization meetings
Promised lead time of 4 weeks
Introduction To Kanban
15. Microsoft Case Study 2004 cont.
Revised Workflow
Introduction To Kanban
Product
Owners
PM 2
DEV QA
Backlog
Deployment
25 days
PM 1
PM 3
PM 4
Input Queue
WIP Limit - 8
16. Microsoft Case Study 2004 cont.
Results
• Immediate Results:
• Lead time successfully reduced from 4 months to 4 weeks
• Weekly meetings were smoother
• Increased trust and collaboration between product owners and team
• By late 2005
• Backlog completely eliminated
• Lead time average reduced to 14 days
• SLA was met 98% of the time.
• Weekly prioritization meetings eliminated
Introduction To Kanban
17. References
• Kanban: Successful Evolutionary Change for Your Technology Business
• The Principals of Product Development Flow
Introduction To Kanban
Real World Examples:
Airline Tickets
An airline ticket tells the passenger which gate to go to, what time the boarding would start , which seat to go to etc. Think how lost the passenger would be without knowing any such information
Starbucks
If you ever pay attention to the cashier taking your Starbucks order, he/she always writes your name, the coffee you ordered and always places them in a queue so that the barista knows exactly which order is next and what coffee to brew. Imagine how difficult and inefficient would it be to not have this information or have the person who takes the order make your drink. As a matter of fact, Starbucks is a perfect example of how exactly to implement the Kanban process.
Supermarkets
Another great example of successful Kanban implementation are the supermarkets where goods are stocked for the consumers to pull from the shelves (demand) and are restocked only when the shelves are empty or low on stock rather than the production of these goods.
Visualize your workflow:
The goal of Kanban is to make positive change to optimize the flow of work through the system hence it is imperative that you know the entire workflow from beginning till the end.
Limit your WIP:
As Kanban implements the pull system it is critical that the WIP is limited and new work is pulled into the next stage only when there is available capacity. These constraints will quickly illuminate problem areas in your flow so you can identify and resolve them.
Manage flow:
The idea of implementing Kanban is adding value. For that, you need to look at how value is currently flowing through the system analyzing problem areas in which value flow is stalled and then defining and implementing, changes.
Make Process Policies Explicit:
Without an explicit understanding of how things work and how work is actually done, any discussion of problems tends to be emotional and anecdotal. Ex: Having an explicit policy of unit testing and code review before the code can be pulled forward for the testing phase.
Improve Collaboratively:
Kaizen in Japanese means continuous improvement and Kanban method encourages small continuous, incremental and evolutionary changes
In other words,
Length of the queue = Average Wait Time * Arrival Rate (L = λW)
Flipping this equation
Average Wait Time = Length of the queue / Arrival Rate (W = L / λ)
In software development this can be equated to
WIP = Lead Time (throughput) / value added time
or
WIP = total time to compete 1 WIP / actual time taken to complete the WIP
Imagine you have been tasked with increasing the efficiency of the above team to, lets say, 10%
You can achieve it 2 ways
Increase the throughput, ie. Hire more additional recourses to reduce the lead time to 80 hours
Efficiency = 8/ 80 = 10%
2. Another approach would be to limit the WIP to 10 items which means that our new lead time would be:
Lead Time = WIP (10) * value added time (8) = 80 hours
Efficiency = 8/80 = 10%
Hence limiting your WIP is so compelling and one of the most important principles of Kanban
While one may think highly about a TO-DO list, it has many limitations we don’t think of
Maintenance – How do we keep on editing and maintaining the TODO lists with time ?
Scalability – Work OK for a small scale task list. How do we PRIORITIZE, highlight ROAD BLOCKS, scale it for my team, re-writing stuff every time we get a set of new tasks ?
Outlook and Digital TO-DO – Digital TO-DO lists remove many of the manual overheads like re-writing, completing, flagging the tasks but they still are very poor with PRIORITIZATION, highlighting ROADBLOCKS and do not depict the WORK FLOW
Enter Kanban boards
Example of a simple Kanban Board
PRIORITIZE, PRIORITIZE, PRIORITIZE:
I cannot emphasize enough on the importance of prioritization. Imagine asking customer – can you please categorize the 100 requirements as High, Medium and Low and then realizing that the customer has marked 80 as high, 15 as medium and 5 as low making the expectations unrealistic.
Hence the key is to Prioritize. Rather, the question should have been – Please prioritize these 100 requirements from 1 to 100.
The above Kanban board prioritizes the tasks/ backlog items on the left most corner in the order of their priority (bottom to top)
Visualize Flow – Establish the value stream:
If you remember, a few slides ago, when we talked about the Principles of Kanban, we talked about visualizing the workflow. In the above Kanban board, the work items moves from left to right passing through each defined stage until they are moved to the completed stage.
WIP:
We also talked about limiting your WIP without which you would often find yourself overwhelmed with the tasks you are working on. The above board has the WIP limit set to 5
Blocked Item:Have a dedicated area on your story board/ Kanban board for items which are blocked due to external factors.
This helps you to make your work flow more productive.
Ex: Imagine that your WIP limit is 3 and all 3 of those items are blocked due to external factors (waiting for external teams to develop components to be integrated / waiting for business line to provide clarifications/ waiting paint to dry). Suddenly you find that you have ample time but cannot add more items to the WIP due to the set WIP limit .
In such scenarios, the blocked item comes in handy, but remember its not a procrastination block. It’s idea is to provide insight on the blocked items and determine the road blocks which we often oversee (covered in the case studies ahead)
Its generally a good idea to have a WIP limit and deadline on the tasks in this column too so that you don’t end up with a bunch of tasks in the blocked status.
According to Stephen Covey – keynote speaker the tasks can be prioritized by asking 2 simple questions:
Is the task urgent?
Is the task important
Mission Critical Quadrant:
This quadrant lists the tasks which are both urgent and important
Ex: Production Issues, Last minute defect preventing the project from going live.
These are the tasks one should consider while retrospection after task completion. The idea is to prevent such tasks rather than react to it.
Quality Quadrant:
This quadrant includes the tasks which are Important but not urgent
Ex: Improving the performance of an application, Developing a coding standards document
This quadrant is also referred as the quadrant of Kaizen (continuous improvement) as the tasks under this quadrant improve overall quality and efficiency – Investment into future
Quadrant of Deception:This quadrant lists the tasks which are urgent but not important.
Ex: Meetings/ Phone calls/ social interruptions etc.
While not all meetings and phone calls can be categorized as “non-important” but all of them can we tweaked to minimize waste and maximize value
Quadrant of Waste:
This quadrant lists the tasks which are neither important nor urgent
Ex: Idle Time/ Lunch, Surfing the internet etc.
Some of these tasks are truly a waste but still required to recharge your battries
Maintenance Team consisting of 1 manager, 3 developers and 3 testers.
This team took work requests from 4 different Product Owners who acted as Customers
Followed SDLC methodology
Produced a generally good quality application
Lead time for a new request was 5 months and backlog was ever growing
A new manager was brought in when the backlog size grew to 80 items to address these issues
Visualizing the work flow
Rate of request - 7 new requests per month
Backlog prioritization would happen once per month
Average engineering effort per request – 11 days but lead time was 155 days meaning over 90% of this lead time was waste.
Estimation Policy Effects
Customer expected accurate estimates
Required 1 day of developer and tester time which equated to 33% of available monthly team capacity
Minor Changes Policy Effects
Changes arrived without much warning
Expedited delivery
Requests were sporadic
Minor Changes Policy Effects
Each month around 75 items were prioritized and re-prioritized
Stop Estimating:Recover team capacity for development and testing
Eliminate variability caused by random intervals of incoming requests and estimates
Limit WIP:
Limit WIP for development and testing to 8
Add input queue between the backlog and development so that dev would always know about the next item to work on
More Frequent Prioritization
Weekly meetings
Limit the items to added to the Input Queue to 3 making these meetings shorter and thereby eliminating redundancy of re-prioritization
Ensured that the Input Queue would always be adequately filled
After the initial success of reducing the lead time, the process was evolved making additional policy changes like
Backlog items more that 6 months old to be purged
Large tasks and requests to be flagged by the developers and testers and would require management to take a look at the request
As soon as current item was completed, the team would notify the 4 product owners about WIP capacity via email and not wait until the weekly prioritization meetings
This was achieved without making any significant changes to the development and testing process except:
Limiting WIP
Estimating process