Where does Kanban come from?
• Is originally from the automotive industry - Toyota Production System (TPS) • All we know about Kanban is an inspiration from the manufacturing • It is also well known in the software development since 2003 (inspired by the book from David J. Anderson)
In what kind of management
culture do you use Kaizen? • Kaizen is Japanese for "improvement“ or "change for the better" refers to philosophy or practices that focus upon continuous improvement • Lean Management is a bundle of principles • bring expertise and responsibility together • work self-organized • eliminate “waste” • harmonize processes and • attempt for continuous improvement (Kaizen)
What is allowed in Kanban?
• Kanban leaves almost everything open you can do whatever is needed • Kanban supports the team to find the best solution by • continuously monitoring the work to improve the process
What kind of stream identifies
all steps to develop a prodcuct? • Value Stream identifies all steps in order to develop the wanted product • Makes visible how much time is spent on value adding vs non value adding (waste) work • The goal is to minimize the non value adding work or to prevent waste
7 wastes of software development?
Mary and Tom Poppendieck translated the seven wastes of Lean into „The 7 wastes of software development“: • Delays, e.g. waiting for something • Extra Features, e.g. rising cost of complexity • Relearning, e.g. writing a report vs. talking to each other • Handoffs, e.g. analyst to designer to developer to tester • Task Switching, e.g. developer working on different topics • Partially Done Work, e.g. un-tested, un-documented, un- deployed • Defects, e.g. bug occure after release
What fits perfect for working
with Kanban? • Ideal in Kanban is to have the focus on one ticket • That is pulled as fast as possible from left (open) to right (done) • The activities or single steps should be value adding activities
What are the most often
used metrics in Kanban? Lead time • starts when the request is made, and ends once delivered • is what the customer or/and stakeholder sees Cycle time • Time from starting to work on a ticket until it is done Lead time Ticket Start Work Ticket Created Live Cycle time
What are the most often
used metrics in Kanban? Throughput • is reported as a rate of valued work that was delivered in a given time period • it is used as an indicator of how well the system (team, organisation) is performing and to demonstrate continuous improvement • allows planning of next milestones/steps/capabilities
What does Scrum & Kanban
have in common? • Focus – parallel work is reduced (WIP), timeboxes • Inspect & Adapt – Constant Improvement (Kaikaku, Kaizen) • Self Organization • Faster time to market • Expectation Management – Planning (Backlog, Input Queue, Cycle Time, Throughput) • Satisfied Customer – early / constant involvement of customers
Match the Kanban method to
the following topics... There are several options! Service Teams Teams in conservative cultures Teams in regulated environments Teams with a lot of specialisation
Kanban fits to a lot
of topics • Kanban can be applied by everyone • Kanban enforces that the right work is being done in the right time, rather than who is doing it • Participants apply to the system/workflow in the most efficient manner
1 2 3 4 Prioritize
the following Classes of Services in the correct order! Due Date Standard Refactoring Expedite
Classes of Services in Kanban
• Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined • The classes of service are used to visualize different levels severities • Expedite - e.g. bug on live platform • Due Date - e.g. marketing campaign • Standard - e.g. user story • Refactoring – e.g. cleaning up code base
The QA has a problem
with one ticket. After tester 1 recognized a problem with the ticket which he couldn´t fix by himself, he asked tester 2 for help. They have been trying to solve the issue for hours but without any result. The 3 green cards in the progress column are already finished by the developers. What should they do next? !
Interesting Read Terms • Kaikaku
is about making fundamental and radical changes to a production system, unlike Kaizen which is focused on incremental minor changes. • Shu-Ha-Ri is a Japanese martial art concept, and describes the stages of learning to mastery. Links • Leand Kanban University http://www.leankanbanuniversity.com/resources • Limited WIP Society http://www.limitedwipsociety.org • Kanban 101 http://www.kanban101.com • Lean Alliance Group https://www.xing.com/net/leanalliance • 7 wastes of Software Development http://agile.dzone.com/articles/seven-wastes-software • Value Stream Mapping http://en.wikipedia.org/wiki/Value_stream_mapping
Disclaimer This presentation was produced
in September 2011 by XING AG (the "Company") solely for use as an information source for potential business partners and is strictly confidential. It has been made available to you solely for your own information and may not be copied, distributed or otherwise made available to any other person by any recipient. This presentation is not an offer for sale of securities in the United States. The distribution of this presentation to you does not constitute an offer or invitation to subscribe for, or purchase, any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of, or be relied on in connection with, any offer or commitment whatsoever.The facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future. Neither the Company nor any of its subsidiaries, any directors, officers, employees, advisors nor any other person makes any representation or warranty, express or implied as to, and no reliance should be placed on, the accuracy or completeness of the information contained in this presentation. Neither the Company nor any of its subsidiaries, any directors, officers, employees, advisors or any other person shall have any liability whatsoever for any loss arising, directly or indirectly, from any use of this presentation. The same applies to information contained in other material made available at the presentation.While all reasonable care has been taken to ensure the facts stated herein are accurate and that the opinions contained herein are fair and reasonable, this document is selective in nature and is intended to provide an introduction to, and overview of, the business of the Company. Where any information and statistics are quoted from any external source, such information or statistics should not be interpreted as having been adopted or endorsed by the Company as being accurate.This presentation contains forward-looking statements relating to the business, financial performance and results of the Company and/or the industry in which the Company operates. These statements are generally identified by words such as "believes," "expects," "predicts," "intends," "projects," "plans," "estimates," "aims," "foresees," "anticipates," "targets," and similar expressions. The forward-looking statements, including but not limited to assumptions, opinions and views of the Company or information from third party sources, contained in this presentation are based on current plans, estimates, assumptions and projections and involve uncertainties and risks. Various factors could cause actual future results, performance or events to differ materially from those described in these statements. The Company does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future accuracy of the opinions expressed in this presentation. No obligation is assumed to update any forward-looking statements.