Kanban is an approach for optimizing workflow that uses visual cues and limits on work-in-progress to facilitate continuous improvement. It focuses on measuring and improving the flow of work rather than following a prescriptive process. Kanban is well-suited for teams focused on delivering services in response to requests. It aims to spark collaboration, identify and remove impediments, and stop partially completed work from piling up. Metrics like cycle time, throughput, and work item age help teams track progress and quality of their services over time.
Kanban is a lean methodology for managing workflow. It utilizes visual cues like kanban boards and cards to limit work-in-progress (WIP) and optimize flow. Key practices include visualizing the workflow, making policies explicit, managing flow, and continuously improving collaboratively through incremental changes. The overall goals are to balance demand with capacity, improve service delivery, and enable evolutionary change.
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.
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 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.
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.
The document outlines the rules for a team-based game where players are split into roles to collaboratively build Lego animals. The roles are legs developer, body developer, head developer and tester. The rules describe 5 rounds of play with different collaboration restrictions for each round to encourage teamwork and test different skills. The testers use dice to introduce random defects ("bugs") and determine if completed animals pass testing or must be returned to the appropriate developer role for repairs.
1) Kanban originated from the Toyota Production System and focuses on limiting work in progress to improve flow.
2) Kanban has two meanings - "signboard" which refers to visualizing work, and "signal card" which was used to signal production needs.
3) The Kanban method focuses on evolutionary change, respecting existing roles and encouraging leadership at all levels. It emphasizes starting to finish work and stopping the habit of starting new work.
This document provides information about Kanban and Lean Kanban training from Netmind and Lean Kanban University. It discusses Kanban practices like visualizing work, managing flow, making policies explicit, and implementing feedback loops. It promotes Lean Kanban University's accredited Kanban training and certifications, including the Team Kanban Practitioner and Kanban Management Professional programs. Contact information is provided for Miquel Rodriguez, a consultant director at Netmind, to obtain more details on Lean Kanban University courses and certifications available through Netmind.
Kanban is a lean methodology for managing workflow. It utilizes visual cues like kanban boards and cards to limit work-in-progress (WIP) and optimize flow. Key practices include visualizing the workflow, making policies explicit, managing flow, and continuously improving collaboratively through incremental changes. The overall goals are to balance demand with capacity, improve service delivery, and enable evolutionary change.
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.
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 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.
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.
The document outlines the rules for a team-based game where players are split into roles to collaboratively build Lego animals. The roles are legs developer, body developer, head developer and tester. The rules describe 5 rounds of play with different collaboration restrictions for each round to encourage teamwork and test different skills. The testers use dice to introduce random defects ("bugs") and determine if completed animals pass testing or must be returned to the appropriate developer role for repairs.
1) Kanban originated from the Toyota Production System and focuses on limiting work in progress to improve flow.
2) Kanban has two meanings - "signboard" which refers to visualizing work, and "signal card" which was used to signal production needs.
3) The Kanban method focuses on evolutionary change, respecting existing roles and encouraging leadership at all levels. It emphasizes starting to finish work and stopping the habit of starting new work.
This document provides information about Kanban and Lean Kanban training from Netmind and Lean Kanban University. It discusses Kanban practices like visualizing work, managing flow, making policies explicit, and implementing feedback loops. It promotes Lean Kanban University's accredited Kanban training and certifications, including the Team Kanban Practitioner and Kanban Management Professional programs. Contact information is provided for Miquel Rodriguez, a consultant director at Netmind, to obtain more details on Lean Kanban University courses and certifications available through Netmind.
Agile Testing: The Role Of The Agile TesterDeclan Whelan
This presentation provides an overview of the role of testers on agile teams.
In essence, the differences between testers and developers should blur so that focus is the whole team completing stories and delivering value.
Testers can add more value on agile teams by contributing earlier and moving from defect detection to defect prevention.
The document discusses Lean, Agile development methods, and how Agile principles relate to Lean. It provides background on Lean, describing how Agile emerged from principles that have existed for over 60 years in Lean manufacturing. Key Lean principles like eliminating waste, creating knowledge, building quality in, and respecting people are described. Agile fits these Lean principles through values like individuals over process, working software over documentation, and responding to change. Kanban is introduced as a Lean technique using visual boards to manage work flow.
The document discusses Agile and Kanban principles and practices. It defines Agile as focusing on early delivery of business value, continuous improvement, and flexibility. Kanban is introduced as a method for managing knowledge work using visual signals and limiting work in progress. The document outlines Kanban values like transparency and flow, principles like starting with the current process and incremental change, and practices like visualizing work, limiting WIP, and implementing feedback loops. It provides an example of how Kanban could be applied at an organization's support team.
This document describes one team's transition from Scrum to Kanban or "Scrumban". It outlines their typical Scrum process, including daily standups and weekly planning and retrospectives. It then discusses how they experimented with different work in progress limits on their Kanban board and the problems they encountered, such as bottlenecks. Finally, it notes how their process evolved more naturally over time with continuous improvement and that they retained stakeholder demos and retrospectives as needed rather than having fixed weekly meetings.
This document provides an overview of Kanban concepts and practices for improving workflow. It discusses how Kanban aims to visualize workflow, limit work-in-progress, encourage continuous flow and collaboration, and evolve processes experimentally through measurement and feedback. Key aspects covered include managing demand and capacity, understanding customers, focusing on flow and pull systems, setting work-in-progress limits, and continuously improving through reflection and data.
The document provides an overview of implementing Scrum with Kanban. It begins with definitions of Scrum and Kanban principles and practices. It then compares Scrum and Kanban approaches and outlines how Scrum events, roles and artifacts can be combined with Kanban practices like limiting work in progress, visualizing workflow and metrics. The remainder discusses the experience of one team that adopted Scrum with Kanban, including defining their workflow, setting work in progress limits and evolving their approach over time based on metrics.
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
The Agile Fluency Model outlines a journey through different zones of agility, including positive, investment, improvement, and inclusive zones. It focuses on shifting team culture, skills, and organizational structure over time through practices like co-locating teams, establishing clear priorities, and empowering teams. The goal is to help teams and organizations continuously optimize value delivery through metrics like frequent working software delivery and transparent progress visibility.
Agile Training: Roles and ExpectationsMike Wienold
The document provides an overview of roles and expectations in Agile training at Itron. It discusses the key roles of the Scrum Master, Product Owner, and Development Team. The Scrum Master facilitates meetings and removes impediments for the team. The Product Owner represents customers, prioritizes work, and accepts completed items. The cross-functional Development Team delivers working software each sprint and manages its own work. It also reviews the Agile process, sprint activities like planning and retrospectives, and expectations for each role.
The document provides the results of an Agile self-evaluation for a software delivery team. It finds that the team supports some Agile principles like prioritizing user stories and having generalist developers. However, it also finds practices that could be improved like more frequent integration builds and check-ins. The report recommends a more thorough assessment and continuous improvement program to help the team better adopt Agile practices.
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!
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.
Release wednesdays and the agile release train uploadChris Smith
The document discusses the benefits of using an "Agile Release Train" approach for software development. Some key points:
- An Agile Release Train plans work in train-like themes that are delivered on a regular cadence, such as every 2 weeks. This provides a predictable release rhythm.
- Work is broken into small, independently releasable increments called user stories. If a story is not ready for the current release, it waits for the next one.
- Planning occurs through story mapping epics and stories to future releases. The plan is updated each sprint to reflect progress and priority changes.
- Benefits include clear focus on current work, visibility of priorities and timelines, and
Kanban vs Scrum: What's the difference, and which should you use?Arun Kumar
Originally presented at the 207 Lean Transformation Conference, this presentation provides a practical introduction to Scrum, particularly for public sector employees, and guides you to deciding whether Kanban or Scrum will work best for your teams and projects.
Kanban is a scheduling system for lean manufacturing and just-in-time manufacturing. Kanban is an inventory-control system to control the supply chain. Taiichi Ohno, an industrial engineer at Toyota, developed kanban to improve manufacturing efficiency.
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.
Scrum Bangalore 18th Meetup - October 15, 2016 - Elasticity of Kanban - Saika...Scrum Bangalore
The document discusses scaling Kanban across teams and organizations. It describes expanding Kanban in three dimensions: width, height, and depth. Width involves extending the workflow upstream and downstream. Height involves linking different levels of work from portfolio to personal tasks. Depth involves visualizing and managing interdependent services across shared resources. The document provides examples and recommendations for coordinating Kanban at scale, including common metrics, managing work in progress limits, and benefits of scaling Kanban such as increased flow and throughput.
Advanced Lean Training Manual Toolkit.pptThinL389917
The document discusses the concept of standardization and its importance in lean processes. It makes three key points:
1) Standardization prevents waste from occurring, exposes existing waste to identify areas for improvement, and increases flexibility.
2) There are two levels of standardization - standard activities and standard connections between activities. Standardizing connections is especially important for reducing waste in office environments.
3) Standardization forms the basis for other lean tools like visual management, mistake proofing, and continuous improvement through kaizen events by establishing a normal process and making abnormalities visible.
Agile Testing: The Role Of The Agile TesterDeclan Whelan
This presentation provides an overview of the role of testers on agile teams.
In essence, the differences between testers and developers should blur so that focus is the whole team completing stories and delivering value.
Testers can add more value on agile teams by contributing earlier and moving from defect detection to defect prevention.
The document discusses Lean, Agile development methods, and how Agile principles relate to Lean. It provides background on Lean, describing how Agile emerged from principles that have existed for over 60 years in Lean manufacturing. Key Lean principles like eliminating waste, creating knowledge, building quality in, and respecting people are described. Agile fits these Lean principles through values like individuals over process, working software over documentation, and responding to change. Kanban is introduced as a Lean technique using visual boards to manage work flow.
The document discusses Agile and Kanban principles and practices. It defines Agile as focusing on early delivery of business value, continuous improvement, and flexibility. Kanban is introduced as a method for managing knowledge work using visual signals and limiting work in progress. The document outlines Kanban values like transparency and flow, principles like starting with the current process and incremental change, and practices like visualizing work, limiting WIP, and implementing feedback loops. It provides an example of how Kanban could be applied at an organization's support team.
This document describes one team's transition from Scrum to Kanban or "Scrumban". It outlines their typical Scrum process, including daily standups and weekly planning and retrospectives. It then discusses how they experimented with different work in progress limits on their Kanban board and the problems they encountered, such as bottlenecks. Finally, it notes how their process evolved more naturally over time with continuous improvement and that they retained stakeholder demos and retrospectives as needed rather than having fixed weekly meetings.
This document provides an overview of Kanban concepts and practices for improving workflow. It discusses how Kanban aims to visualize workflow, limit work-in-progress, encourage continuous flow and collaboration, and evolve processes experimentally through measurement and feedback. Key aspects covered include managing demand and capacity, understanding customers, focusing on flow and pull systems, setting work-in-progress limits, and continuously improving through reflection and data.
The document provides an overview of implementing Scrum with Kanban. It begins with definitions of Scrum and Kanban principles and practices. It then compares Scrum and Kanban approaches and outlines how Scrum events, roles and artifacts can be combined with Kanban practices like limiting work in progress, visualizing workflow and metrics. The remainder discusses the experience of one team that adopted Scrum with Kanban, including defining their workflow, setting work in progress limits and evolving their approach over time based on metrics.
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
The Agile Fluency Model outlines a journey through different zones of agility, including positive, investment, improvement, and inclusive zones. It focuses on shifting team culture, skills, and organizational structure over time through practices like co-locating teams, establishing clear priorities, and empowering teams. The goal is to help teams and organizations continuously optimize value delivery through metrics like frequent working software delivery and transparent progress visibility.
Agile Training: Roles and ExpectationsMike Wienold
The document provides an overview of roles and expectations in Agile training at Itron. It discusses the key roles of the Scrum Master, Product Owner, and Development Team. The Scrum Master facilitates meetings and removes impediments for the team. The Product Owner represents customers, prioritizes work, and accepts completed items. The cross-functional Development Team delivers working software each sprint and manages its own work. It also reviews the Agile process, sprint activities like planning and retrospectives, and expectations for each role.
The document provides the results of an Agile self-evaluation for a software delivery team. It finds that the team supports some Agile principles like prioritizing user stories and having generalist developers. However, it also finds practices that could be improved like more frequent integration builds and check-ins. The report recommends a more thorough assessment and continuous improvement program to help the team better adopt Agile practices.
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!
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.
Release wednesdays and the agile release train uploadChris Smith
The document discusses the benefits of using an "Agile Release Train" approach for software development. Some key points:
- An Agile Release Train plans work in train-like themes that are delivered on a regular cadence, such as every 2 weeks. This provides a predictable release rhythm.
- Work is broken into small, independently releasable increments called user stories. If a story is not ready for the current release, it waits for the next one.
- Planning occurs through story mapping epics and stories to future releases. The plan is updated each sprint to reflect progress and priority changes.
- Benefits include clear focus on current work, visibility of priorities and timelines, and
Kanban vs Scrum: What's the difference, and which should you use?Arun Kumar
Originally presented at the 207 Lean Transformation Conference, this presentation provides a practical introduction to Scrum, particularly for public sector employees, and guides you to deciding whether Kanban or Scrum will work best for your teams and projects.
Kanban is a scheduling system for lean manufacturing and just-in-time manufacturing. Kanban is an inventory-control system to control the supply chain. Taiichi Ohno, an industrial engineer at Toyota, developed kanban to improve manufacturing efficiency.
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.
Scrum Bangalore 18th Meetup - October 15, 2016 - Elasticity of Kanban - Saika...Scrum Bangalore
The document discusses scaling Kanban across teams and organizations. It describes expanding Kanban in three dimensions: width, height, and depth. Width involves extending the workflow upstream and downstream. Height involves linking different levels of work from portfolio to personal tasks. Depth involves visualizing and managing interdependent services across shared resources. The document provides examples and recommendations for coordinating Kanban at scale, including common metrics, managing work in progress limits, and benefits of scaling Kanban such as increased flow and throughput.
Advanced Lean Training Manual Toolkit.pptThinL389917
The document discusses the concept of standardization and its importance in lean processes. It makes three key points:
1) Standardization prevents waste from occurring, exposes existing waste to identify areas for improvement, and increases flexibility.
2) There are two levels of standardization - standard activities and standard connections between activities. Standardizing connections is especially important for reducing waste in office environments.
3) Standardization forms the basis for other lean tools like visual management, mistake proofing, and continuous improvement through kaizen events by establishing a normal process and making abnormalities visible.
"How we switched to Kanban and how it integrates with product planning", Vady...Fwdays
The practical application of the Kanban development approach, its features at Uklon, and the reason we call it Kanplan. This topic will cover the following questions: - Philosophy of Kanban
How we got to Kanban methodology; - What key metrics we use; - Why Kanban is not just about support, but also about active development; - Where to start setting up and what to monitor at the start; - Our practice of building the product plan and how it is connected to Kanplan
A Kanban is a method for visualizing and managing work to improve workflow. It uses a board with columns to track work from initial collection to completion. The key steps are to collect all work, prioritize it, and assign and complete tasks as quickly as possible. Terminology includes epics (large goals broken into user stories), a backlog to prioritize work, and columns for work that is doing/blocked or done. Teams can implement Kanban boards and ceremonies like stand-ups and retrospectives to manage their process.
Kanban is a scheduling system used in lean manufacturing to improve workflow efficiency. It involves visualizing workflow, limiting work-in-progress, measuring and managing flow, making policies explicit, and implementing feedback loops to iteratively improve processes. The key aspects of Kanban include using boards to visualize workflow and WIP limits, evolving processes experimentally through small changes, and respecting existing roles and responsibilities when first implementing Kanban.
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 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.
Artem Bykovets: Optimizing efficiency of Value Delivery vs keeping people bus...Lviv Startup Club
Artem Bykovets: Optimizing efficiency of Value Delivery vs keeping people busy: how it is connected? (UA)
Ukraine Online PMDay 2023 Winter
Website - www.pmday.org/online
Youtube - https://www.youtube.com/startuplviv
FB - https://www.facebook.com/pmdayconference
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.
Kanban Development And The Paradigm Of FlowAlisson Vale
That was the title of my presentation on Oct 8th 2009 at Agiles 2009, 2nd Latin-American conference on Agile Development Methodologies. I have designed this presentation trying to summarize what the Kanban community is trying to spread recently as a new way to manage knowledge work.
- The document describes how a large organization with 15 software teams scaled agile practices to manage interdependent projects across teams.
- Key practices included all-at-once planning to coordinate work and dependencies, classes of service to prioritize work for shared resources like operations, and daily stand-ups focused on deliverables rather than individual team work.
- Teams adopted continuous delivery practices and metrics to guide planning and reduce cycle times, while releases remained iterative to accommodate testing and changes near the end of iterations.
This document provides an introduction to the Kanban method. It begins with an agenda for discussing what Kanban is, the Kanban method, applying upstream Kanban, applying Kanban to Scrum, and includes a Q&A section. The document then discusses the key aspects of the Kanban method including visualizing workflow with Kanban boards, limiting work-in-progress with WIP limits, managing flow, making policies explicit, implementing feedback loops, and improving collaboratively through experimentation. It also discusses how Kanban can help teams become more lean by eliminating waste. The document concludes by discussing how Kanban can be applied to both Scrum processes and other domains beyond software development.
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.
David Lowe introduces Kanban, a lean method for knowledge work. Kanban focuses on evolutionary, not revolutionary change by starting with the current process and respecting existing roles. The core Kanban principles include visualizing workflow, limiting work-in-progress, managing flow, making policies explicit, using feedback loops, and making continuous improvements. Kanban aims to optimize flow and identify bottlenecks through measuring and limiting work-in-progress.
Lean Kanban India 2019 Conference | Scrumban comes to the rescue: A Case Stud...LeanKanbanIndia
Session Title: Scrumban comes to the rescue: A Case Study
Abstract: In this case study, we discuss the challenges faced by the customer and the project team and how Scrumban helped the customer navigate through these challenges. We highlight how Metrics helped the team in its planning, forecasting and identifying their Continuous Improvement steps.
A survey of Kanban, a software development practice, its history, why people are using it, how to start using it, why it works, criticisms of it, advanced techniques, some general advice and a selected set of references,
Using Kanban techniques can help control incremental software development. Kanban uses visual cards to limit work in progress, similar to how Toyota used cards in manufacturing. A Kanban system for software involves defining a workflow, creating a visual board, setting limits on work in queues, prioritizing goals, and moving work through the process. Measuring cycle times and addressing bottlenecks can further improve the flow of work. Regular inspections of products and processes also help when using Kanban for incremental development.
This document discusses using Kanban techniques to control incremental software development. It covers what a Kanban system is and how it can be applied to software development. The document provides guidance on how to set up a development team Kanban system, including defining the workflow process, creating a visual Kanban board, setting work in progress limits, prioritizing goals, and moving work through the process. It also discusses techniques like decomposing large tasks, using cumulative flow diagrams, and incorporating regular process inspections. The overall aim is to focus the team on continuous flow and detecting/resolving bottlenecks to improve delivery of work.
This document outlines the STATIK (System Thinking Approach to Implementing Kanban) methodology for coaching new teams. STATIK is an iterative approach that uses systems thinking to understand existing processes. The 8 steps of STATIK are: 1) Understand the business purpose, 2) Understand sources of dissatisfaction, 3) Analyze demand types, 4) Analyze demand and delivery capabilities, 5) Model workflows, 6) Identify classes of service, 7) Design the Kanban system, and 8) Socialize the design and negotiate implementation. Examples are provided for several of the steps. The overall goal is to help teams implement Kanban by first analyzing their current processes and workflows.
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.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
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.
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
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
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
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.
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.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
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.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...Tatiana Kojar
Skybuffer AI, built on the robust SAP Business Technology Platform (SAP BTP), is the latest and most advanced version of our AI development, reaffirming our commitment to delivering top-tier AI solutions. Skybuffer AI harnesses all the innovative capabilities of the SAP BTP in the AI domain, from Conversational AI to cutting-edge Generative AI and Retrieval-Augmented Generation (RAG). It also helps SAP customers safeguard their investments into SAP Conversational AI and ensure a seamless, one-click transition to SAP Business AI.
With Skybuffer AI, various AI models can be integrated into a single communication channel such as Microsoft Teams. This integration empowers business users with insights drawn from SAP backend systems, enterprise documents, and the expansive knowledge of Generative AI. And the best part of it is that it is all managed through our intuitive no-code Action Server interface, requiring no extensive coding knowledge and making the advanced AI accessible to more users.
2. 2
2
• Introduction to Kanban
• Understand the basic definition of Kanban, and experience a simulation
• Kanban Theory
• Understand Pull vs Push and how limiting WIP can create a pull system
• Flow & Metrics
• Understand how we can measure flow of value and how to interpret the 4 key metrics
• Summary
• Understand when and where Kanban can / should be used
What is covered?
2 2 CONFIDENTIAL | October 2020
3. 3
3
Kanban – Truth or Myth?
3
Truth? Myth?
Kanban is for process improvement, not workflow
Kanban can only be used for linear processes, or support teams
Kanban is easy to implement
The earlier we start work, the sooner we will finish it
Better to start with Scrum, then move onto Kanban
Kanban is just a board with ‘tickets’ on it
You cannot do long range planning with Kanban
Kanban is only for a team
4. 4
4
Kanban is an approach for optimising the flow of value through a process that uses a visual,
pull-based system. There may be various ways to define value, including consideration of
safety, the needs of the customer, the end-user, the organization, and the environment
Kanban
4 4 CONFIDENTIAL | October 2020
6. 8
8
3 Practices
8
Definition of Workflow (DoW)
Fundamental concept of Kanban
Defined by Kanban system team
members
Defining and
visualising a workflow
Actively managing
items in a workflow
Improving a workflow
Control WIP
Avoiding work items piling up
Ensuring work items do not age
unnecessarily
Unblocking blocked work.
Continuous Improvement
Kanban team members
continuously improve the DoW
7. 9
9
At minimum, members must create their DoW using all of the following elements:
• A definition of the individual units of value that are moving through the workflow. These
units of value are referred to as work items (or items).
• Defined points at which work items are considered to have started / committed and to
have finished / delivered.
• One or more defined states that the work items flow through from started to finished. Any
work items between a start point and an endpoint are considered work in progress (WIP).
• A definition of how WIP will be controlled from started to finished.
• Explicit policies about how work items can flow through each state from started to finished.
• A service level expectation (SLE), which is a forecast of how long it should take a work item
to flow from started to finished.
Definition of Workflow
9 9 CONFIDENTIAL | October 2020
8. 10
10
Exercise
• Split into 4 groups
• 2 Questions to answer:
• What examples do you have of Projects?
• What examples do you have of Products?
Once back in the room – discuss what success looked like for the Projects and Products
5 minutes in rooms, plus 5 minute discussion
Products
10 10 CONFIDENTIAL | October 2020
10. 12
12
Value
12 12 CONFIDENTIAL | October 2020
Exercise
• Split into 4 groups
• 1 Question to answer:
• What is ‘value’ in your Team / Squad / Unit
Open discussion to talk through Value, and who the Customer
was for the value delivered
5 minutes in rooms, plus 5 minute discussion
12. 15
15
Flow
15
There are 4 main Flow Metrics to help a team optimise flow
of value through the system:
• WIP
• Cycle Time
• Throughput
• Work Item Age
13. 16
16
16
Work Item Age
The amount of time between when a Work Item started and the current
time
Chart to use
Aging WIP Chart
What is it?
Chart What to watch for
X-Axis represents your workflow
(from DoW)
Y-Axis is the current age in days
(from when it started)
Uses Cycle Time percentiles to plot
your likelihood of delivering
Items in green areas are being
delivered under your 70th percentile
Items above that are at risk of going
over that
Teams can take action early to discuss
problems with flow
Aging WIP Chart
16. 20
20
20
Cumulative Flow
Diagram (CFD)
A flow chart which is able to demonstrate Total WIP and Average
throughput
What is it?
Chart What to watch for
X-Axis represents time
Y-Axis is the number of work items
Shows the number of work items in
each stage of the workflow at that
point in time
Top line growing faster than bottom
line
Increasing bands
Top line and bottom line meeting
(starving the system)
18. 22
22
22
Cycle Time
What is it?
The amount of elapsed time between when a work item started and when
a work item finished.
Chart to use
Cycle Time Scatterplot
Chart What to watch for
Shows the time taken for each work
item to get to ‘Done’
X-Axis is the date the work was
done
Y-Axis is the number of days
Each dot represents a single work
item
Horizontal Percentile lines are
drawn to show % of the time work
was done, e.g.
50% of the time, work is done
in 30 days or less
Trends – getting slower or faster
Outliers
Blockers (in red below)
Percentile lines, to inform your SLE
We want low cycle times!
Cycle Time Scatterplot
20. 24
24
24
Throughput
What is it?
The number of work items finished per unit of time
Chart to use
Throughput Histogram
Chart What to watch for
Shows the number of completed
items in a given period of time
X-Axis is the number of work items
Y-Axis how many days this
throughput occurred
Vertical Percentile lines are drawn
to show a probabilistic view of
likely future
We want to produce more items per
day
Percentile lines, to inform your SLE
Throughput Histogram
22. 26
26
SLE
26
Service Level Expectations
A Forecast of how long it should take a Work Item to flow
from Started to Finished
Cycle Time Scatterplot can give you percentiles, i.e. 80% of
the time, we deliver a work item in 25 days.
Best guess until your system becomes predictable
“80% confidence that a Work Item will be done in 25 days or
less.”
27. 31
31
Quiz
Reinventing westlake | May 2020 | Confidential
31
In teams:
Prepare 5 questions
5 mins to prepare
Each team will ask up to 3 questions of the others in the
course.
28. 32
32
Agility
32
Introduce sustainable work Focus on Flow
Pull not Push
Summary
Controlling WIP is one way to
create a pull system
Pull work when Team is ready
Protect people from
overburdening
Spark collaboration
Identify & Remove
impediments
Stop Starting and Start
Finishing
The less work in progress,
the more work gets done
Powerful metrics to help
29. 33
33
When to use Kanban
33
You want to introduce
sustainability of work and
protect people from
overburdening.
Service delivery lens is a
natural fit for your work as
you work is request-based
(e.g. support team, shared
services/global teams)
You want to spark more
collaboration across
involved parties
Not enough focus on
solving impediments and
blockers as soon as
possible
Powerful flow metric to
track improvement and
quality of service.
Stop starting and start
finishing!
(and bring more
predictability to what you
do)
No process existing / work
requires vastly novel,
creative approach every
single time.
31. 35
35
For formal training and coaching see you Agile Coach and continue your
journey with assessments of your knowledge and practicing Kanban.
Want to know more?
35
Editor's Notes
Module 1 : Introduction to Kanban
Understand the basic definition of Kanban, and experience a simulation which they can relate to in their own context. They should be able to describe what is not working in their environment. Make a note this is not ‘The Kanban Method’ which is covered in the formal training in myT&L (although coaches can feel free to introduce elements of the Kanban Method if desired).
Module 2 : Kanban Theory
Understand Pull vs Push, explain how Kanban can help create a pull system and understand the basics of limiting WIP.
Module 3 : Flow & Metrics
Understand how we can measure Flow of Value through a Kanban System, and how to interpret 4 key metrics and charts.
Module 4 : Summary
Link training to their own context, understand how Kanban can help their workload. Should we include some commitments from the team?
These are all Myth.
Learning Outcome: establish with delegates where they think they are. This can take 15-20 mins depending on discussion points.
Learning Outcome: Basic definition of Kanban. NB This is not ‘The Kanban Method’ which includes more around organizational change etc. This is the basics needed to establish flow.
Focus on flow and value on this slide.
Learning Outcome: Experience Kanban, will likely be a bit chaotic.
Reflect on the exercise – 5 mins.
What did they observe in the game?
How did it feel?
What parallels can you draw from this to your current work environment?
<Add facilitator notes!!>
Skip Rules Dialog * Pause Game * Explain rules * Start game
We will run for 10 days.
Reflect on the exercise – 5 mins.
What did they observe in the game?
How did it feel?
What parallels can you draw from this to your current work environment?
Skip Rules Dialog * Pause Game * Explain rules * Start game
We will run for 10 days.
Make sure intro…
Use Henrik Knibergs game (and credit him when you run it please)
http://www.crisp.se/henrik.kniberg/multitasking-name-game
Use the PDF. We can create a Mural board to simulate using pens and paper.
Usually, it is good to get the Team Leader of a team being the ‘Worker’. Not mandatory though.
Also good if the teams are well known to each other, to give them different names they can use, and to ask the ‘Customers’ to create chaos, e.g. forget which letter they are on etc.
Learning Outcome: These are the only 3 mandatory practices in Kanban in order to crate a pull system and establish Flow. Again, the Kanban Method builds upon these for their 6 Practices. These 3 fundamental practices are needed to establish flow.
There are no Roles defined in Kanban Systems.
There are no Events defined in Kanban Systems, however teams will often establish their own cadence in order to manage these practices, e.g. Retrospectives, Replenishment.
DO NOT mix up Scrum events with this, e.g. Sprint Planning belongs in Scrum.
Learning Outcomes: Have something which allows teams to establish their own working agreements with Kanban systems and flow. This creates transparency.
Again, these are the minimum items needed to establish flow. You can build on these if needed, but teams should start somewhere.
SLE will be covered more later, but introduce the concept here
Learning Outcome: Introduce the concept of a Product, and the agile mindset around product delivery (rather than a project plan being delivered).
Projects would be things they have been asked to deliver, e.g. compressor overhall, fpso delivery etc. The key thing is a project is a sequence of tasks to be completed to get an output. Success of a Project is driven by delivery of Scope on Time and On Budget.
Products – iPad, Phone, car – items which can be improved upon, they have value to the customer, can be used. Success of the product is driven by users (they love it, hate it) and revenue for the company.
We are looking to get people focusing on Products at the outcome of their work – which have value.
Learning Outcome: There is always a Product.
Every product has a customer – someone who gets value from your product.
Every product has a producer – someone who gets a benefit (revenue, cost savings, society)
Optional: Ask delegates to give examples where there is NOT a product. Work with them to show what the product is in their examples.
Delegates should bring their context to this, what is valuable to them, what do they deliver that has value.
Value as gained by successful completion of the activity. Value may be estimated using tangible or quantitative measures (e.g., mboe, $m, NPT reduced, cost of delay); or using largely intangible or qualitative measures (e.g., strategic, reputational, feel); or some combination of both
Remember difference between current value and potential value. We don’t really know the value of something until we deliver it – we only have an estimate of potential value until then.
Learning outcome: Working to understand where WIP limits bring back a degree of control.
Reflect on the exercise – 5 mins.
What did they observe in the game?
How did it feel?
What parallels can you draw from this to your current work environment?
<Add facilitator notes!!>
Skip Rules Dialog * Pause Game * Explain rules * Start game
We will run for 10 days.
Reflect on the exercise – 5 mins.
What did they observe in the game?
How did it feel?
What parallels can you draw from this to your current work environment?
<Add facilitator notes!!>
Skip Rules Dialog * Pause Game * Explain rules * Start game
We will run for 10 days.
Learning Outcome: Introduction of the 4 key metrics, and how they can help. We have just completed an exercise in understanding WIP, so we can to a bit deeper here.
Cover WIP fully.
Work In Progress – all of the work between a defined Start Point and the End Point (as per the DoW). If it is past the start point, and not done yet, it is Work in Progress.
Introduce the other concepts briefly. More detail coming in next 3 slides.
Cycle Time – the amount of elapsed time between the point a work Item Started and when it Finished. “How long did it take to get completed”
Throughput – the number of workitems finished per unit of time, e.g. we finished 5 items in a week (7 days).
Work Item Age – the amount of elapsed time between the point a Work Item started and ‘now’.
This is the only ‘leading’ indicator, and is a teams most powerful metric for use in detecting problems with flow and making interventions.
Learning Outcome: understand how to read the chart and what actions could be taken. The X-Axis is the stages of the workflow for this team, everything is WIP.
Flowing reasonably well, perhaps something to look at towards the end. Are we focussing on work at the start? Are we pulling in work before finishing work?
Lots of issues, aging right from the start, no longer predictable
Focus in the early stages, but major issues towards the end – we are not going to deliver on ‘time’
Looking good, but perhaps should think about swarming on the last 3 items.
Learning Outcome: If we start with Kanban, what happens. What differences do the teams see. Usually, more work will get done in this round than in Round 1 and 2 combined.
Reflect on the exercise – 5 mins.
What did they observe in the game?
How did it feel?
What parallels can you draw from this to your current work environment?
Skip Rules Dialog * Pause Game * Explain rules * Start game
We will run for 10 days.
Reflect on the exercise – 10 mins.
What did they observe in the game?
How did it feel?
What parallels can you draw from this to your current work environment?
Metrics – what did they see
“Doing less will get more done”
Learning Outcome: understand how to read a CFD.
Look at the trend lines. Where is Total WIP?
Make sure we understand that this shows you approximate average cycle times and throughput.
Feel free to introduce Littles Law here, but make it clear that littles law is a relationship, not a formula.
Learning Outcome: How to spot trends in a CFD, and what actions could be taken.
Examples of CfD plots – delegates invited to speak about what can be seen from each one
Lines diverging – crocodile jaws
Stepped delivery – releasing in cycles / iterations?
Flat lines – was no-one working?
Cumulative Flow Diagram (brodzinski.com)
Learning Outcome: Understand Cycle Time and how to read the chart. What outliers are there, and how to have the conversation.
Cycle Time and Lead Time are basically the same. Sometimes you may have Customer Lead Time and Systems Lead Time (Kanban Method), but fundamental understating of cycle time is what we are after here. The additional training can go into the nuances of this.
Learning Outcome: How to spot trends in Cycle Time.
Increasing Cycle Time, look at the flow, Wip limits, etc.
Clusters – tricky to analyse, but worth finding out what is causing things to cluster together.
Gaps – we are not delivering consistently
All over the place! Not predictable.
Learnining Outcome: understand Throughput, and how to read the chart.
81 Days we produced nothing (throughput 0), 25 days was 1, 18 days was 2, 8 days we produced 3 items, 8 days we produced 4 items, 2 days we produced 5 items.
95% of the time, we produce 5 items or less, 85% of the time we produce 3 items or less, 50% of the time we produce no items.
Learning Outcome: Understand SLE as a forecast that can be used by teams to help them understand how much work they can get done, and to have conversations with their customer. The more predictable a system is, the better.
Emphasise the wording – it is a forecast, not a promise. Avoid: “It will be done in 10 days” for example.
Go back to the Cycle Time Scatterplot to show the percentiles.
This is only valid once your system becomes predictable. Ask how we can see if we are predictable (Cycle Time Scatterplot and CfD)
Learning Outcome: Spot the items from the Definition of Workflow, and any other visualisations that are apparent on the picture.
What can you see in the examples?
What can you see in the examples?
What can you see in the examples?
Learning Outcome: Spot the items from the Definition of Workflow, and any other visualisations that are apparent on the picture.
Learning Outcome: Solidify the learnings from the delegates by getting them to teach back some of the topics.
They can use Mural, slides, flipcharts etc etc – up to them, allow them to be creative.
Learning Outcome: Reminder of what Kanban can do, pull systems and establish flow. Doing less work will get more done.