The most recommended agile software development books

Suzanne and James Robertson have been writing insightful books on software requirements for many years. This book covers all the important topics, including understanding the real problem, different techniques for exploring solutions, and numerous ways to communicate requirements effectively. I especially like their treatment of quality attribute requirements and defining “fit criteria” to judge whether a solution adequately addresses them.

The book includes a comprehensive requirements specification template to guide writing a rigorous and complete specification on projects for which that is valuable. I also appreciate their use of visual models both to communicate with the reader and to guide the reader in communicating requirements to project stakeholders. I do prefer my book Software Requirements, but this is an excellent choice as well by two authorities in the field.

Gerald M. – Jerry – Weinberg is my most-often quoted author.

Having spent more than 50 years in the software world, Jerry was able to write in a timeless manner about the lessons he learned. Over the years, he collected more and more stories he survived from, including all aspects that brings software from an idea to a product that everyone can use.

In this first volume in his Quality Software Management series, he will extend your perspective with Causal-Loop Diagrams and thereby introduce you to the world of Thinking in Systems.

The takeaways from his stories are fostered in easy-to-remember laws and principles that he gives you as a free takeaway summary in the end as well. Extend your perspective on managing for quality rather than staying oblivious.

Accelerate is a book about data. The authors used data collected during their PhD projects in order to prove The DevOps is effective.

They have all sorts of different ways to measure DevOps, it sufficiency, and the fact that way more projects succeed when you do DevOps, rather than waterfall methodology.

The book essentially show can be used as evidence of return on investment when modernizing your IT department. I am a person who loves data, and thus I absolutely love this book. Also, if you listen to the audiobook version, one of the authors reads it to you and her personality really shines through in a fun way.

I really enjoyed listening to Nicole read a book about to me about data!

This is the most recent book I'm recommending, and it’s also more than just a book on Test-Driven Development. I often proclaim that Test-Driven Development and software design are two sides of the same coin. One cannot separate one from the other. So learning about Test-Driven Development also means that one has to learn about software design principles. This book teaches both. The first part of the book is all about Test-Driven Development, while the remainder of the book also touches on object calisthenics, refactoring, code smells, design patterns, the S.O.L.I.D. principles, connascence, the four elements of simple design, and much more. Whether you’re new to programming software, or whether you’re a seasoned developer, there’s much to learn from this book.      

Many agile projects employ user stories as a way to represent requirements rather than a more traditional approach combining use cases and functional requirements. I favor the latter approach for several reasons. Nonetheless, user stories are well established in the agile development world, and if you wish to learn about them, there’s no better author to read than Mike Cohn. Cohn describes how to craft user stories well and how they fit into the agile development process.

When I read the very first page, I had an “aha!” moment. Singh explains that scaling flow, the flow of work through the teams, is the single most important idea in “scaling” agility. That means each team optimizes for their challenges, not a specific process. 

I loved this book because Singh makes the principles of flow easy to understand and apply. That’s the “secret” to scaling agility. 

The second book from Gregory and Crispin brought me up-to-date on the different trends in the Agile world, ten years after having delved into their first book.

How do you share the quality mindset in a DevOps culture? What about Design Thinking? With many more examples from the industry, the two authors made me curious about some of the things that I had ignored until I read their book.

While this book was still in the writing, Crispin and Gregory published draft chapters on the internet.

At the time, I read them, and managed to introduce many of the great insights into my own work. Even though I was working in a more traditional environment, the ideas from the two ladies inspired me on my journey to the agile methodologies.

I even managed to contribute some of my own real-world examples from my own experiences to their writings – and they decided to include some of them.

It may seem strange to include a jobseeker’s guide in a list of leadership books, but Agile Unemployment is the resource for anyone faced with the hardest leadership task of all: leading yourself through a time of trial.

Sabina Sulat has been there—on both sides of the HR desk for “that conversation”—and she offers her well-earned wisdom with deep candor, much-needed encouragement, and straight-shooting practicality. In my early career days, I always found the “What color is your parachute” genre pretty useless, not to mention incredibly depressing. I wish I’d had Sulat’s sound guidance back then; it would have helped me lean in, out, up, down, and sideways with far more grace and optimism.

When agile software development emerged, many developers saw it as a way to end the era of death march projects. The more "agile" caught on, the less it looked like the original concept.

In the face of the corruption of the movement, Joy Of Agility is a wonderful return to positive ideas that make you agile, not hasty. As we all push back against the industrial complex that has appropriated the agile movement, this book is the white wizard shining blinding light that chases away the monsters.