Introduction to Kanban

831 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
831
On SlideShare
0
From Embeds
0
Number of Embeds
9
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Introduction to Kanban

  1. 1. Kanban Intro
  2. 2. Introductions● Hosts: microsoft.lv & agile-latvia.org● Speaker: Aleksejs Truhans – Programmer, systems administrator, analyst, project manager, team leader, software engineering teacher – Now at Citadele bank, tsi.lv, nh.lv, javaguru.lv, agile- latvia.org and LDN.lv – Approaching BDD – Aleksejs.Truhans@gmail.com● Should you have a question – raise your hand!
  3. 3. Origins● Toyota Production System & Lean● Value● Value stream map● Waste● Flow – highlight problems● Further reading – “The Goal: A Process of Ongoing Improvement” by Eliyahu M. Goldratt & Jeff Cox – “Leading Lean Software Development: Results Are not the Point” by Mary & Tom Poppendiecks
  4. 4. Kanban● A “visual card”● Software engineering: “Kanban” by David Anderson● Pull the work. Limit the capacity. – WIP – Work In Progress● Visualization of the flow stimulates improvement and provokes change – … even of ”waterfall” teams ;)● Kanban board cartoon: – http://blog.crisp.se/henrikkniberg/2009/06/26/1246 053060000.html
  5. 5. Pros and Cons● Evolution rather than revolution● Agnostic to software engineering and management practices● When 1 week iteration is too long● Cadence taking form of average lead time● There are “idle” people● Identifies micro-level problems● Protecting people
  6. 6. Pros and Cons● Just giving names and structure to common sense ideas● May give no advantage, e.g., compared to timeboxing● Main effect may come from just-in-time planning and estimating● More suitable for unpredictable loads● Not a complete sofware lifecycle tool
  7. 7. Reality Dev 1 Dev n QA 1 QA n OperationsProjectsMaintenance &SupportOn hold ● Daily delivery “trains” ● Same team doing development and maintenance ● Experienced and reliable people ● Hold - if a much higher priority task comes in ● No visualisation on a common board ● Improving just-in-timeness of prioritisation

×