Goodreads helps you keep track of books you want to read.
Start by marking “Clean Agile: Back to Basics” as Want to Read:
Clean Agile: Back to Basics
by
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 of software developers. In this eagerly-awaited book, the best-selling author of The Clean Coder shows how to bring unprecedented levels of professionalism and discipline to agile development -- and thereby w
...more
Get A Copy
Paperback, 240 pages
Published
October 27th 2019
by Pearson
Friend Reviews
To see what your friends thought of this book,
please sign up.
Reader Q&A
To ask other readers questions about
Clean Agile,
please sign up.
Recent Questions
This book is not yet featured on Listopia.
Add this book to your favorite list »
Community Reviews
Showing 1-30

Start your review of Clean Agile: Back to Basics

This book talks about the history of Agile and, as the subtitle suggests, the basics of it. It also tries to bring some sanity to the subject. Great to see Bob’s perspective after 18 years of the Agile Summit in 2001. It was a pleasure for me to write the chapter on Software Craftsmanship and contribute to this book.

It's good to be reminded what was Agile (is it a noun now?) all about in the beginning, before it became distorted beyond all recognition by the industry. The book should probably be obligatory for everyone working in IT. Although, I don't agree with everything, especially with the critique of Agile Lifecycle Management (ALM) systems and I don't think that implementation of the presented practices is as easy as Uncle Bob says. If it would be that easy, there wouldn't be so much struggle, especia
...more

I'm a Robert C. Martin fan, but this book is the same content from videos and other presentations all over repeated again. There is nothing new. Maybe, for newcomers to the Uncle Bob world, it can be fun to read and they can be delighted by his pragmatism. However, nothing new in the shop. Maybe he could try with different content that we are not so used to from him such us functional programming, for example.
...more

A must-read for everyone involved on software engineering. Well, if you really want quality and functional software, whether you are an engineer or an executive.
This book is an oasis of knowledge and principles in times like these when Agile is being totally misinterpreted by people who want to do old, unprofessional and ineffective management practices with new "agile" names, roles and complex "scaled" frameworks. It has tons of experience, results and skin in the game in form of sentences. ...more
This book is an oasis of knowledge and principles in times like these when Agile is being totally misinterpreted by people who want to do old, unprofessional and ineffective management practices with new "agile" names, roles and complex "scaled" frameworks. It has tons of experience, results and skin in the game in form of sentences. ...more

This book is not an introductory text. Indeed, it requires that you'd been in the software industry for the last years because it's a deep analysis of the Agile movement and how and why it was created, and how it has evolved and adopted by the teams and companies.
Robert Martin's vision is clear here. The Agile ideas were good. They tried to solve common problems that the development companies had all around the world. But since its release, the ideas and principles were turned into a completely ...more
Robert Martin's vision is clear here. The Agile ideas were good. They tried to solve common problems that the development companies had all around the world. But since its release, the ideas and principles were turned into a completely ...more

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 ...more
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 ...more

This is probably not a must-read, but still a very interesting, thoughtful and personal perspective on Agile. Martin brings the often forgotten developers side to the equation and strongly advertises software craftsmanship as a way to incorporate the often forgotten and ignored parts of agile (XP, TDD, Pair Programming, ...) into today’s organizations. With this the book is an important contribution to the history of agile!

I feel this book is just repeating all the essentials of earlier books in this Clean Code series. Though, it does add new materials taken from Uncle Bob's experiences
...more

Wonderfully opinionated (and slightly grumpy) polemic on getting back to the basics of Agile software development. Worth the price of admission just for the extended rant about project deadlines: "What is the first thing you know about a project? Before you know the name of the project or any of the requirements, there is one piece of data that precedes all others. The Date, of course. And once The Date is chosen, The Date is frozen. There’s no point trying to negotiate The Date, because The Dat
...more

Brilliant absolutely brilliant!!
Too many of us in this industry including myself think we know what agile is and that we are working for organisations who do agile and maybe work for companies who claim to be agile.
Uncle Bob as one of the original signatories to the agile manifesto clears alot of misconceptions.
Will be recommending this book to all at work fellow developers and PM's ...more
Too many of us in this industry including myself think we know what agile is and that we are working for organisations who do agile and maybe work for companies who claim to be agile.
Uncle Bob as one of the original signatories to the agile manifesto clears alot of misconceptions.
Will be recommending this book to all at work fellow developers and PM's ...more

