Kanban: Successful Evolutionary Change for Your Technology BusinessKanban is becoming a popular way to visualize and limit work-in-progress in software development and information technology work. Teams around the world are adding kanban around their existing processes to catalyze cultural change and deliver better business agility. This book answers the questions: What is Kanban? Why would I want to use Kanban? How do I go about implementing Kanban? How do I recognize improvement opportunities and what should I do about them? Published 10 years ago it is in the top 5 agile books ever published. |
Contents
1 | |
6 | |
11 | |
12 | |
Chapter 3 | 21 |
From Worst to Best in Five Quarters ___________________________ | 35 |
Chapter 5 | 49 |
Mapping the Value Stream ________________________________ | 63 |
Chapter 11 | 123 |
Metrics and Management reporting _________________________ | 139 |
Chapter 14 | 159 |
Part FOur Making Improvements | 187 |
Chapter 17 | 195 |
Chapter 18 | 211 |
Chapter 19 | 219 |
External Sources of Variability | 225 |
Chapter 9 | 74 |
Chapter 7 | 79 |
establishing an Input Cadence _____________________________ | 103 |
Chapter 10 | 113 |
Chapter 20 | 235 |
_______________________________ endnotes __________________________________________ | 241 |
Common terms and phrases
activities additional Agile allows analysis approach asked backlog become behavior better blocked bottleneck buffer build cadence capacity card wall chapter choice class of service collaborative complete continuous coordination costs Corbis costs create culture defects delivered delivery demand discussion effect electronic enable engineering estimation example Figure five fixed flow function implemented important improvement increase initial input queue introduced involved issues kanban system lead maintenance maturity meeting method Microsoft months organization percent performance planning possible predictability prioritization problems project manager pull queue reduce regular release requests requirements result risk scheduled shows simple software development specific steps team members things throughput tickets tion tracking trust typically variability variation visual waste week WIP limits work-in-progress