TY  - BOOK
AU  - Kniberg,Henrik
AU  - Skarin,Mattias
AU  - Poppendieck,Mary
AU  - Anderson,David
TI  - Kanban and Scrum making the most of both
T2  - Enterprise software development series
SN  - 9780557138326
U1  - 005.1112 23
PY  - 2010///
CY  - United States
PB  - C4Media Inc
KW  - Desarrollo ágil de software
KW  - Scrum (Desarrollo de software)
KW  - Innovación en los negocios
KW  - Cambio organizacional
KW  - Productividad de software
N1  - Incluye referencias bibliográficas (103-104); Part I. Comparison : 1. So what is Scrum and Kanban anyway? ; 2. So how do Scrum and Kanban relate to each other? ; 3. Scrum prescribes roles ; 4. Scrum prescribes timeboxed iterations ; 5. Kanban limits WIP per workflow state ; 6. Both are empirical ; 7. Scrum resists change within an iteration ; 8. Scrum board is reset between each iteration ; 9. Scrum prescribes cross-functional teams ; 10. Scrum backlog items must fit in a sprint ; 11. Scrum prescribes estimation and velocity ; 12. Both allow working on multiple products simultaneously ; 13. Both are Lean and Agile ; 14. Minor differences ; 15. Scrum board vs Kanban board - a less trivial example ; 16. Summary of Scrum vs Kanban ; Part II. Case study : 17. he nature of technical operations ; 18. Why on earth change? ; 19. Where do we start? ; 20. Getting going ; 21. Starting up the teams ; 22. Addressing stakeholders ; 23. Constructing the first board ; 24. Setting the first work in progress (WIP) limit ; 25. Honoring the Work in Progress (WIP) limit ; 26. Which tasks get on the board? ; 27. How to estimate? ; 28. So how did we work, really? ; 29. Finding a planning concept that worked ; 30. What to measure? ; 31. How things started to change ; 32. General lessons learned
N2  - Scrum and Kanban are two flavours of Agile software development - two deceptively simple but surprisingly powerful approaches to software development. So how do they relate to each other? The purpose of this book is to clear up the fog, so you can figure out how Kanban and Scrum might be useful in your environment. Part I illustrates the similarities and differences between Kanban and Scrum, comparing for understanding, not for judgement. There is no such thing as a good or bad tool - just good or bad decisions about when and how to use which tool. Part II is a case study illustrating how a Scrum-based development organization implemented Kanban in their operations and support teams. Consistent with the style of "Scrum and XP from the Trenches", this book strikes a conversational tone and is bursting with practical examples and pictures
ER  -