A good book for developers. It tells what it means to be a professional developer.
We read through war stories which teach us principles, concepts and tips on how to stay on track during project development. Uncle Bob reminds us not to cut corners, not to ask for permission to work in a professional manner (ex to ask to set CI), to say early about the problems in the project... and the list goes on.
We learn about Agile fundamentals, why it was born, what problems was it addressing when it was cre ...more
We read through war stories which teach us principles, concepts and tips on how to stay on track during project development. Uncle Bob reminds us not to cut corners, not to ask for permission to work in a professional manner (ex to ask to set CI), to say early about the problems in the project... and the list goes on.
We learn about Agile fundamentals, why it was born, what problems was it addressing when it was cre ...more

This book consists of three parts:
1. Short memoir about the meeting where Agile Manifesto had been initiated. Interesting, even, as "Uncle Bob" himself admits he did not check any sources and trusted his memory only and many other participants described it differently.
2. Description of what Agile is - from team, individual, company perspective. It's very confusing part. While the author himself agreed before that "Agile"!= XP all he describes as "Agile" is actually XP. He talks (mostly negative ...more
1. Short memoir about the meeting where Agile Manifesto had been initiated. Interesting, even, as "Uncle Bob" himself admits he did not check any sources and trusted his memory only and many other participants described it differently.
2. Description of what Agile is - from team, individual, company perspective. It's very confusing part. While the author himself agreed before that "Agile"!= XP all he describes as "Agile" is actually XP. He talks (mostly negative ...more

A great reminder of what Agile is and how it should be. This book outlines the history of Agile, what problems it is trying to solve and what the important principles and practices that should be understood in order to do Agile well. This book is lightweight and doesn't go deep into each of those, but serves as guidance for us to go deeper into each of the topic when required.
For me as someone who already has experience in the industry, this book helps me to deepen my understanding, aware of the ...more
For me as someone who already has experience in the industry, this book helps me to deepen my understanding, aware of the ...more

The book sells itself well. It really is about the basics of agile, with some useful history thrown in. As a software professional, I found it to be very helpful in order to formulate an opinion about practices commonly found in agile, such as continuous integration and refactoring. I want to be clear, there is a difference between saying "XP does refactoring" and "This is why XP does refactoring". This book uses the latter style to convey why different practices are used. Knowing the reason why
...more

A great book on agile and software craftsmanship, written with an emphasis on what the author view as the most important aspect of the agile development process. His wisdom and experience on the subject gives it an honest touch that align with my own view when it comes to agile, and the experience of practicing it for the last 13 years.
My first introduction to agile were through Scrum, that actually worked quite well. We did not follow it strictly, we did estimate, but that were just to give us ...more
My first introduction to agile were through Scrum, that actually worked quite well. We did not follow it strictly, we did estimate, but that were just to give us ...more

I really loved the introductory chapters of this book, and got a lot out of it as a whole. I have been a huge Uncle Bob Martin fan since my early days as a software craftsman.
However, I did find it to not be super cohesive or targeted in its audience. At times, there seemed to be an assumption that the reader was familiar with all the existing Agile frameworks (Kanban, Scrum, etc...) and the History of Agile and project managment. But then there were chapters which were super basic and explained ...more
However, I did find it to not be super cohesive or targeted in its audience. At times, there seemed to be an assumption that the reader was familiar with all the existing Agile frameworks (Kanban, Scrum, etc...) and the History of Agile and project managment. But then there were chapters which were super basic and explained ...more

The first disappointment by Uncle Bob. I don't think I will ever return to this book for whatever reason. It's a shame though! I just love all of his other books! But this one... I didn't find any value in it. Furthermore, 20-25% of the content is taken from other authors (with permission!). It feels like he was forced by his publishers to write this book although he hadn't that much important stuff to say. There are much better books on the topic. I'm just glad I read the book before I purchase
...more

A Must read for all people that is supposed to create any kind of digital product. Agile is supposed to be everywhere. But what we're seeing is something like, not agile at all. This book try to recover what agile is for managers and developers with the fundation that agile was built. In my opinion, this book is for every developer (beginner or not) that want to learn how to develop good code, not only things that "work". As well, it will teach you, manager, how to get the most of Agile practice
...more

