Agile Retrospectives: Making Good Teams Great
et plus d'un million d'autres livres sont disponibles pour le Kindle d'Amazon. En savoir plus
| |||||||||||||||
Produits fréquemment achetés ensemble
Descriptions du produit
Shows you the tools, tricks and tips you need to fix the problems you face on a software development project on an on-going basis. This work also shows how to architect retrospectives in general, how to design them specifically for your team and organization, how to run them effectively, and how to make the needed changes.
Détails sur le produit
Souhaitez-vous compléter ou améliorer les informations sur ce produit ? Ou faire modifier les images?
|
En savoir plus sur les auteurs
Découvrez des livres, informez-vous sur les écrivains, lisez des blogs d'auteurs et bien plus encore.
Dans ce livre
(En savoir plus)
Quels sont les autres articles que les clients achètent après avoir regardé cet article?
Commentaires en ligne
Commentaires client les plus utiles
Par Pierre Fauvel
Format:Broché|Achat authentifié par Amazon
Quiconque s'intéresse aux méthodes agiles sérieusement en vient à considérer les rétrospectives.
Ce livre est simple, court (comme tous les livres de la collection).
Peut-être un peu répétitif en énumérant les techniques.
Un bon choix pour un scrum master débutant.
Pour un facilitateur avancé, lui préférer "Collaboration Explained" de Jean Tabaka.
Ce livre est simple, court (comme tous les livres de la collection).
Peut-être un peu répétitif en énumérant les techniques.
Un bon choix pour un scrum master débutant.
Pour un facilitateur avancé, lui préférer "Collaboration Explained" de Jean Tabaka.
Commentaires client les plus utiles sur Amazon.com (beta)
Amazon.com:
4.4 étoiles sur 5
34 commentaires
45 internautes sur 56 ont trouvé ce commentaire utile
3.0 étoiles sur 5
Reality Check
5 mars 2007
Par R. Williams
- Publié sur Amazon.com
Format:Broché|Achat authentifié par Amazon
After the first 100 pages, I was ready to give this book a single star. Then it made its way back by producing some stimulus in the center of the book, basically talking about some techniques for eliciting and then analyzing feedback (made it back to a 4, 5 is ludicrous just from the content perspective, this thing is thin in every sense of the word). But then, it fell back to a 3 because ultimately the many examples are laid out as if they were patterns, but there is little to no structure. Finally, the conclusion section goes back to some of the silliness of the beginning. What I am referring to as silliness is the constant enveloping of process suggestions with new agey psychobabble. I found that 80% of the time, this additional stuff was noise.
Ultimately, I was left convinced (as probably all who have done iterative could easily be) that retrospectives are a good thing, but a strong conviction that they could be done better than what is being espoused here. There are a few good ideas, and the overall presentation is good. That's all.
Ultimately, I was left convinced (as probably all who have done iterative could easily be) that retrospectives are a good thing, but a strong conviction that they could be done better than what is being espoused here. There are a few good ideas, and the overall presentation is good. That's all.
12 internautes sur 13 ont trouvé ce commentaire utile
5.0 étoiles sur 5
Take your team to a new level with this book!
1 août 2006
Par Lisa Crispin
- Publié sur Amazon.com
Format:Broché
My agile team has used retrospectives for years and thought we were pretty good at them. The activities and ideas in this well-written, well-organized book take our retrospectives to a whole new level. Now if we can't remember what we did in the previous two weeks (it's surprising how poor our memories can be!), or are stumped for ideas on how to address a prickly issue, we can just turn to the book for a way to jump-start a beneficial change.
I had no idea there were so many different approaches to getting value via retrospectives. The activities are all simple, and illustrated with many figures and examples. Even if you're not very experienced at leading these types of meetings, the book will give you confidence.
The authors also explain when and why to do different types of retrospectives. For example, I hadn't thought of having project retrospectives for our agile team, since we already have iteration retrospectives, but now I can see how they can be managed for good effect. Most importantly, the book explains how to use the information and ideas produced in a retrospective to effect real change. It's easy to get complacent and not strive to do better, and this book will help your team be proactive.
The book's organization makes it a good reference guide too. Anytime your team is in a rut or having a problem, you could pick an activity out of this book to kick start things. I love user-friendly books such as this one.
I had no idea there were so many different approaches to getting value via retrospectives. The activities are all simple, and illustrated with many figures and examples. Even if you're not very experienced at leading these types of meetings, the book will give you confidence.
The authors also explain when and why to do different types of retrospectives. For example, I hadn't thought of having project retrospectives for our agile team, since we already have iteration retrospectives, but now I can see how they can be managed for good effect. Most importantly, the book explains how to use the information and ideas produced in a retrospective to effect real change. It's easy to get complacent and not strive to do better, and this book will help your team be proactive.
The book's organization makes it a good reference guide too. Anytime your team is in a rut or having a problem, you could pick an activity out of this book to kick start things. I love user-friendly books such as this one.
10 internautes sur 12 ont trouvé ce commentaire utile
5.0 étoiles sur 5
It's not hype; their advice works.
18 septembre 2006
Par Norman L. Kerth
- Publié sur Amazon.com
Format:Broché
Diana and Esther tell us how to make good teams great. It's not hype; their advice works!
From the first few pages we know the authors are speaking from their vast experience, sharing knowledge on how to install iterative retrospectives in a team's process. Their book is written in an easy-to-read manner and leaves nothing out: it includes examples from real retrospectives, a theory of iterative retrospective design as well as a number of carefully designed exercises.
I'm not surprised that the authors could make clear such a difficult topic, blending insight from a number of fields and writing specifically for software teams. For more than a decade, Esther and Diana have been teaching the techniques and helping leading edge companies from all over the world implement retrospectives.
This is a must read book for anyone serious about making the Agile approach work, and then work better and better. Why? Because an Agile approach deployed right out of the book or course is likely to be a poor fit for your specific environment. Agile needs to be fine-tuned for your teams strengths, skills, challenges and goals. The iterative retrospective is the widely proven technique to make these crucial adjustments. There is no better book on the topic.
From the first few pages we know the authors are speaking from their vast experience, sharing knowledge on how to install iterative retrospectives in a team's process. Their book is written in an easy-to-read manner and leaves nothing out: it includes examples from real retrospectives, a theory of iterative retrospective design as well as a number of carefully designed exercises.
I'm not surprised that the authors could make clear such a difficult topic, blending insight from a number of fields and writing specifically for software teams. For more than a decade, Esther and Diana have been teaching the techniques and helping leading edge companies from all over the world implement retrospectives.
This is a must read book for anyone serious about making the Agile approach work, and then work better and better. Why? Because an Agile approach deployed right out of the book or course is likely to be a poor fit for your specific environment. Agile needs to be fine-tuned for your teams strengths, skills, challenges and goals. The iterative retrospective is the widely proven technique to make these crucial adjustments. There is no better book on the topic.
›
Allez sur Amazon.com pour voir l'ensemble des 34 commentaires
4.4 étoiles sur 5
Ces commentaires ont-ils été utiles ?
Dites-le-nous
Listmania!
|
|
Rechercher des articles similaires par rubrique
- Livres anglais et étrangers > Business & Investing > Management & Leadership > Management
- Livres anglais et étrangers > Business & Investing > Skills
- Livres anglais et étrangers > Computers & Internet > Computer Science > Software Engineering
- Livres anglais et étrangers > Computers & Internet > Programming > Software Design, Testing & Engineering > Software Development
Commentaires
Souhaitez-vous compléter ou améliorer les informations sur ce produit ? Ou faire modifier les images?
|
