Hundreds of organizations around the world have already benefited from Disciplined Agile Delivery (DAD). Disciplined Agile® (DA™) is the only comprehensive tool kit available for guidance on building high-performance agile teams and optimizing your way of working (WoW). As a hybrid of the leading agile, lean, and traditional approaches, DA provides hundreds of strategies to help you make better decisions within your agile teams, balancing self-organization with the realities and constraints of your unique enterprise context. This book: • Provides a foundation for enterprise agility, value streams, and a disciplined approach to DevOps; • Is a pragmatic application of agile, lean, and traditional techniques for your enterprise-class environment; • Overviews a strategy for teams to evolve a fit-for-purpose, flexible WoW that still supports a consistent governance strategy for leadership; and • Makes a perfect study guide for Disciplined Agile certification. Why “fail fast” (as the agile industry likes to recommend) when you can learn quickly on your journey to high performance? With this book, you can make better decisions based upon proven, context-based strategies, leading to earlier success and better outcomes.
Rendkívül hasznos kézikönyv, mind a 430+ oldala fontos és jól használható információt hordoz! Az elmúlt egy évben elsősorban referenciaként használtam agilis coach-i, tanácsadói, oktatói munkámban, de most befektettem az időt, végigolvastam és kijegyzeteltem.
Overall I believe is a good book compiling all the complex process related to software development. Some processes (like QA-related) feel a bit more detailed than others, and some described practices are truly not recommendable (I believe the authors tried to include all options, but not sure how valuable some of them are). As a product person, I believe it falls short on the role of product and how we prioritize work, but many agile related books have the same issue.
As an agilist this book filled so many gaps in how to implement agile in a pragmatic way. I highly recommend both reading the book and taking the Disciplined Agile course. These have been an epiphany to me.
Elige tu procedimiento de trabajo (Way of Working), parte de un principio general: cada proyecto es único y, además, evoluciona en el tiempo.
Hace años, casi todos los proyectos seguían una metodología secuencial para su desarrollo, que se adaptaba atendiendo, sobre todo, a su tamaño.
Ahora hay una variedad de proyectos que responden a distintas situaciones, tanto por la tecnología que utilizan como por los objetivos que persiguen.
También se han abierto camino nuevas metodologías de gestión ágiles que, en vez de seguir caminos secuenciales, iteran en ciclos de desarrollo que incorporan el cambio para adaptarse a las necesidades cambiantes de los clientes.
Este libro es un manual de uso sobre la gestión de proyectos que, reconociendo la utilidad y pervivencia del enfoque en cascada, lo deja a un lado para centrarse en lo que ha llamado Disciplined Agile Delivery (DAD), o Entrega Ágil Disciplinada.
Me lo he leído de principio a fin, y eso mismo recomiendo a quien tenga interés en la gestión de proyectos con enfoques ágiles, para después conservarlo como manual de consulta al que recurrir cuando se presenten dudas sobre un tema específico, como por ejemplo qué tipo de pruebas convienen al tipo de proyecto que se afronta.
Para facilitar una guía rápida de consulta (que, por supuesto, también está explicada en perfecto inglés en el prefacio del libro), describo aquí la estructura del texto:
El ciclo de vida del proyecto se divide en tres etapas:
• Iniciación • Construcción • Transición
Puedes elegir entre seis tipos diferentes de ciclos de vida (los escribo en inglés, como aparecen en el texto):
Bien. Podrás elegir el ciclo de vida más adecuado para tu proyecto teniendo en cuenta su contexto. Para ello dispones de un árbol de decisión (pág. 111) que resulta de gran ayuda.
¿Y luego, qué?
Pues luego, por cada fase (Iniciación; Construcción —producir valor de negocio—; Transición —despliegue en producción—) encontrarás los objetivos de proceso (Process Goals).
Por cada uno, se detallan las principales prácticas y estrategias, entre las cuales podrás elegir la que mejor se acomode a tu situación.
Aquí te dejo el índice de procesos, a modo de chuleta, por si quieres ir directamente a lo que te interesa. Aún así, te aconsejo encarecidamente leer el prefacio y el primer capítulo.
Iniciación
7. Formar el equipo (110) 8. Alineamiento con la Dirección Corporativa (127) 9. Explorar el alcance (135) 10. Identificar la estrategia de la Arquitectura (149) 11. Planificar la Release (165) 12. Desarrollar la estrategia de pruebas (179) 13. Desarrollar una visión común (207) 14. Asegurar presupuesto (215)
Construcción
15. Probar la Arquitectura en fase temprana (223) 16. Abordar las necesidades cambiantes de los usuarios (227) (en el original usa “Address”) 17. Producir una solución potencialmente utilizable (241) 18. Mejorar la calidad (257) 19. Acelerar la entrega de valor (265)
Transición
20. Asegurar la preparación de Producción (291) 21. Desplegar la solución (295) 22. Crecimiento del Equipo de trabajo (305) 23. Coordinar actividades (315) 24. Evolucionar el procedimiento de trabajo (WoW) (335) 25. Abordar riesgos (365) (en el original usa “Address”) 26. Aprovechar y mejorar la Arquitectura existente (378) 27. Gobernar al equipo de la entrega
La última sección la dedica a convencernos de las bondades de la certificación en alguna de las posibilidades que ofrece el PMI.
Certificarte requiere un esfuerzo de aprendizaje, y lo digo por experiencia, pero sin duda merece la pena. Soy partidario de estas certificaciones porque realmente aportan valor al profesional y, gracias al prestigio del PMI, transmiten a los demás la confianza de que ese conocimiento está demostrado y avalado.
Quería contribuir al colectivo hispanohablante con esta guía para un uso eficiente del libro/manual Choose your WoW de Scott W. Ambler.
Agilistas y Jefes de proyecto, ¡Os deseo la mejor elección!
Choose your Wow is about how agile software development teams can choose their way of working (WoW).
What does this mean? DA starts with some assumptions: 1. That teams should choose their way working 2. The being agile is constructed on knowing how to do agile 3. Software creation is complicated and needs scaffolding to support teams in choosing their WoW 4. Since other people faced similar challenges to yours you can use that learning
The scaffolding DA proposes starts with process goals that guide teamsprocess-relatedocess related decisions that they need to make to tailor agile strategies to address the context of the situations they face. Each process goal (there are 24 of them like "form team", "prove architecture early", "deploy the solution", "measure outcomes", ...) contains decision points (items you must decide upon, ranging from 2 to 20+). Each decision point has lists (or choice) that you could make in order to address a decision point.
I highly encourage all Agile practitioners in software development to check this book out.
On the downside, it speaks a lot about process, and it feels that it speaks less about people and their interactions. It also feels heavy, and although less prescriptive that SAFe for example, the sheer amount of choices, the details, and the norms can feel overwhelming. It is no surprise to me that the Project Management Institute chose to host it. They so keep on heaviness.
I found this book intriguing as it introduces a new way of looking at agile projects, beyond the usual approach of scrum. It is certainly not for everyone!
The book is reasonably well organized, though not perfect.
This book, just like the disciplined agile idea it discusses, are not prescriptive in any respect. See pmi.org for more in-depth info on specific disciplined agile techniques. Some may find that the lack of “do this” to be a significant barrier; this “weakness” is also the greatest “strength”, in that your team gets to choose the parts and pieces that will work for them. Note that there are no specific work methods that are truly covered in detail in the book, and these are all located on pmi.org for free, and in some cases, what may be covered in a small paragraph on pmi.org would then lead you to lots of other blog, posts, or even books necessary to fully understand that respective topic.
This book does a great job of giving a high-level overview of what distributed agile is, and is not.
If these ideas may be applicable to your organization, this could absolutely be a transformative idea on how a team or organization works together to deliver value to customers quicker.
Choose your Way of Working --> this book helps you through the process of choosing your way of working, without instructing you how to actually do the work. What do I mean? The Choose your WoW approach might guide you and your team towards Scrum or Lean (etc), without actually helping you with how to implement Scrum. The idea is that there are plenty other resources to help with that.
I valued that Choose your WoW explicitly addressed scaling Agile in large organizations, and was forthright and pragmatic about while theoretical Agile is great, Business management, PMOs, and similar forces are present and must be addressed (and not ignored).
I wish the book was a bit more detailed on the mechanics of lifecycles, a little more clear about Process Blades, and I wish the DABrowser had links to more artifacts (possibly something that should grow with time).
DAD Choose Your WOW" is a standout book for anyone delving into Agile methodology. Its exceptional attention to detail makes it a valuable resource, offering comprehensive insights into the world of Agile frameworks and tools. As a novice Agile practitioner, I found the author's guidance on implementing Agile to be especially invaluable. It provides clear and actionable guidelines that can lead to successful Agile adoption. With its meticulous guidance and clarity, it's an indispensable companion for mastering Agile methodology and making it work for you.
Great book about scaling agile. If you have taken scrum or safe courses you need to check this out because PMI purchased the company that made this book. The book is a bit long but most of the material is reference that you can skim so it wont take you long to finish. My full review is here: https://ericbrownbookreviews.com/choo...
Referenced this book for some workflow processes on an organisational level. I love how detailed the book is in explaining how to put them into practice. Although it is a it of an overload of information to remember all the concepts and processes on your first read. It is a good book to reference as the information is categorised into chapters and sections for easy reference.
This book did not wow me at all. But I did copy their DA principles, promises, and guidelines into my notebook – they’re a very sensible of the existing agile principles, and I might refer back to them one day.