This document provides an overview of Kanban concepts and how to visualize workflows using Kanban boards. It demonstrates how to transform a simple task list into a Kanban board with statuses, queues, work-in-progress limits, and swim lanes for priorities. Additional concepts covered include identifying and addressing bottlenecks, handling wait times, limiting team member activities, creating forecasts, linking boards for Scrum, personal Kanban boards, and using a board for a cross-functional team.
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
Scrum, Kanban, and DevOps Sitting in a Tree… - Big Apple Scrum Day 2018Yuval Yeret
Scrum, Kanban, and DevOps Sitting on a Tree... (Learn how to leverage Kanban & Scrum together and how to fit DevOps into the picture)Should we use Scrum? Should we use Kanban? Where does DevOps fit into the picture? The best agile teams already know they don’t need to choose. Scrum teams improve when they start to look at flow inside and outside their sprints. Kanban teams improve when they have a disciplined cadence, and effective Product Ownership and Scrum Mastership. DevOps really is mainly about doing Agile the right way. In this session, we will look at a core definition of Scrum, Kanban & DevOps, do some myth-busting as well as identify the quite significant common ground between Scrum, Kanban and DevOps. We will then look at practical ways like the Kanban-based Sprint Backlog, Flow-based Daily Scrum, Visualizing aging work, Flow-based Sprint Planning - which bring some Kanban flow into your Scrum. We will look at how to bring Scrum roles/events/artifacts into your Kanban. We will look at ways to wrap Scrum with a Kanban Flow system that looks upstream/downstream and at the higher level picture of a DevOps Culture/Process. You’ll leave with a better understanding of how Scrum, Kanban, and DevOps relate to each other and with some ideas for experiments to try when back at work.
Immer mehr Organisationen setzen Flight Levels als ein Denkmodell ein, damit das Unternehmen agil am Markt agieren kann. Dafür braucht es sehr viel mehr, als einfach nur ein paar Teams zu agilisieren. In diesem Vortrag werde ich anhand eines Unternehmens zeigen, wie Flight Levels dafür verwendet werden, teamübergreifende Business Agilität zu erreichen. Ich werde auch darauf eingehen, welche Boards gebaut wurden, um agile Interaktionen zwischen den Teams zu etablieren und wie sich die Arbeit über die Boards bewegt, damit strategisches Alignment in der gesamten Organisation erreicht wird.
Imported from Japan, Kanban is an agile methodology that is gaining a lot of traction. Kanban, or Japanese for signal card, is a process that focuses on transparency and limiting the work in progress. By utilizing Kanban, you can pinpoint the bottlenecks and address them easily. In this session you will learn what Kanban is, how it evolved from its roots in the Toyota Production System (TPS) and lean manufacturing to software development, Kanban’s benefits, and how best to implement a Kanban system. We’ll also discuss when not to use Kanban and how to modify other agile methodologies, such as Scrum, to be used in conjunction with Kanban.
Updated version at https://www.slideshare.net/GiulioRoggero/kanban-board-82363781
Do you have a team that works on both project and maintenance? Do you need to organize your team activities? Do you have a lot of activities in parallel and the time to market it's a problem? With a Kanban board and an Agile approach you can solve your problems!
Take a look of the animation of the slides to discover how it works.
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
Scrum, Kanban, and DevOps Sitting in a Tree… - Big Apple Scrum Day 2018Yuval Yeret
Scrum, Kanban, and DevOps Sitting on a Tree... (Learn how to leverage Kanban & Scrum together and how to fit DevOps into the picture)Should we use Scrum? Should we use Kanban? Where does DevOps fit into the picture? The best agile teams already know they don’t need to choose. Scrum teams improve when they start to look at flow inside and outside their sprints. Kanban teams improve when they have a disciplined cadence, and effective Product Ownership and Scrum Mastership. DevOps really is mainly about doing Agile the right way. In this session, we will look at a core definition of Scrum, Kanban & DevOps, do some myth-busting as well as identify the quite significant common ground between Scrum, Kanban and DevOps. We will then look at practical ways like the Kanban-based Sprint Backlog, Flow-based Daily Scrum, Visualizing aging work, Flow-based Sprint Planning - which bring some Kanban flow into your Scrum. We will look at how to bring Scrum roles/events/artifacts into your Kanban. We will look at ways to wrap Scrum with a Kanban Flow system that looks upstream/downstream and at the higher level picture of a DevOps Culture/Process. You’ll leave with a better understanding of how Scrum, Kanban, and DevOps relate to each other and with some ideas for experiments to try when back at work.
Immer mehr Organisationen setzen Flight Levels als ein Denkmodell ein, damit das Unternehmen agil am Markt agieren kann. Dafür braucht es sehr viel mehr, als einfach nur ein paar Teams zu agilisieren. In diesem Vortrag werde ich anhand eines Unternehmens zeigen, wie Flight Levels dafür verwendet werden, teamübergreifende Business Agilität zu erreichen. Ich werde auch darauf eingehen, welche Boards gebaut wurden, um agile Interaktionen zwischen den Teams zu etablieren und wie sich die Arbeit über die Boards bewegt, damit strategisches Alignment in der gesamten Organisation erreicht wird.
Imported from Japan, Kanban is an agile methodology that is gaining a lot of traction. Kanban, or Japanese for signal card, is a process that focuses on transparency and limiting the work in progress. By utilizing Kanban, you can pinpoint the bottlenecks and address them easily. In this session you will learn what Kanban is, how it evolved from its roots in the Toyota Production System (TPS) and lean manufacturing to software development, Kanban’s benefits, and how best to implement a Kanban system. We’ll also discuss when not to use Kanban and how to modify other agile methodologies, such as Scrum, to be used in conjunction with Kanban.
Updated version at https://www.slideshare.net/GiulioRoggero/kanban-board-82363781
Do you have a team that works on both project and maintenance? Do you need to organize your team activities? Do you have a lot of activities in parallel and the time to market it's a problem? With a Kanban board and an Agile approach you can solve your problems!
Take a look of the animation of the slides to discover how it works.
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.
The Product Backlog Refinement refers to activities that help us keeping the product backlog in optimal form. This overview presents all important aspects of this important analysis activity in SCRUM.
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.
Where can Kanban be embedded in the organizational context? Sounds like an easy question, however, it is not always easy to answer - especially in bigger organizations. In this session I will introduce the Kanban Flight Levels model which provides an overview of the different fields of application of Kanban and helps to understand the implications for the organizational context. Furthermore, the model helps to clarify where to start with your Kanban change initiative: on team level, on the value stream, or on portfolio level - every level has it's own challenges, pros and cons.
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.
Lean Inception: how to align people and build the right productPaulo Caroli
Lean inception is the effective combination of Design Thinking and Lean StartUp to decide the Minimum Viable Product (MVP). It is a collaborative workshop that will help a group of people — typically an agile team, a squad, or a product team -- understand, align and plan the building of the lean product.
É fácil gerar ideias para produtos, e elas são muito mais rápidas que a capacidade de entrega da organização, criando uma frustração constante nos clientes. Mas ideias são apenas ideias, e o processo de validação e aprendizado é muitas vezes separado da entrega, criando uma cascata que aumenta o time to market do produto, ou muitas vezes nem é feito, gerando muito desperdício. O Discovery Kanban é a adoção dos princípios e práticas do Upstream Kanban para criação de um fluxo de validação e aprendizados contínuos em um contexto de inovação ou mudança. Nesse cenário, gargalos na entrega são usados para a melhoria do processo de criação e triagem de opções, melhorando a eficácia do sistema.
Scrumban Demystified. Talk from Agile New England.
A few of the Scrumban Evolutions from Mamamoth bank from the upcoming book on Scrumban.
More excerpts can be found at facebook.com/scrumban
Learn more at scrumban.io
Do you have a case study of applying the Kanban Method in a Scrum context. We want to learn more from your experiments and results. Contact us at info@codegenesys.com
Agile Team Working agreements, also known as team norms, are guidelines developed by the teams as to how they must work together to create a positive, productive process.
This is the updated version of the presentation https://www.slideshare.net/GiulioRoggero/how-a-kanban-board-works.
Do you have a team that works on both project and maintenance? Do you need to organize your team activities? Do you have a lot of activities in parallel and the time to market it's a problem? With a Kanban board and an Agile approach you can solve your problems!
Take a look of the animation of the slides to discover how it works.
--- BONUS ---
Here you can find a more details on lead time and CFD and a new board about Scrum Team Roadmap.
This simple and crisp quick reference card is for Agile and Scrum basics. It is a simple way to glance through all the concepts and use it as a tool for revision, even before an interview.
XBOSoft runs through the Top 10 Agile Metrics revealing the most fundamental data points Agile methodology requires to work effectively, and will put you on the highly targeted path to successful implementation of your Agile processes.
XBOSoft and Go2Group run through the top data points you should be measuring in your Agile Workflow. We’ll show you what to track, when and how often, and most importantly – why. Many believe that metrics are useless, but unless you measure, how can you systematically improve or know how you are doing? And with velocity as an overarching objective in agile, you should be tracking other things so that you know what else you could be impacting by going faster. But, with all the metrics so readily available to us today, how do we filter through to the most meaningful?
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.
The Product Backlog Refinement refers to activities that help us keeping the product backlog in optimal form. This overview presents all important aspects of this important analysis activity in SCRUM.
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.
Where can Kanban be embedded in the organizational context? Sounds like an easy question, however, it is not always easy to answer - especially in bigger organizations. In this session I will introduce the Kanban Flight Levels model which provides an overview of the different fields of application of Kanban and helps to understand the implications for the organizational context. Furthermore, the model helps to clarify where to start with your Kanban change initiative: on team level, on the value stream, or on portfolio level - every level has it's own challenges, pros and cons.
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.
Lean Inception: how to align people and build the right productPaulo Caroli
Lean inception is the effective combination of Design Thinking and Lean StartUp to decide the Minimum Viable Product (MVP). It is a collaborative workshop that will help a group of people — typically an agile team, a squad, or a product team -- understand, align and plan the building of the lean product.
É fácil gerar ideias para produtos, e elas são muito mais rápidas que a capacidade de entrega da organização, criando uma frustração constante nos clientes. Mas ideias são apenas ideias, e o processo de validação e aprendizado é muitas vezes separado da entrega, criando uma cascata que aumenta o time to market do produto, ou muitas vezes nem é feito, gerando muito desperdício. O Discovery Kanban é a adoção dos princípios e práticas do Upstream Kanban para criação de um fluxo de validação e aprendizados contínuos em um contexto de inovação ou mudança. Nesse cenário, gargalos na entrega são usados para a melhoria do processo de criação e triagem de opções, melhorando a eficácia do sistema.
Scrumban Demystified. Talk from Agile New England.
A few of the Scrumban Evolutions from Mamamoth bank from the upcoming book on Scrumban.
More excerpts can be found at facebook.com/scrumban
Learn more at scrumban.io
Do you have a case study of applying the Kanban Method in a Scrum context. We want to learn more from your experiments and results. Contact us at info@codegenesys.com
Agile Team Working agreements, also known as team norms, are guidelines developed by the teams as to how they must work together to create a positive, productive process.
This is the updated version of the presentation https://www.slideshare.net/GiulioRoggero/how-a-kanban-board-works.
Do you have a team that works on both project and maintenance? Do you need to organize your team activities? Do you have a lot of activities in parallel and the time to market it's a problem? With a Kanban board and an Agile approach you can solve your problems!
Take a look of the animation of the slides to discover how it works.
--- BONUS ---
Here you can find a more details on lead time and CFD and a new board about Scrum Team Roadmap.
This simple and crisp quick reference card is for Agile and Scrum basics. It is a simple way to glance through all the concepts and use it as a tool for revision, even before an interview.
XBOSoft runs through the Top 10 Agile Metrics revealing the most fundamental data points Agile methodology requires to work effectively, and will put you on the highly targeted path to successful implementation of your Agile processes.
XBOSoft and Go2Group run through the top data points you should be measuring in your Agile Workflow. We’ll show you what to track, when and how often, and most importantly – why. Many believe that metrics are useless, but unless you measure, how can you systematically improve or know how you are doing? And with velocity as an overarching objective in agile, you should be tracking other things so that you know what else you could be impacting by going faster. But, with all the metrics so readily available to us today, how do we filter through to the most meaningful?
1. Project objectives (hierarchized SMART)
2. To what problem the project is a response ?
3. Priorities (Cost, Quality, Scope, Time)
4. Success criterias
5. Success factors
6. Benefits
7. Fondamental Business Need
8. High Level Requirements prioritized (MoSCoW)
9. Project description
10. Scope (What is in the project ? What is not in the project ?
11. Main steps, Key deliverables, milestone
12. Organization : who is involved and what role does he play?
13. High level Risks : main risks identified
14. Budget
Welcome to TechSoup New Member Orientation and Q&A (May 2024).pdfTechSoup
In this webinar you will learn how your organization can access TechSoup's wide variety of product discount and donation programs. From hardware to software, we'll give you a tour of the tools available to help your nonprofit with productivity, collaboration, financial management, donor tracking, security, and more.
Synthetic Fiber Construction in lab .pptxPavel ( NSTU)
Synthetic fiber production is a fascinating and complex field that blends chemistry, engineering, and environmental science. By understanding these aspects, students can gain a comprehensive view of synthetic fiber production, its impact on society and the environment, and the potential for future innovations. Synthetic fibers play a crucial role in modern society, impacting various aspects of daily life, industry, and the environment. ynthetic fibers are integral to modern life, offering a range of benefits from cost-effectiveness and versatility to innovative applications and performance characteristics. While they pose environmental challenges, ongoing research and development aim to create more sustainable and eco-friendly alternatives. Understanding the importance of synthetic fibers helps in appreciating their role in the economy, industry, and daily life, while also emphasizing the need for sustainable practices and innovation.
How to Make a Field invisible in Odoo 17Celine George
It is possible to hide or invisible some fields in odoo. Commonly using “invisible” attribute in the field definition to invisible the fields. This slide will show how to make a field invisible in odoo 17.
How to Create Map Views in the Odoo 17 ERPCeline George
The map views are useful for providing a geographical representation of data. They allow users to visualize and analyze the data in a more intuitive manner.
The Indian economy is classified into different sectors to simplify the analysis and understanding of economic activities. For Class 10, it's essential to grasp the sectors of the Indian economy, understand their characteristics, and recognize their importance. This guide will provide detailed notes on the Sectors of the Indian Economy Class 10, using specific long-tail keywords to enhance comprehension.
For more information, visit-www.vavaclasses.com
This is a presentation by Dada Robert in a Your Skill Boost masterclass organised by the Excellence Foundation for South Sudan (EFSS) on Saturday, the 25th and Sunday, the 26th of May 2024.
He discussed the concept of quality improvement, emphasizing its applicability to various aspects of life, including personal, project, and program improvements. He defined quality as doing the right thing at the right time in the right way to achieve the best possible results and discussed the concept of the "gap" between what we know and what we do, and how this gap represents the areas we need to improve. He explained the scientific approach to quality improvement, which involves systematic performance analysis, testing and learning, and implementing change ideas. He also highlighted the importance of client focus and a team approach to quality improvement.
We all have good and bad thoughts from time to time and situation to situation. We are bombarded daily with spiraling thoughts(both negative and positive) creating all-consuming feel , making us difficult to manage with associated suffering. Good thoughts are like our Mob Signal (Positive thought) amidst noise(negative thought) in the atmosphere. Negative thoughts like noise outweigh positive thoughts. These thoughts often create unwanted confusion, trouble, stress and frustration in our mind as well as chaos in our physical world. Negative thoughts are also known as “distorted thinking”.
Operation “Blue Star” is the only event in the history of Independent India where the state went into war with its own people. Even after about 40 years it is not clear if it was culmination of states anger over people of the region, a political game of power or start of dictatorial chapter in the democratic setup.
The people of Punjab felt alienated from main stream due to denial of their just demands during a long democratic struggle since independence. As it happen all over the word, it led to militant struggle with great loss of lives of military, police and civilian personnel. Killing of Indira Gandhi and massacre of innocent Sikhs in Delhi and other India cities was also associated with this movement.
The French Revolution, which began in 1789, was a period of radical social and political upheaval in France. It marked the decline of absolute monarchies, the rise of secular and democratic republics, and the eventual rise of Napoleon Bonaparte. This revolutionary period is crucial in understanding the transition from feudalism to modernity in Europe.
For more information, visit-www.vavaclasses.com
2. Kanban Boards step-by-step V0.5– beta
See all credits on next slide! by Giulio Roggero under CC 3.0 license
Normal Flow & WIP Urgencies Swarming People Sprint (a proposal)
Support team Personal Time drivenLinked Kanban Cross-functional teams
Scatter merge Program Lead TimePortfolio Examples
3. Credits
V0.5 – beta
by Giulio Roggero – Creative Common 3.0 License – http://www.agilereloaded.it
Work inspired by great slides and posts written by:
• Joakim Sundén, Marcus Hammarberg and Christophe Achouiantz -
http://www.slideshare.net/marcusoftnet/kanbanboards
• Antonio Lucca - http://tonyxzt.blogspot.it/2011/09/measurment-is-quantitatively-expressed.html
• Claudio Perrone - http://www.slideshare.net/cperrone/a3-kaizen-heres-how
• Benjamin Mitchell - http://blog.benjaminm.net/2012/06/26/how-to-study-the-flow-or-work-with-kanban-cards/
• Gaetano Mazzanti - http://www.slideshare.net/mgaewsj/agile-in-the-bathtub
• David Anderson - http://agilemanagement.net/index.php/kanbanbook/
• Fabio Armani - http://www.slideshare.net/tangram77/scrumban-a-methodology-fusion-bettersoftware-2011
• Yuval Yeret - http://www.slideshare.net/yyeret/explaining-cumulative-flow-diagrams-cfd
Graphics elements by Emanuele Mantovani – http://www.intre.it
Great feedbacks by Fabio Armani, Gaetano Mazzanti, Marco Bresciani, Dario Giannoccaro, Stefano Leli, Fabio Ghislandi
166. Issues Team Backlog
with priorities
Todo this month
20
Free person
Person on other projects
Prj A
Prj B
Prj C
Prj D
Prj E
Blockers
Crtical
Two avatars per person
20
Devel Test Acceptance Released
Ready AcceptedIn prog Done
14 10 30
5
10
168. IDEAS Brainstorming APPROVAL
10 5
Idea generation phase
OK
DISCARDED
SIZE & PRODUCT/SERVICE VISION
KPI to monitor after deploy
SIZING, VISION
& KPI
READY FOR FUNNEL
Innovation
bubbleS
4
Pre-funnel
169. Funnel backlog APPROVAL
10
Business &
TECH
AnaLYSIS
7 5
OK
IN PROG DONE
DISCARDED
URGENCIES BACKLOG (WIP)
SIZ
ED
SIZED
+
VISIO
N
TEAM
READY
starting In prog UAT completed APPROVED &
Closed
IN
Prod
Idea generation implementation
5
deploy
URGENCIES in progress (WIP)
Operations BACKLOG (WIP) Operations in progress (WIP)
Innovation
bubble
incubators
206. Stay tuned for next versions:
• Portfolio kanban boards
• Prisoner metric
• Control Charts
• How-to reduce the WIP step-by-step from current situation to one-piece-flow
This is not the end …
… is just the begin of your journey!
Kanban is not only a board; Lean is not only Kanban.
Be courios, respect people and improve, always!
Per il ranking definitivo valutare anche il costo del ritardo e debito tecnico.
Ogni iniziativa minore di 1 mese sarà riassunta sulla card di portfolio con: nome, costo, stato, se è urgente