Kanban and Scrum - making the most of both (Anglais) Broché – 1 mars 2010
Rentrée scolaire 2017 : découvrez notre boutique de livres, fournitures, cartables, ordinateurs, vêtements ... Voir plus.
|Neuf à partir de||Occasion à partir de|
- Choisissez parmi 17 000 points de collecte en France
- Les membres du programme Amazon Prime bénéficient de livraison gratuites illimitées
- Trouvez votre point de collecte et ajoutez-le à votre carnet d’adresses
- Sélectionnez cette adresse lors de votre commande
Les clients ayant acheté cet article ont également acheté
Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.
Pour obtenir l'appli gratuite, saisissez votre numéro de téléphone mobile.
Détails sur le produit
Si vous vendez ce produit, souhaitez-vous suggérer des mises à jour par l'intermédiaire du support vendeur ?
Meilleurs commentaires des clients
Than someone told me about this book and I read it and found exactly what I wanted. The agile technick you need is the one that helps you resolve your problem. It's not a long book but full of interesting small chapters.
Commentaires client les plus utiles sur Amazon.com
"Kanban and Scrum" is about 100 pages and consists of 2 parts, each written by one of the two authors. The first part is the "Kanban and Scrum" part, written by Henrik, where he shortly clarifies Scrum and Kanban and explains the differences between them. He gives hints to in which situation Kanban and which situation Scrum might be better... and also hints about ways of combining them into Scrumban (a term Henrik doesn't use, but was popularized by one of the first descriptions of Kanban by Corey Ladas Scrumban - Essays on Kanban Systems for Lean Software Development).
The second part of this book is an experience report written by Mattias Skarin about applying Kanban for an operations team in a games company. He briefly explains how they got started and how gradually they evolved Kanban and the kind of decisions they had to make.
This book is very thin and reads fast (of the 100 pages, there are a lot of empty pages). Most of it is available for free from Henrik's page, so if you don't want to buy the book, you can just download it :) The writing is easy to read, it reads more like a blog post than a book.
Amazon stars-wise, I've been thinking about 3 or 4 stars. 3 stars because the book is thin, not very thorough and it does what it is supposed to do well, but not much more. It doesn't give a thorough introduction of Kanban (for that, probably check David Andersons work: Kanban) it doesn't give a thorough introduction of Scrum either. It just briefly explains the difference. Four stars because Henriks writing is very popular (a little too popular for me) but it attracts a wide audience. Also, his writing is very clear, he has a good ability to explain seemingly complex concepts in a simple way. Yet, this book is not a ground-shaking new book. In the end, I decided to favor Henriks explanation skills and go for 4 stars. If you know about Scrum and heard about Kanban and... wonder... then this is the book for you! If you want to have a thorough explanation of Kanban or Scrum, skip this book and go for the ones mentioned in this review.
As the authors put it in the opening.. "it's not the tool you start with, but the way you constantly improve your use of that tool and expand your toolset over time". In other words, Scrum, or any other methodology should not be treated as a dogma. Great teams review, adjust, and experiment with their process to discover what works for them and their environment. Scrum provides a set of guidelines, and Kanban relaxes some of them, giving you more wiggle room (which can be both a blessing and a curse) to explore: how you estimate, how you prioritize, which criteria you optimize (lead time vs troughput vs ...), whether you hold daily standups, and so on.
The book is a quick read and provides a good mix of hands-on examples and practical advice. The reassuring part was that our team has already arrived at many of the same conclusions and patterns on our own, and this just gave us the confidence to go even further and experiment with our workflow to a larger extent.