Kanban: Successful Evolutionary Change for Your Technology BusinessBlue Hole Press, 2010 - 261 pages Kanban 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. |
Table des matières
6 | |
11 | |
12 | |
Whos better? | 28 |
From Worst to Best in Five Quarters | 35 |
Mapping the Value Stream | 63 |
Allocating Capacity According to Demand | 69 |
CHAPTER 5 | 70 |
a Continuous Improvement Culture | 120 |
CHAPTER 11 | 123 |
Metrics and Management reporting _________________________ | 139 |
CHAPTER 14 | 159 |
CHAPTER 16 | 187 |
CHAPTER 17 | 195 |
CHAPTER 18 | 211 |
CHAPTER 19 | 219 |
CHAPTER 7 | 79 |
CHAPTER 3 | 82 |
CHAPTER 8 | 91 |
CHAPTER 9 | 103 |
CHAPTER 10 | 113 |
CHAPTER 20 | 235 |
endnotes __________________________________________ | 241 |
249 | |
about the author _____________________________________ | 261 |
Expressions et termes fréquents
activities Agile development Agile software development allocation analysis asked backlog behavior blocked bottleneck buffer build capability capacity card wall change requests chapter class of service CMMI collaborative column continuous improvement coordination costs Corbis defects delivered delivery cadence deployment discussion downstream Dragos electronic tracking estimation example feature Figure flow function implemented input queue issue item types iterations kaizen culture Kanban Method kanban system limit WIP maintenance Microsoft on-demand optimize organization percent performance predictability prioritization cadence prioritization meeting production text changes Prog project manager PTCs pull system Recipe for Success release requirements scheduled Server slack slot social capital software engineering software maintenance sources of variability stakeholders standup meetings swim lanes Team Foundation Server team members testers Theory of Constraints ticket tion tool Toyota Production System transaction costs transparency trust typically user stories value stream visual week WIP limits workflow