CMMI Capability Counts conference key note. Evolutionary change and the new Kanban Maturity Model as an alternative to enterprise scaled Agile methodologies
Very frequently, when we discuss a change initiative failure, we point as one of key reasons of the failure lack of support from top management. Much effort on team level is wasted because the organization on high level is set up to preserve status quo.
For a change agent looking to set an organization on a path on continuous, evolutionary change addressing the issue of stale mindset of the leaders of the company is frequently the key obstacle to overcome. Usually, a different set of tools is required to achieve that, especially for internal change agents who have hierarchy working against them.
I will show how we can use Portfolio Kanban as a low-friction method, which might be used by change agents, to steer mindset change among top managers. Similarly to team-level Kanban a few simple rules help to change how we look at project or product portfolio and how the work flows on high level.
Thinking about Kanban on portfolio level introduces the whole new set of challenges that can’t be solved with standard approach, so it is also a story about Kanban versatility and adaptability.
After all, if end results include better understanding of how the work is done, improved effectiveness and healthier work environment for teams it is worth giving a try, isn’t it?
Scalability is currently a big topic in the agile world. Most agile methods and practices often reach their limits when one wants to “agilize" more than a few teams, let alone one wants to achieve real agile collaboration of several hundert people.
The main problem is that many agile methods focus on the team. Kanban follows a completely different path - Kanban is not a team method! Kanban is a management method which focuses on generating value. "Manage work and not workers" is one of the key messages of the Lean Kanban management philosophy. Therefore, scalability is not a real topic within Kanban: if you focus on value generation of work, scaling Kanban simple means doing more Kanban - it’s inherent scalable.
In this session I show how one could use Kanban at scale. Besides the general schematic explanation I will also show a case study where Kanban is used to coordinate work of more than 200 people.
Very frequently, when we discuss a change initiative failure, we point as one of key reasons of the failure lack of support from top management. Much effort on team level is wasted because the organization on high level is set up to preserve status quo.
For a change agent looking to set an organization on a path on continuous, evolutionary change addressing the issue of stale mindset of the leaders of the company is frequently the key obstacle to overcome. Usually, a different set of tools is required to achieve that, especially for internal change agents who have hierarchy working against them.
I will show how we can use Portfolio Kanban as a low-friction method, which might be used by change agents, to steer mindset change among top managers. Similarly to team-level Kanban a few simple rules help to change how we look at project or product portfolio and how the work flows on high level.
Thinking about Kanban on portfolio level introduces the whole new set of challenges that can’t be solved with standard approach, so it is also a story about Kanban versatility and adaptability.
After all, if end results include better understanding of how the work is done, improved effectiveness and healthier work environment for teams it is worth giving a try, isn’t it?
Scalability is currently a big topic in the agile world. Most agile methods and practices often reach their limits when one wants to “agilize" more than a few teams, let alone one wants to achieve real agile collaboration of several hundert people.
The main problem is that many agile methods focus on the team. Kanban follows a completely different path - Kanban is not a team method! Kanban is a management method which focuses on generating value. "Manage work and not workers" is one of the key messages of the Lean Kanban management philosophy. Therefore, scalability is not a real topic within Kanban: if you focus on value generation of work, scaling Kanban simple means doing more Kanban - it’s inherent scalable.
In this session I show how one could use Kanban at scale. Besides the general schematic explanation I will also show a case study where Kanban is used to coordinate work of more than 200 people.
Enterprise Services Planning: Defining Key Performance IndicatorsDavid Anderson
Defining KPIs for use in Enterprise Services Planning and with Kanban systems. Understanding the difference between KPIs, Improvement Guides, and General Health Indicators. Understanding how KPIs drive behavior such as establishing multiple classes of service. Relating KPIs to evolutionary change. KPIs are Fitness Criteria Metrics with defined threashold values
20220607 Introduction to Flight LevelsCraeg Strong
The Flight Levels framework represents a breakthrough achievement in the Agile community, finally living up to the promise of true Business Agility. It does this by encompassing every part of the organization and encouraging participation at every level, across all disciplines. The flight level model recognizes that we need three “viewpoints” for managing our work—flight level three, or the strategy level, flight level two, or the coordination level, and flight level one, or the team level. Flight Levels provide a simple and clear way to connect strategy to execution—facilitating alignment and enabling innovation to occur at every level. Unlike complex and prescriptive frameworks, Flight Levels fit in smoothly with your existing processes like Scrum or Kanban and can be adopted quickly and incrementally.
In this talk I will introduce the flight levels framework, focusing on the problems that it solves and how it differs from other well-known frameworks. Unlike other frameworks, flight levels can be used by the entire company—it is non-IT specific. In addition, flight levels can happily coexist with other Agile frameworks. Rather than specify what teams should be doing, the flight levels framework focuses on helping teams coordinate in value streams and connecting strategy to execution at the portfolio and corporate strategy level. Unlike traditional org charts, the flight level system maps the flow of work and helps us understand the needs for coordination--where we need daily touchpoints and feedback loops. A flight level system consists of a flight level three, or strategy level board mapping corporate strategy to our portfolio of work via OKRAs—(objectives key results and Actions) as well as one or more flight level two boards to help us coordinate the work of multiple teams within a given value stream. These boards all connect to our standard flight level one team-level Scrum or Kanban boards. This talk introduces an exciting new approach to enterprise agility that is neither vague nor overly prescriptive. Participants will come away with a new perspective on scaling Agile that they can apply immediately, no matter which Agile framework(s) their organization is using.
Kanban's 3 Agendas (London Lean Kanban Day)David Anderson
When introducing the Kanban Method coaches and consultants have 3 specific agendas that resonate with people at different levels within a business: survivability; service-orientation; and sustainability. This presentations explains what they are, why they matter and who they affect.
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.
Actionable Agile Metrics for Predictability - Daniel VacantiAgile Montréal
Actionable Agile Metrics for Predictability
“When will it be done?” That's the first question customers ask once work is started. Your predictability is judged by the accuracy of your answer. Think about how many times you’ve been asked that question and how many times you’ve been wrong. That you’ve been wrong more times than right is not necessarily your fault. You have been taught to collect and analyze the wrong metrics. Until now.
About Daniel Vacanti
Daniel Vacanti is a 20+ year software industry veteran who has spent most of his career focusing on Lean and Agile practices. In 2007, he helped to develop the Kanban Method for knowledge work and managed the world’s first project implementation of Kanban that year. He has been conducting Lean-Agile training, coaching, and consulting ever since. In 2011 he founded ActionableAgile (previously Corporate Kanban) which provides industry-leading predictive analytics tools and services organizations that utilize Lean-Agile practices. In 2015 he published his book, “Actionable Agile Metrics for Predictability”, which is the definitive guide to flow-based metrics and analytics. Daniel holds an M.B.A. and regularly teaches a class on lean principles for software management at the University of California Berkeley.
A central component of Kanban is to make invisible knowledge work visible. However, you will notice quite often that you very often cannot work, but are blocked. Waiting for the test environment, requirements unclear, or missing customer information are only a small part of blockages that prevent us from continuing to work. These blockages are in most cases not a singular event, but have a systemic cause. In other words, it is very unlikely that a blockage occurs only once in the history of a company. Normally the same blockage occurs again and again.
What can one do about it? Jumping out of the window in despair would be a possible approach. Another idea would be to see the blockages for what they are: Treasures of improvements. In this session, we show you how to harvest these treasures and to improve sustainably your working system. In addition, we will present a model that shows with the help of a few simple number games, which blockages need to be removed to achieve the greatest possible leverage.
Cross-department Kanban Systems - 3 dimensions of scaling #llkd15Andy Carmichael
Describes Clearvision's journey of adopting Kanban, not just in the software development team but in Marketing and other departments. Uses 3 dimensions of scaling - Width (before and after); Height (different sizes, timescales, decision-making); Depth (interdependent services at the same level)
Scrum.org Professional Scrum with Kanban (PSK I) Certification | Question & A...Meghna Arora
Start Here---> https://bit.ly/2Rsw0Bx <---Get complete detail on PSK I exam guide to crack Professional Scrum with Kanban. You can collect all information on PSK I tutorial, practice test, books, study material, exam questions, and syllabus. Firm your knowledge on Professional Scrum with Kanban and get ready to crack PSK I certification. Explore all information on PSK I exam with the number of questions, passing percentage, and time duration to complete the test.
Prioritization – 10 different techniques for optimizing what to start next ...Troy Magennis
10 different prioritization techniques to help understand what to START next. Shows the evolution between choosing at random up to full economic analysis. First presented at Agile 2017 in Florida.
Kanban is a 2nd generation approach to Agile which enables practitioners to evolve their own unique processes. This was my key note address to the Scrum Gathering China, Hangzhou 2016
Enterprise Services Planning: Defining Key Performance IndicatorsDavid Anderson
Defining KPIs for use in Enterprise Services Planning and with Kanban systems. Understanding the difference between KPIs, Improvement Guides, and General Health Indicators. Understanding how KPIs drive behavior such as establishing multiple classes of service. Relating KPIs to evolutionary change. KPIs are Fitness Criteria Metrics with defined threashold values
20220607 Introduction to Flight LevelsCraeg Strong
The Flight Levels framework represents a breakthrough achievement in the Agile community, finally living up to the promise of true Business Agility. It does this by encompassing every part of the organization and encouraging participation at every level, across all disciplines. The flight level model recognizes that we need three “viewpoints” for managing our work—flight level three, or the strategy level, flight level two, or the coordination level, and flight level one, or the team level. Flight Levels provide a simple and clear way to connect strategy to execution—facilitating alignment and enabling innovation to occur at every level. Unlike complex and prescriptive frameworks, Flight Levels fit in smoothly with your existing processes like Scrum or Kanban and can be adopted quickly and incrementally.
In this talk I will introduce the flight levels framework, focusing on the problems that it solves and how it differs from other well-known frameworks. Unlike other frameworks, flight levels can be used by the entire company—it is non-IT specific. In addition, flight levels can happily coexist with other Agile frameworks. Rather than specify what teams should be doing, the flight levels framework focuses on helping teams coordinate in value streams and connecting strategy to execution at the portfolio and corporate strategy level. Unlike traditional org charts, the flight level system maps the flow of work and helps us understand the needs for coordination--where we need daily touchpoints and feedback loops. A flight level system consists of a flight level three, or strategy level board mapping corporate strategy to our portfolio of work via OKRAs—(objectives key results and Actions) as well as one or more flight level two boards to help us coordinate the work of multiple teams within a given value stream. These boards all connect to our standard flight level one team-level Scrum or Kanban boards. This talk introduces an exciting new approach to enterprise agility that is neither vague nor overly prescriptive. Participants will come away with a new perspective on scaling Agile that they can apply immediately, no matter which Agile framework(s) their organization is using.
Kanban's 3 Agendas (London Lean Kanban Day)David Anderson
When introducing the Kanban Method coaches and consultants have 3 specific agendas that resonate with people at different levels within a business: survivability; service-orientation; and sustainability. This presentations explains what they are, why they matter and who they affect.
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.
Actionable Agile Metrics for Predictability - Daniel VacantiAgile Montréal
Actionable Agile Metrics for Predictability
“When will it be done?” That's the first question customers ask once work is started. Your predictability is judged by the accuracy of your answer. Think about how many times you’ve been asked that question and how many times you’ve been wrong. That you’ve been wrong more times than right is not necessarily your fault. You have been taught to collect and analyze the wrong metrics. Until now.
About Daniel Vacanti
Daniel Vacanti is a 20+ year software industry veteran who has spent most of his career focusing on Lean and Agile practices. In 2007, he helped to develop the Kanban Method for knowledge work and managed the world’s first project implementation of Kanban that year. He has been conducting Lean-Agile training, coaching, and consulting ever since. In 2011 he founded ActionableAgile (previously Corporate Kanban) which provides industry-leading predictive analytics tools and services organizations that utilize Lean-Agile practices. In 2015 he published his book, “Actionable Agile Metrics for Predictability”, which is the definitive guide to flow-based metrics and analytics. Daniel holds an M.B.A. and regularly teaches a class on lean principles for software management at the University of California Berkeley.
A central component of Kanban is to make invisible knowledge work visible. However, you will notice quite often that you very often cannot work, but are blocked. Waiting for the test environment, requirements unclear, or missing customer information are only a small part of blockages that prevent us from continuing to work. These blockages are in most cases not a singular event, but have a systemic cause. In other words, it is very unlikely that a blockage occurs only once in the history of a company. Normally the same blockage occurs again and again.
What can one do about it? Jumping out of the window in despair would be a possible approach. Another idea would be to see the blockages for what they are: Treasures of improvements. In this session, we show you how to harvest these treasures and to improve sustainably your working system. In addition, we will present a model that shows with the help of a few simple number games, which blockages need to be removed to achieve the greatest possible leverage.
Cross-department Kanban Systems - 3 dimensions of scaling #llkd15Andy Carmichael
Describes Clearvision's journey of adopting Kanban, not just in the software development team but in Marketing and other departments. Uses 3 dimensions of scaling - Width (before and after); Height (different sizes, timescales, decision-making); Depth (interdependent services at the same level)
Scrum.org Professional Scrum with Kanban (PSK I) Certification | Question & A...Meghna Arora
Start Here---> https://bit.ly/2Rsw0Bx <---Get complete detail on PSK I exam guide to crack Professional Scrum with Kanban. You can collect all information on PSK I tutorial, practice test, books, study material, exam questions, and syllabus. Firm your knowledge on Professional Scrum with Kanban and get ready to crack PSK I certification. Explore all information on PSK I exam with the number of questions, passing percentage, and time duration to complete the test.
Prioritization – 10 different techniques for optimizing what to start next ...Troy Magennis
10 different prioritization techniques to help understand what to START next. Shows the evolution between choosing at random up to full economic analysis. First presented at Agile 2017 in Florida.
Kanban is a 2nd generation approach to Agile which enables practitioners to evolve their own unique processes. This was my key note address to the Scrum Gathering China, Hangzhou 2016
Key note - Lean Kanban Central Europe 2013 - Kanban & Evolutionary ManagementDavid Anderson
Exploring how Kanban can be used to improve the fitness for purpose of an organization. Comparing the development of Kanban with the journey of Bruce Lee as he rebelled against traditional Chinese martial arts teaching and developed his own "way without way."
KANBAN AND EVOLUTIONARY MANAGEMENT – LESSONS WE CAN LEARN FROM BRUCE LEE’S JO...Lean Kanban Central Europe
We have to stop adopting defined processes (or methodologies as they known in the IT business). Instead we need to look to adopt a new style of management that encourages an adaptive capability to emerge in our organizations. This talk will look at Bruce Lee‘s rejection of patterned styles of Chinese Martial Arts and emergence of his Jeet Kune Do approach and compare it to the emergence of the Kanban Method. The talk will illustrate how to use fitness criteria metrics aligned to customer desires to manage an organization that is continually evolving its workflows to improve service delivery and customer satisfaction.
Closing key note from Lean Kanban India. Understanding the appropriate application of kanban systems, appropriate use of Enterprise Services Planning, and appropriate application of the Kanban Method for Evolutionary Change. Mapping to Cynefin complexity framework
Just say #no____ the altenative path to enterprise agilityDavid Anderson
The Kanban Method & Enterprise Services Planning have, for a decade, offered an alternative to Agile methodologies for improving business agility across professional services organizations employing thousands of knowledge workers. This key note highlights why Kanban is the least disruptive approach to agility but the most radical alternative to Agile
TOCPA 2013 - Towards a Framework for Managing Knowledge WorkDavid Anderson
This presentation looks at aspects of Theory of Constraints that have worked for me in creative knowledge work activities such as software development. It also looks at others that haven't and features 6 suggestions for how this experience affects the body of knowledge of the Theory of Constraints
La gestion visuelle Kanban - Daniel DoironAgile Montréal
A) Est-ce que votre gestion du risque est rassembleuse, ouverte sur la discussion, qualitative, visuelle, peu couteuse, rapide et supportant plusieurs taxonomies ?
Arrêtez les approches quantitatives en matière de gestion des risques qui sont souvent trop subjectives et non agiles.
B) Vos indicateurs de gestion ont-ils une valeur prédictive sur vos performances à venir? Sont-ils simples, pertinents, visuels et se génèrent automatiquement?
Si une approche basée sur la pensée scientifique des Edwards Deming, Eli Goldratt, Peter Drucker vous intéresse, alors vous serez plus efficace à identifier les systèmes globalement saturés, les systèmes localement saturés et les sources de variabilité de vos processus. Et vous aurez des solutions en main!
Votre avantage: Une fois ces concepts connus, vous n'aurez besoin d'aucun budget ou permission pour rayonner tout autrement en matière d'agilité au sein de vos équipes.
Daniel Doiron est conférencier international en matière de Kanban pour la SCRUM ALLIANCE et le LEAN KANBAN UNIVERSITY. En 2015 et 2016, il aura visité Miami et Shanghai pour ces deux organisations. Daniel a récemment contribué à la nouvelle bible Kanban écrite par David Anderson et Andy Carmichael, et sa contribution a été reconnue dans l'ouvrage. Le livre 'Essential Kanban Condensed' est disponible gratuitement sur le web et pave la voix au chemin alternatif vers l'agilité au 21ième siècle. En parallèle, Daniel s'affère à améliorer certains concepts de coaching propres à Kanban et à revisiter les paradigmes en matière de fluidité des idées. Daniel est dispensateur de formation LEAN KANBAN et Management 3.0 et opère à partir des Etats-Unis.
Tribal behavior in the workplace is core to the human condition. This talk explains how an understanding of sociology and social psychology has been used to develop the community for the Kanban Method, embedded into the Kanban Method to leverage human behavior in the workplace and how you can design kanban systems to encourage positive social behavior in the workplace
An understanding of sociology and social psychology has been present in the design of the Kanban Method - an evolutionary approach to improving service delivery in professional services, knowledge work and creative industries. This talk shows how to use Kanban for social engineering, the aspects of social psychology and sociology built into the design of the method, and how this knowledge was used to develop and grow the movement and community globally over the last 8 years. Lean Kanban Benelux 2015
Key Note - Smidig 2013 - Scaling Kanban in the Enterprise - Kanban's 3 AgendasDavid Anderson
The Kanban Method comes with 3 explicit agendas: Sustainability; Service-orientation; and survivability. This presentation looks at how to achieve large scale Kanban implementations in your enterprise and how Kanban will enable sustainable pace, improved service delivery and survivability through evolutionary capability and an improved focused on fitness for purpose
Key Note - SEPG 2013 - Kanban and the End of MethodologyDavid Anderson
This presentation looks at Alistair Cockburn's claim that software development methodologies are losing mind share to adaptive frameworks of which he considers the Kanban Method to be one. It also introduces an analysis of Bruce Lee's journey developing his own style of Chinese martial arts training and compares it with the journey David J. Anderson has taken developing the Kanban Method
Kanban implementations have become ubiquitous around the world. Many are very large scale with over 5000 people using the technique. However, enterprise are struggling to implement end-to-end pull systems. Why? This talk looks at how to achieve true Lean workflows with deferred commitment and just-in-time replenishment in professional services enterprises
Presented at Silicon Valley Agile Leadership Network 2014 by Janice Linden-Reed See also https://www.slideshare.net/AgileCampSV/silicon-valley-agile-leadership-network
Similar to Kanban - the alternative path to agility (20)
Creating Resilient, Robust, & Antifragile OrganizationsDavid Anderson
What makes organizations fragile? What makes them resilient and able to bounce back from failure? How can they be robust to avoid major failures? However, what really differentiates business that are "built to last" is that they can mutate & evolve in response to change technology, market, economic and political conditions. What actions can leaders take to create resilient, robust & antifragile businesses and how can the Kanban Method help with that?
Creating Robust, Resilient & Antifragile Organizations (using Kanban)David Anderson
Explains in plain language Nassim Nicholas Taleb's taxonomy of fragile, resilient, robust & antifragile organizations and explains how the Kanban Method can be used to create resiliency, robustness and evolutionary capability. Ultimately antifragility requires an ability to change identity
This Limited WIP Society Munich talk look at emerging patterns of kanban boards and kanban systems at differing levels of organizational maturity. It presents a new simplified model for understanding maturity and how it relates to fragile, resilient, robust & antifragile organizations, and presents suggestions on how to catalyze evolutionary change using different mechanisms as maturity improves. For Kanban Coaches and Change Leaders.
Opening 45 minute key note from Lean Kanban India summarizing 10 years of Kanban history and main innovations and advances during that time, plus a brief overview of Enterprise Services Planning as the future direction for the movement
Janice Linden-Reed's presentation at Lean Kanban Central Europe describing the feedback mechanisms in the Kanban Method used with Enterprise Services Planning to evolve to a business to be "fit for purpose" constantly sensing & responding to political, economic & market changes
Enterprise Services Planning - Effective Middle ManagementDavid Anderson
This may be the first time, I really explained Enterprise Services Planning (ESP) effectively. Many people in the audience seemed to understand for the first time.
Enterprise Services Planning - Scaling the Benefits of KanbanDavid Anderson
ESP - the right thing, at the right time, the right way, with appropriate risk exposure!
Your business is an ecosystem of interdependent services which can be improved. Learn to see services. Kanban each service with STATIK. Imrpove using the Kanban Cadences.
An understanding of sociology and social psychology was the differentiator for Agile software development methods. This talk looks at how Kanban can be used for social engineering to improve innovation and trust, and how an understanding of sociology was used to design the Kanban Method and shape the community that advocates it.
Enterprise Services Planning - Scaling the Benefits of KanbanDavid Anderson
ESP - the right thing, at the right time, the right way, with appropriate risk exposure!
Your business is an ecosystem of interdependent services which can be improved. Learn to see services. Kanban each service with STATIK. Imrpove using the Kanban Cadences.
Enterprise Services Planning - Scaling the Benefits of KanbanDavid Anderson
My latest key note providing an overview of the Enterprise Services Planning (ESP) vision, together with the first public release of the 2nd edition of the Kanban Method (Kanban 2.0). The power in ESP is in its simplicity! Lean Kanban - power in simplicity! Lean Kanban - the alternative path to agility!
Enterprise Services Planning - Scaling the Benefits of KanbanDavid Anderson
Key note from Lean Kanban Southern Europe in Madrid, April 2015. Defines Enterprise Services Planning as a service-oriented approach to improving professional services and evolving to a level of business performance that is "fit for purpose". Your business is an ecosystem of interdependent services which can be improved through the use of Kanban: Learn to see services; Kanban each service; Implement feedback loops to enable evolutionary change and continually improving service delivery.
The history of Kanban applied in IT, knowledge work & creative services, telling the time line of innovations and adoption. Conclusions on what we've learned and a vision for the future direction enabling Enterprise Services Planning
"Fitness for Purpose" - Resilience & Agility in Modern BusinessDavid Anderson
High technology businesses tend to focus on and reward innovation but to be “fit for purpose” in the eyes of customers, product and service innovation must be coupled with acceptable service delivery. Business resilience relies on a constant ability to sense shifts in customer demands and expectations, and to respond with new products, service and levels of service delivery. Evolutionary biology provides us with a model for adapting to changing conditions and evaluating fitness. This talk will look at how the Kanban Method enables evolutionary adaptability and how to define fitness criteria metrics to drive effective business performance.
"Fitness for Purpose" - Resilience & Agility in Modern BusinessDavid Anderson
Understanding "fitness for purpose". A new way to look at market segmentation based on identity. Defining fitness criteria metrics. Sense and respond. Using Kanban Systems to increase service delivery agility. Using the Kanban Method to catalyze and evolve your business to be "fitter for purpose". Making sense of a complex market using clustering of narratives from front-line staff. Remaining resilient through frequent "fitness" reviews
Fitness for purpose, aligning capability to customer expectations. How evolutionary processes reveal that the fitness for purpose of a business has both a product/service component and a service delivery component. Kanban systems have been shown to help improve service delivery. This presentation shows how to derive and use the correct metrics to guide process improvements and steer service delivery methods to be fitter for purpose
Making Better Decisions - Understanding Fitness for Purpose, Aligning Capabil...David Anderson
This is an update to my Modern Management Methods 2014 talk in San Francisco. It includes an example kanban system based on lead time distribution and demand analysis.
Making Better Decisions - understanding "fitness for purpose", matching strat...David Anderson
Modern Management Methods 2014 Key Note - Fitness for purpose has a product component and a service delivery component. Understanding service delivery capability helps you make better decisions about how and what to improve. Lean Kanban North America, San Francisco 2014
The Team Member and Guest Experience - Lead and Take Care of your restaurant team. They are the people closest to and delivering Hospitality to your paying Guests!
Make the call, and we can assist you.
408-784-7371
Foodservice Consulting + Design
The case study discusses the potential of drone delivery and the challenges that need to be addressed before it becomes widespread.
Key takeaways:
Drone delivery is in its early stages: Amazon's trial in the UK demonstrates the potential for faster deliveries, but it's still limited by regulations and technology.
Regulations are a major hurdle: Safety concerns around drone collisions with airplanes and people have led to restrictions on flight height and location.
Other challenges exist: Who will use drone delivery the most? Is it cost-effective compared to traditional delivery trucks?
Discussion questions:
Managerial challenges: Integrating drones requires planning for new infrastructure, training staff, and navigating regulations. There are also marketing and recruitment considerations specific to this technology.
External forces vary by country: Regulations, consumer acceptance, and infrastructure all differ between countries.
Demographics matter: Younger generations might be more receptive to drone delivery, while older populations might have concerns.
Stakeholders for Amazon: Customers, regulators, aviation authorities, and competitors are all stakeholders. Regulators likely hold the greatest influence as they determine the feasibility of drone delivery.
Senior Project and Engineering Leader Jim Smith.pdfJim Smith
I am a Project and Engineering Leader with extensive experience as a Business Operations Leader, Technical Project Manager, Engineering Manager and Operations Experience for Domestic and International companies such as Electrolux, Carrier, and Deutz. I have developed new products using Stage Gate development/MS Project/JIRA, for the pro-duction of Medical Equipment, Large Commercial Refrigeration Systems, Appliances, HVAC, and Diesel engines.
My experience includes:
Managed customized engineered refrigeration system projects with high voltage power panels from quote to ship, coordinating actions between electrical engineering, mechanical design and application engineering, purchasing, production, test, quality assurance and field installation. Managed projects $25k to $1M per project; 4-8 per month. (Hussmann refrigeration)
Successfully developed the $15-20M yearly corporate capital strategy for manufacturing, with the Executive Team and key stakeholders. Created project scope and specifications, business case, ROI, managed project plans with key personnel for nine consumer product manufacturing and distribution sites; to support the company’s strategic sales plan.
Over 15 years of experience managing and developing cost improvement projects with key Stakeholders, site Manufacturing Engineers, Mechanical Engineers, Maintenance, and facility support personnel to optimize pro-duction operations, safety, EHS, and new product development. (BioLab, Deutz, Caire)
Experience working as a Technical Manager developing new products with chemical engineers and packaging engineers to enhance and reduce the cost of retail products. I have led the activities of multiple engineering groups with diverse backgrounds.
Great experience managing the product development of products which utilize complex electrical controls, high voltage power panels, product testing, and commissioning.
Created project scope, business case, ROI for multiple capital projects to support electrotechnical assembly and CPG goods. Identified project cost, risk, success criteria, and performed equipment qualifications. (Carrier, Electrolux, Biolab, Price, Hussmann)
Created detailed projects plans using MS Project, Gant charts in excel, and updated new product development in Jira for stakeholders and project team members including critical path.
Great knowledge of ISO9001, NFPA, OSHA regulations.
User level knowledge of MRP/SAP, MS Project, Powerpoint, Visio, Mastercontrol, JIRA, Power BI and Tableau.
I appreciate your consideration, and look forward to discussing this role with you, and how I can lead your company’s growth and profitability. I can be contacted via LinkedIn via phone or E Mail.
Jim Smith
678-993-7195
jimsmith30024@gmail.com
Artificial intelligence (AI) offers new opportunities to radically reinvent the way we do business. This study explores how CEOs and top decision makers around the world are responding to the transformative potential of AI.
Oprah Winfrey: A Leader in Media, Philanthropy, and Empowerment | CIO Women M...CIOWomenMagazine
This person is none other than Oprah Winfrey, a highly influential figure whose impact extends beyond television. This article will delve into the remarkable life and lasting legacy of Oprah. Her story serves as a reminder of the importance of perseverance, compassion, and firm determination.
1. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Kanban
the alternative path to agility
How do Bruce Lee, a Red
Squirrel & a London Taxi
relate to business survivability?
David J. Anderson
Chairman, Lean Kanban Inc
Capability Counts
Alexandria VA, May 2017
5. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Agility = Capability x Optionality
Skills
Experience
Capacity
# Options x Frequency of decision making
7. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Bruce Lee rejected traditional teaching
and styles of Chinese martial arts
There are some parallels in the story of
Bruce Lee and the emergence of his
approach to Kung Fu
Lee rejected the idea of following a
particular style of Chinese Martial Arts
8. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Snake
Monkey
Mantis
Tiger
Kung Fu Panda simplified the art to only five styles
Crane
10. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
“Dry land swimming” provides a false sense of
capability
The only way to learn is to train with a live opponent
Lee rejected the many styles of martial arts for various reasons,
mainly that they gave the practitioners a false sense of
capability, putting them at risk in real combat situations
He was against Kata (learning patterns without an opponent)
and described them in derogatory terms such as "dry land
swimming.“
11. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Lee believed he had to train martial artists to adopt an
adaptive style of fighting – to inherently know how to
modify their tactics in response to the competitive threat
13. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Lee wanted to start from first principles and core concepts
Four ranges of combat
• Kicking
• Punching
• Trapping
• Grappling
*Apparently still called the Five Ways, there are actually now six **with the later inclusion of SAA
**The fact that The Five Ways has six elements is evidence of evolution in action
***Incorporated core ideas such as "center line" and single fluid motion from Wing Chun and parrying from Epee Fencing****
****Not a Chinese Martial Art and hence evidence of "no limitation as limitation"
Five* Ways of Attack***
• Single Direct Attack (SDA)
• Attack By Combination (ABC)
• Progressive Indirect Attack
(PIA)
• (Hand) Immobilization Attack
(HIA)
• Attack by Drawing (ABD)
• Single Angle Attack (SAA)
14. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
The Kanban Method
General Practices
1. Visualize (with a kanban board 看板)
2. Limit work-in-progress (with kanban かんばん)
3. Manage flow
4. Make policies explicit
5. Implement feedback loops
6. Improve collaboratively, evolve experimentally
(using models & the scientific method)
15. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Lee’s approach still needed a name
He named his approach
Jeet Kune Do - the way of the
intercepting fist - after one of
the practices taught in his
method
He was quick to point out that it
was just a name, a way of
communicating a set of ideas.
He was passionate that
practitioners shouldn't get hung
up on the name or the inclusion
of any one move or action.
16. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Kanban is just a name!
The Kanban Method is named
for use of kanban systems
- a single practice within a wider
philosophy of evolutionary process
development
17. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Jeet Kune Do
Using no
way as way
Having no
limitation as
limitation
18. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Kanban – follow your own path to agility!
Kanban is the Agile method
without a “methodology”!
There is no defined Kanban
Process!
19. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Jeet Kune Do encourages development of a
uniquely personal style
a framework from
which to pick &
develop a personal
style
an evolutionary
approach where
adoption of
maneuvers is learned
& reinforced by
training with an
opponent
Nothing was sacred
"absorb that which is
useful“
discard the remainder
20. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Training with an opponent provides the core
feedback loop to drive adaptation
Lee pursued ever
more elaborate
approaches to
protected real
combat training to
enable the closed
loop learning that
was core to the
evolutionary
nature of JKD
21. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Kata are not adaptive
In comparison with JKD, patterned styles of martial arts
taught with "kata" were open loop and not adaptive.
There is no adaptation of style from practicing kata.
Instead you must follow the style precisely.
22. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
The Kanban Method
Change Management Principles
1. Start with what you do now
Understanding current processes, as actually practiced
Respecting existing roles, responsibilities & job titles
2. Gain agreement to pursue improvement through
evolutionary change
3. Encourage acts of leadership at all levels
25. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
A Kanban Systems consists of
“kanban” (かんばん) signal cards in
circulation
26. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
What are kanban systems good for?
Deferred commitment – “just-in-time”, “last responsible moment”
Limiting work-in-progress – focus on quality workmanship
Reducing delay
Less inventory, less work queuing
Improved “flow efficiency”
Shorter & more predictable lead times
Implication: If you suffer from over-committing, committing too early,
poor quality or long & unpredictable delivery times, kanban systems will
help
27. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Kanban systems are a point solution
Like the “incepting fist” maneuver, you use kanban systems for specific
reasons
However, it turns out that limiting WIP creates stress that catalyzes the
evolutionary process
Limiting WIP provokes conversation about why work isn’t flowing in an optimal
fashion
29. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
You are part of a professional services business!
An ecosystem of
professionals
providing
interdependent
services, often with
complex
dependencies.
Professional
Service
organizations
build intangible
goods
30. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Seeing Services
Learn to view what you do now as a set of services
(that can be improved):
Service-orientation Paradigm…
• Creative & knowledge work is service-oriented
• Services have a requestor who both requests a product
or service and accepts or acknowledges delivery of the
finished item or condition
• Service delivery may involve workflow
• Workflow involves a series of knowledge discovery
activities
• The way in which a request is treated defines its class of
service
31. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Treat each service separately
Demand
Observed
Capability
Demand
Demand
Observed
Capability
Observed
Capability
32. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Kanban Cadences
Strategy
Review
Risk
Review
Monthly
Service
Delivery
Review
Bi-WeeklyQuarterly
Kanban
Meeting
Daily
Operations
Review
Monthly
Replenishment/
Commitment
Meeting
Weekly
Delivery
Planning
Meeting
Per delivery cadence
change change
change
change
change
change
change change
change
info
info
info
info
info
info
info
info
info
change info
Focus on Service Delivery
Driving improvement…
Higher level
management function
34. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
F
F
O
M
N
K
J
I
Pull
For each service implement a Kanban “pull” system
Ideas
D
Dev
Ready
G
5
Ongoing
Development Testing
Done
3 3
Test
Ready
5
F
B
CPull
Pull
*
There is capacity here
UAT
Release
Ready
∞ ∞
Pulling work from development will
create capacity here too –
the pull signals move upstream!
Now we have capacity
to replenish our ready
buffer
Kanban has been called
“Iterationless” Agile. Batches of
work are replaced with
continuous flow of work
35. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Commitment is deferred
E
D
Commitment point
F
F
FF
F
F F
G
Pull
Wish to avoid aborting after commitment
Ideas
Dev
Ready
5
Ongoing
Development Testing
Done
3 3
Test
Ready
5
UAT
Release
Ready
∞ ∞
We are committing to getting
started. We are certain we want
to take delivery.
Ideas remain optional and
(ideally) unprioritized
Kanban implements the Lean
principle of “just in time”
through the practice of deferred
commitment
36. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Test
Ready
F
F
FF
F
F F
Decoupled Cadence Improved Optionality
EG
D
Replenishment
Discarded
I
Pull
Ideas
Dev
Ready
5
Ongoing
Development Testing
Done
3 35
UAT
Release
Ready
∞ ∞
The frequency of system replenishment
should reflect arrival rate of new
information and the transaction &
coordination costs of holding a meeting
Lead time
The frequency of delivery should
reflect the transaction & coordination
costs of deployment plus costs &
tolerance of customer to take delivery
Delivery
For software development skill in
configuration management is an
enabling capability for Kanban
37. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Agility = Capability x Optionality
Skills
Experience
Capacity
# Options x Frequency of decision making
38. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Delivery Capability has 3 Dimensions
Service Delivery
Agility
Commitment
frequency
Lead Time
Delivery
Frequency
LeadTime
Short
Long
Delivery
Service Delivery Agility
Commitment
Frequent
Seldom
Frequent
Seldom
More
Agile
Less
Agile
Kanban system dynamics
44. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
In evolutionary processes, alternative solutions often compete to
demonstrate which is “fitter” for the environment
47. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Achieve “Fitness for Purpose”
+
These must be balanced to deliver what your
customers need and expect: to be “fit for purpose”
Product component
(capability/brand/non-
functional elements)
Service delivery component
demand /customer expectations/
customer satisfaction)
48. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
What makes a pizza delivery service “fit for purpose” ?
Fitness criteria are metrics that
measure things customers
value when selecting a service
again & again
Delivery time
Quality
Predictability
Safety (or conformance to
regulatory requirements)
50. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Punctuated Equilibrium
Punctuation Points
• Financial crisis, regulatory changes,
political changes, merger, acquisition,
divestiture, split, IPO, outsourcing, CEO
change, key man exit, reorganization,
arrival of a disruptive
innovation/insurgents in your market
• Easy to insert change
• First 100 days
• Honeymoon period, blame predecessor
Periods of Equilibrium
• Need emotional motivation for change
• Immersive experiential learning
• Stressor
• New species competes for fitness in
existing environment
• Grey squirrel, red squirrel
• Galapagos Island Effect
• Protect mutations
• Isolation strategy
• Innovator’s Solution
52. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Evolution can be hard to explain…
Four ranges of combat
• Kicking
• Punching
• Trapping
• Grappling
*Apparently still called the Five Ways, there are actually now six **with the later inclusion of SAA
**The fact that The Five Ways has six elements is evidence of evolution in action
***Incorporated core ideas such as "center line" and single fluid motion from Wing Chun and parrying from Epee Fencing****
****Not a Chinese Martial Art and hence evidence of "no limitation as limitation"
Five* Ways of Attack***
• Single Direct Attack (SDA)
• Attack By Combination (ABC)
• Progressive Indirect Attack
(PIA)
• (Hand) Immobilization Attack
(HIA)
• Attack by Drawing (ABD)
• Single Angle Attack (SAA)
Five
Six
54. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Posit Science Feature Request
Requested by:______________________________________ Date Requested_____________
Feature name__________________________________________________________________
Format: [customer] [action] [purpose]
Description____________________________________________________________
________________________________________________________________________
________________________________________________________________________
Cost of Delay Classification (required)
Check the type of Feature per the cost of delay.
Expedite – critical and immediate cost of delay
Fixed date – cost of delay goes up significantly after deadline….date:_________
Standard- cost of delay goes up increasingly over time
Intangible – cost of delay incurred significantly later
Provide information on one or more of the following (optional)
Projected Revenue______________________________________
Opportunity Cost
• Estimated 6 month revenue loss if not implemented_____________________________
• Estimated 6 month operating expenses if not implemented_______________________
• Estimated cost of man hours or other resources if not implemented_________________
Qualitative Value (customer experience, quality of service, etc)____________________
Suggested stories (optional)
Old
“red squirrel”
New
“grey squirrel”
This portion of the form
quickly fell out of use. It is
an example of an
evolutionary relic
56. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Built to Last - 1994
3M – the Minnesota
Mutation Machine
An Example of a
Resilient, Robust &
Antifragile
organization
57. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Survivability = Agility x Adaptability
Capability x Optionality
Capability
(to manage change)
Frequency of change opportunitiesx
Skills
Experience
Org maturity
59. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Capability
OptionalityAdaptability
Delivered as
management training
& coaching
Focus on managers at
all levels
Business unit scale
Horizontal
Applicable to all
professional services
(not just IT)
60. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Capability
OptionalityAdaptability
Typical Agile
Method
Delivered as
methodologies,
process improvement
& coaching
Focus on individuals
and teams
Vertical
Tends to be IT, or
software engineering
specific
67. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Personal Kanban
Aggregated
Personal Kanban
Team Kanban
Emergent/Undefined
Workflow
Per Person WIP Limit
CONWIP
Physical space
kanban
Physical token
kanban
Virtual Kanban
Classes of service
Capacity allocation
Liquidity optimization
Aggregated teams
68. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Personal Kanban
Aggregated
Personal Kanban
Team Kanban
Emergent/Undefined
Workflow
Per Person WIP Limit
CONWIP
Physical space
kanban
Physical token
kanban
Virtual Kanban
Classes of service
Capacity allocation
Liquidity optimization
Aggregated teams
Benefits of improving maturity
79. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Conclusions
Agility lies at the intersection of capability & optionality
Survivability lies at the interaction of agility & adaptability
The Kanban Method has all the elements needed to help professional
services businesses improve their agility & adaptability across all
knowledge worker activities
80. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Conclusions
Pursuing a non-prescriptive, evolutionary approach has enabled a rich
ecosystem of design solutions to emerge
An understanding of the CMMI model enabled us to put these
implementations in context and correlate patterns to maturity levels
Understanding the mapping of “depth of kanban” to benefits further
enriched the model
The Kanban Maturity Model is set to become a key coaching tool
enabling consultants & change agents to catalyze improvement by
stressing organizations just enough but not so much as to break them
81. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Guided evolution with the Kanban Method
- The future of business agility
83. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
About
David Anderson is an innovator in
management of 21st Century
businesses that employ creative
people who “think for a living” . He
leads a training, consulting,
publishing and event planning
business dedicated to developing,
promoting and implementing new
management thinking & methods…
He has 30+ years experience in the high technology industry
starting with computer games in the early 1980’s. He has
led software organizations delivering superior productivity
and quality using innovative methods at large companies such
as Sprint and Motorola.
David defined Enterprise Services Planning and originated
Kanban Method an adaptive approach to improved service
delivery. His latest book, published in June 2012, is, Lessons
in Agile Management – On the Road to Kanban.
David is Chairman of Lean Kanban Inc., a business operating
globally, dedicated to providing quality training & events to
bring Kanban and Enterprise Services Planning to businesses
who employ those who must “think for a living.”
84. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
Teodora Bozheva has been and continues to e an invaluable contributor to the
Kanban Maturity Model
Hakan Forss played a key role in provoking the development of the Kanban
Cadences and the Depth of Kanban Assessment Framework
Irina Dzhambazova captured many of the case studies that enabled the
observation of kanban implementations correlating to organizational maturity
levels
The global community of accredited trainers and coaches (AKTs & KCPs) in the
Lean Kanban community contribute to the development of this on-going work
Acknowledgements
89. Email dja@leankanban.com Twitter @lki_dja Copyright Lean Kanban Inc.
2012 Lessons in Agile Management
The heavily under-rated book
that underpins the Kanban
Coaching Masterclass and most
of the theory behind the
Kanban Method
There are some parallels in the story of Bruce Lee and the emergence of his approach to Kung Fu.
Lee rejected the idea of following a particular style of Chinese Martial Arts.
Lee rejected these for various reasons, mainly that they gave the practitioners a false sense of ability and put them at risk in real combat situations. He was against Kata (learning patterns without an opponent) and described them in derogatory terms such as "dry land swimming."
Instead he sought to break the art down into a set of basic principles:
The four ranges of combat
Kicking
Punching
Trapping
grappling
and the Five* Ways of Attack***
Single Direct Attack (SDA)
Attack By Combination (ABC)
Progressive Indirect Attack (PIA)
(Hand) Immobilization Attack (HIA)
Attack by Drawing (ABD)
Single Angle Attack (SAA)
*Apparently still called the Five Ways, there are actually now six **with the later inclusion of SAA
**The fact that The Five Ways has six elements is evidence of evolution in action
***Incorporated core ideas such as "center line" and single fluid motion from Wing Chun and parrying from Epee Fencing****
****Not a Chinese Martial Art and hence evidence of "no limitation as limitation"
There are 6 General Practices in the Kanban Method. [Walk briefly through each of the 6 Practices. See David Anderson’s blog at http://www.djaa.com/principles-general-practices-kanban-method if you want help with how to explain]
He named his approach Jeet Kune Do - the way of the intercepting fist - after one of the principles taught in his method. He was quick to point out that it was just a name, a way of communicating a set of ideas. He was passionate that practitioners shouldn't get hung up on the name or the inclusion of any one move or action.
The Jeet Kune Do emblem incorporates the words...
"having no way as way." There would be no specific style or school to his approach. It is not fixed or patterned but guided by a set of principles. An individual would adapt their own style that worked best for them by learning the principles and practicing different types of kicking, punching, trapping and grappling.
"having no limitation as limitation." In other words, Lee would be prepared to pull ideas from any source if it made the (martial) art better and made the individual a better practitioner. His concern was the logical improvement of the method rather than loyalty to any one tradition or tribe. He was happy to borrow ideas from Western traditions as much as Eastern.
While Jeet Kune Do is often described as a framework from which an individual can pick and choose to develop their own style, it is also an evolutionary approach. Lee referred to "absorb what is useful" and discard the remainder. And this was at the personal level for an individual developing their own style. If they chose to discard "intercepting fist" this would be acceptable. They were following the philosophy faithfully and the inclusion of any one maneuver or set of maneuvers was not critical.
In Jeet Kune Do training is always with an opponent. This provides the core feedback loop and learning opportunity that allows a practitioner to select that which "is useful" and discard that which is not.
Lee pursued ever more elaborate approaches to protected real combat training to enable the closed loop learning that was core to the evolutionary nature of JKD. In comparison patterned styles of martial arts taught with "kata" were open loop and not adaptive.
There are 3 Change Management Principles designed to frame an evolutionary approach to improvement. Be aware that the Kanban Method is applied to the way you work now, and it will help you evolve the way you work gradually over time.
[Briefly walk through each of the principles. See David’s blog at http://www.djaa.com/principles-general-practices-kanban-method if you want help with how to explain each.]
Think in terms of services rather than departments or functional groups: look at the way you work, who your customers are, the activities involved, and how the work flows.
Your organization is a system of interdependent services. Each service can be treated separately and “kanbanized” using the STATIK method.
We scale out kanban one service at a time, in a service-oriented fashion.
It is simpler to build independent kanban systems, even with interdependency between them, than it is to design a large scale, complicated system for multiple services.
Explicit feedback mechanisms drive evolutionary adaptive capability. Kanban Cadences create evolutionary DNA. Installing them is key to delivering on the new strategy
Changes decided at Kanban Meetings, Service Delivery Reviews, Ops Reviews, and Risk Reviews lead to different WIP limits, different capacity allocations, and different classes of service. The effect of this is to provide smoother, more predictable flow end-to-end for external customer demand. An optimal design for the entire network emerges organically through evolutionary change.
As soon as work is completed at one step, it can be immediately pulled to the next step. This creates capacity to take on new work.
The first commitment point is when we pull a work item.
Fitness criteria are metrics that measure things customer or other external stakeholders value such as delivery time, quality, predictability, conformance to regulatory requirements or metrics that value actual outcomes such as customer satisfaction or employee satisfaction
Instead he sought to break the art down into a set of basic principles:
The four ranges of combat
Kicking
Punching
Trapping
grappling
and the Five* Ways of Attack***
Single Direct Attack (SDA)
Attack By Combination (ABC)
Progressive Indirect Attack (PIA)
(Hand) Immobilization Attack (HIA)
Attack by Drawing (ABD)
Single Angle Attack (SAA)
*Apparently still called the Five Ways, there are actually now six **with the later inclusion of SAA
**The fact that The Five Ways has six elements is evidence of evolution in action
***Incorporated core ideas such as "center line" and single fluid motion from Wing Chun and parrying from Epee Fencing****
****Not a Chinese Martial Art and hence evidence of "no limitation as limitation"
Lean Kanban Inc offers management training, consulting, community events, publications and software tools to help businesses with strong technical capabilities and commanding market positions, to improve their adaptability and optionality to insure agility and survivability. Lean Kanban delivers the management capability to manage for uncertainty, change, and attack from disruptive innovation.
Lean Kanban Inc offers management training, consulting, community events, publications and software tools to help businesses with strong technical capabilities and commanding market positions, to improve their adaptability and optionality to insure agility and survivability. Lean Kanban delivers the management capability to manage for uncertainty, change, and attack from disruptive innovation.
Kanban creates an environment in which individuals can have a collaborative conversation and do something about problems with their work. [Use the cartoon as a buffer prior to the morning break. Ask the class how many acts of leadership they see in the picture. Ask what “Let’s Do Something about it” – what do you think the “It” is? There are probably 2 “it’s shown in the picture: 1) Development may be a bottleneck because Test is starving whilst work accumulates in Analysis; 2) Many items in Analysis may be blocked and our analysts are starting new work rather than making an attempt to close out existing work.)