Disciplined Agile Delivery (DAD) constitui a base para escalar as estratégias ágeis e de desenvolvimento de software lean dentro da sua organização. DAD fornece a orientação necessária aos times de desenvolvimento para habilitá-los a terem sucesso nas situações únicas em que se encontram: o contexto importa.
Este livro mostra como um pequeno time de desenvolvimento de uma empresa estabelecida no mercado aplica estratégias ágeis de maneira disciplinada ao longo do tempo para melhorar sua agilidade em gerar valor real aos seus stakeholders. Iniciando com uma abordagem baseada em Scrum o time aprende a partir das suas experiências e evolui para um ciclo de vida lean, e em algum momento para um ciclo de vida de entrega contínua, dentro de um ambiente de DevOps. O livro começa com uma visão geral do DAD e então apresenta um estudo de caso que descreve os aprendizados desse time durante várias releases de uma solução de missão crítica.
DAD é um híbrido de métodos existentes que fornece a flexibilidade de usar várias abordagens bem como preencher algumas lacunas não endereçadas por métodos ágeis convencionais. Em poucas palavras, DAD é “ágil pragmático”. Ele descreve estratégias comprovadas que mostram como programação, desenho, testes, arquitetura, análise, implantação, governança, liderança e muitos outros aspectos da entrega de solução se encaixam fazendo sentido em um todo otimizado. DAD faz o “trabalho pesado” de processo que outros métodos deixam para você fazer, enquanto apresenta opções de processo de uma maneira leve e fácil de compreender. DAD te mostra como colocar o volume da agilidade no máximo.
Terrible as an intro to DAD. Still more than OK as a lesson of pragmatism in modern IT.
Why is it terrible as an intro? Because it doesn't describe the rules & foundation of DAD (even the most basic ones) AT ALL - instead it guides the reader through a single (but quite well-thought) case story: problems & challenges encountered are viable & make sense, but you don't get the answer how DAD is better than other approaches in dealing with them, because you're not able to grasp what's DAD and what's just a common sense.
It may make more time after you read a verbose introduction to DAD (separate book), but as a standalone book it's a poor choice.
It's a dry, abstract read where the author might be making good points but they're presented in such a factual manner, without any examples that you don't absorb anything. Check out the following extracts and decide for yourself, whether you feel like you've read something worthwhile.
* Scrum mostly focuses on leadership and change management aspects during Construction and therefore has roles that reflect this. DND on the other hand explicitly focuses on the entire delivery lifecycle and all aspects of solution delivery, including the technical aspects that Scrum leaves out.
* They would also like to use "feature toggles" to be able to share all code on one mainline branch rather than working in seperate feature branches, controlling what is actually deployed using these toggles.
* Terry conveys to the team that encrico mentioned that the Enterprise Architecture group wants to move away from the current monolithic architecture to a micro-services model over time.
* A cartoon showing 3 characters and their thought bubbles. "I think this will work". "But there is a lot of detail". "The details will evolve over time". What did I just read? What details? What will evolve and for what purpose?
* Carlos reminds everyone that while the Vision gets the stakeholders and team on the same page....the vision will be revisted at the end of each iteration.
I'm not saying that this book doesn't make any points. It does. After a bunch of pages the book makes a point that you can comprehend, if you dwell on it long enough. But without any proper context, the point remains somewhat abstract.
It was a well organized and informative read tying Disciplined Agile Delivery to a practical case and related agile approaches/toolkits. If you are an agilist or agile-curious its worth your time to run through this quick read. If you are agile-curious (no agile background), it might be worth checking out Choose your WoW! before reading this book to give you conceptual context and an understanding of what is practically occurring throughout the book's case.
O livro fornece uma introdução ao framework Disciplined Agile, especificamente do fluxo de entregas DAD dentro de Devops. Isso é feito por meio da história de uma empresa que está implementando DA. De qualquer forma não é uma leitura indispensável. Particularmente sugeriria começar diretamente pelo livro principal, o Choose Your Wow.
This is a great intro to DAD. It’s only the start of the journey though. I now need to read more about the subject and work out how it can assist me in structuring and organising development within my own organisation.
Muy buen libro, algunas imágenes no aparecieron, por lo demás, muy bueno, en especial los ejemplos. La información sobre Dad clarifica el concepto sobre ágil.
A Disciplined Agile Delivery nagyon fontos téma. Egyes elemeit próbálgattam már korábban is, gondoltam, most fejest ugrok bele, és egyből a vékonyabb, bevezető jellegű könyv legfrissebb kiadásával kezdtem.
Tartalmilag nem csalódtam, legszívesebben simán ötöst adtam volna rá, bár - a fiktív esettanulmány ellenére - kicsit száraznak találtam a téma feldolgozását. Ami lerontotta az értékelést, az kiadvány megjelenése, pontosabban a belseje. Az oldalak elrendezése, a használt stílusok, a táblázatok - minden nagyon igénytelen, mintha az alapértelmezett Microsoft Word-sablonba szürke-fehér sávos Excel-táblákat másolt volna a kiadvány tervezője, és azzal meg is elégedett volna. Nagy jóindulattal adtam rá hármast, így lett az átlag négyes.
The book is quite good in the sense of practical approach. It's a different and a much lighter than the previous book what it's really appreciated if you do not want to read more than 500 pages to get the idea of what's Disciplined Agile.
The bad point is that is already deprecated in some sections (inception phase) and it seems that sometimes the author is eager to attack Scrum. Because sometimes is clear what aspects Scrum is missing and DA complements and sometimes Scrum is just attack badly. Badly because there are bad assumptions and sometimes old terminology which has already evolved in Scrum. This deprecated information and lack of precision puts this book one step below of the place it could be.
Based on the introduction, I was extremely skeptical. I thought, "great, another watered down Agile method".
Very glad I got past. There was even a character in the book that shared my lack of ambition. Disciplined Agile Delivery is based on Hard experience found at IBM. Its a great way to introduce teams to Agile and even more importantly, it also helped ease questions from Management. I will definitely be using some of the advice in my next project.