This one was recommended to me by a teammate, and is only the second book by Uncle Bob that I have read (first one was Clean Code). I genuinely had chills as I started reading this and I ended up finishing it in just one day. You know that feeling when you want to tell someone how much you agree with everything they said? :P This book is a must read for any software developer.
Here is something that made me laugh: "Some folks think that Agile is about going fast. It’s not. It’s never been about g ...more
Here is something that made me laugh: "Some folks think that Agile is about going fast. It’s not. It’s never been about g ...more

Maybe an article would be more convenient way to share the content of this book but then again it depends on the audience. If you have <2 years of experience working in an Agile environment go on and read the whole thing, otherwise feel free to skim through it. I enjoyed the exposure of common misconceptions of Agile i.e. that you can't just apply the ceremonies without the technical processes (TDD, pair programming), and some insights around the actual roles of Product Owners and Scrum Masters.
...more

Agile manifesto is composed of high-level, simple, instinctive statements (and it should be this way, for sure)... But interpretation of this principles on any organizations daily activities is painful, mostly from the perspective of ierarchical vs n/ierarchical structures...
Reading very similiar cases from Uncle Bob's experience somehow brings relief but also brings the urge to fix things up, finally.. ...more
Reading very similiar cases from Uncle Bob's experience somehow brings relief but also brings the urge to fix things up, finally.. ...more

I enjoyed the book, even though I disagree with some statements (in particular, that it's OK to continuously underdeliver under the justification that the sprint is not a commitment). The book is an easy read, it explains well how XP, Scrum, Agile, agile, and Software Craftsmanship are connected, and I recommend it to everyone no matter how much experience you have working in an agile environment.
...more

A huge disappointment and easily the worst book from Uncle Bob. There is nothing in this book that wasn't already published; most of ideas are borrowed from Pragmatic Programmer. The chapter about agile coaches written by another guy, which contradicts the author's opinion, is totally out of place. The whole book can be three time shorter and still tell the same story.
...more

An overview of the history, philosophy and practices every agile practitioner should know. Entertaining, to the point, enlightening.
The chapters by guest authors complement Bob's material well. An alternative view on coaching and scaled up Agile creates balance. A chapter on Craftsmanship highlights an essential step in the maturation of agile. ...more
The chapters by guest authors complement Bob's material well. An alternative view on coaching and scaled up Agile creates balance. A chapter on Craftsmanship highlights an essential step in the maturation of agile. ...more

I especially liked this because of the way that he told the history of the movement! I love that kind discussion. While I came for this history, I got a great introduction to Agile as well. Being a practitioner of Agile, I appreciate the discussion of the subtleties of the movement that are largely missed by drive-by "leaders".
...more

A short book, Uncle Bob C Martin takes you through the birth of Agile to how it is at the present. While explaining that he emphasizes the practices that has worked for him and he has seen it work. Everything that he talks about is battle tested and endorsed by him. Agile is a customized set of practices for a small software development team.

When you're reading this book it all seems so obvious and simple. And then you remeber all the times you've seen some pathological aberration of Agile. It's good there's a book that gives us some perspective and a concise overview of what this movement was really about and what it was meant to be in the first place.
...more
There are no discussion topics on this book yet.
Be the first to start one »
Goodreads is hiring!
Robert Cecil Martin, commonly called Uncle Bob, is a software engineer, advocate of Agile development methods, and President of Object Mentor Inc. Martin and his team of software consultants use Object-Oriented Design, Patterns, UML, Agile Methodologies, and eXtreme Programming with worldwide clients.
He was Editor in Chief of the C++ Report from 1996 to 1999. He is a featured speaker at internatio ...more
He was Editor in Chief of the C++ Report from 1996 to 1999. He is a featured speaker at internatio ...more
News & Interviews
Need another excuse to treat yourself to a new book this week? We've got you covered with the buzziest new releases of the day.
To create our...
48 likes · 12 comments
No trivia or quizzes yet. Add some now »
“Adding manpower to a late project makes it later.”
—
2 likes
“If a change to the requirements breaks your architecture, then your architecture sucks.”
—
2 likes
More quotes…