Nicole Forsgren

DevOps, roughly speaking, seeks to get IT workers to interact with each other more – particularly when they are in different functional roles. Authors Humble and Kim have led this movement and pioneered annual studies to ascertain its progress among practitioners of technology. In this book, they team together with Forsgren (a PhD who brings a rigorous knowledge of statistics and data collection to the table) to present their findings and explain their methods.

IT professionals are show more notorious for trusting what a computer says over what their fellow humans say – even when the computational figures can be shown as inaccurate. They tend to distrust “subjective” surveys (even the most rigorous) over “objective” data sources. In this work, Forsgren runs head-first against that prevailing wind to sail cleanly into the harbor of first-rate technology organizations.

In this work, these three authors share what to look for in high-performing organizations with technology centers. They distinguish those from characteristics of other clusters with mid-level or low performance. In an ever-changing, competitive tech environment, these findings, grounded in rigorous data collection and analysis, shine a light onto what to aspire towards in an IT group. Reading them can save needless experimentation as it confirms employees’ collective instincts as to the path forward.

Information technology is now central to our lives in modern societies. Thus, it is important to just about every major corporation (i.e., a “vertical”). Those who manage, work in, or interface with technology sectors can benefit from learning what a healthy tech workforce looks like. That is this book’s main audience. Researchers about, teachers of, and students in computer science serve as another market as these groups learn about what modern workplaces look like in the “real world.”

I’ve been a fan of the DevOps movement for a while now. I’ve worked in environments (academic research labs) that practice DevOps principles since 2001… well before the movement became organized. The ability to wear many hats and think through various functions just seems beneficial towards producing high-quality software. In recent years, Kim and Humble have articulated the foundations of this movement. In this book, Forsgren’s addition of grounding their theories in rigorous data analysis is welcomed and serves to transform the tech industry even further. show less

Uninspiring. Authors seem pretty concerned about explaining to you why their research uses valid methods (even including a whole section on statistics), rather than delving into the research that the title suggests the book would. Perhaps they felt they needed to prop up the research, because really all that's here are surveys with a biased sample selection and subsequent correlation investigations. I'm already on board with many of the things this book espouses, but I just couldn't get show more behind the way the authors approached it here. For a better treatment that doesn't try to obscure the fact that there still isn't really any true RCT-type research in this area, see Kim's earlier work [b:The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win|17255186|The Phoenix Project A Novel About IT, DevOps, and Helping Your Business Win|Gene Kim|https://i.gr-assets.com/images/S/compressed.photo.goodreads.com/books/1361113128l/17255186._SX50_.jpg|23848838] -- a much more readable piece. show less

O centro deste livro é a descrição de 24 habilidades (práticas) divididas em 5 categorias (Continuous Delivery, Architecture, Product and Process, Lean Management and Monitoring, Cultural) em times de desenvolvimento de software, baseado no resultado de pesquisas.

Apesar de ter gostado mais da primeira metade do livro, acredito ser completamente necessário para todas as pessoas que trabalham em times de desenvolvimento, não só para refletir sobre as práticas colocadas neste livro, show more como para potencialmente entender contexto e influenciar pessoas para aplica-las.

Um bom livro para entender um pouco sobre
práticas ágeis e como elas se aplicam dentro de times de desenvolvimento, assim como algumas diferenças de comportamento ou tempo investido em situações diversas entre times de baixa e alta performance, entendimento de cultura e motivação - potenciais situações que podem levar a insatisfação e burnout.

Apesar de ter gostado do livro, uma coisa me chamou atenção e me despertou a vontade de ter novamente a pesquisa considerando diversidade: apenas 6% das pessoas entrevistadas são mulheres, 3% não binárias ou outros. 77% não se considera de grupos minoritários (oprimidos), 12% se considera. Porém os autores são explícitos que fizeram teste para evitar viéses. show less

Lots of good advice, most of which is out in the wild today (automated testing, working in small batches, loose arch etc.). Findings are based on survey data, so gigo, but as most of the conclusions are common sense I don't think the lack of 'real' data is an issue.

Part one of the book and the appendix were most useful to me - your mileage will vary depending on your role.

CI/CD making for happy developers is fair enough, but I'm not totally onboard with it causing 'better' software. Other show more areas of dev may need attention before jumping all in with CI/CD. show less