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. |
Avis des internautes - Rédiger un commentaire
Aucun commentaire n'a été trouvé aux emplacements habituels.
Table des matières
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 |
Expressions et termes fréquents
activities Agile development Agile software development allocation analysis asked average lead backlog behavior blocked bottleneck buffer build capability capacity card wall change requests chapter class items class of service CMMI collaborative continuous improvement coordination costs Corbis defects delivered delivery cadence demand against throughput downstream Dragos electronic tracking estimation example feature Feature Driven Development Figure flow function implemented input queue issues item types iterations kaizen culture Kanban Method kanban system limit WIP limit work-in-progress maintenance maturity Microsoft on-demand optimize organization OTA download percent predictability prioritization meeting production text changes Prog project manager pull system Recipe for Success release requirements risk scheduled server slack software engineering sources of variability stakeholders standup meetings swim lanes takeaways team members testers Theory of Constraints tickets tion Toyota Production System transaction costs trust typically user stories value stream visual week WIP limits workflow