Image from Amazon Title: Clean Agile: Back to Basics
Author(s): Robert C Martin
InformIT wrote:Nearly twenty years after the Agile Manifesto was first presented, the legendary Robert C. Martin (“Uncle Bob”) reintroduces Agile values and principles for a new generation–programmers and nonprogrammers alike. Martin, author of Clean Code and other highly influential software development guides, was there at Agile’s founding. Now, in Clean Agile: Back to Basics, he strips away misunderstandings and distractions that over the years have made it harder to use Agile than was originally intended.
Martin describes what Agile is in no uncertain terms: a small discipline that helps small teams manage small projects . . . with huge implications because every big project is comprised of many small projects. Drawing on his fifty years’ experience with projects of every conceivable type, he shows how Agile can help you bring true professionalism to software development.
Get back to the basics–what Agile is, was, and should always be
Understand the origins, and proper practice, of SCRUM
Master essential business-facing Agile practices, from small releases and acceptance tests to whole-team communication
Explore Agile team members’ relationships with each other, and with their product
Rediscover indispensable Agile technical practices: TDD, refactoring, simple design, and pair programming
Understand the central roles values and craftsmanship play in your Agile team’s success
This book was a mix of memory lane, tips and essays from others.
The preface explains that this is a small book because it solves a small problem. The author reminisces about the the Snowbird meeting and the start tho the agile manifesto. He talks about 4 agile frameworks. (It's been a while since I thought about XP).
I like that he asks you to count the number of computers in your life. (Did you remember to count things like your clock and DVR). It was fun hearing the origin of the term “checkout” for source code. (from checking out physical punch cards from the drawer).
There are many good examples and stories throughout. I liked “Who is training the new people? The people who made the mess in the first place”. The point that the outer circle of Scrum is a “highly efficient way to make a large mess.”
The last two chapters were essays written by others, but they fit well. We are currently on lockdown due to coronavirus, but I look forward to passing this book around when I see people again!
I give this book 10 out of 10 horseshoes.
Disclosure: I received a copy of this book from the publisher in exchange for writing this review on behalf of CodeRanch.