Buy new:
$26.13$26.13
FREE delivery:
Thursday, April 11
Ships from: Follow Books Sold by: Follow Books
Buy used: $22.75
Other Sellers on Amazon
& FREE Shipping
90% positive over last 12 months
FREE Shipping
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required.
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
Image Unavailable
Color:
-
-
-
- To view this video download Flash Player
-
-
-
-
-
VIDEO -
Follow the author
OK
Clean Agile: Back to Basics (Robert C. Martin Series) 1st Edition
Purchase options and add-ons
Agile Values and Principles for a New Generation
"In the journey to all things Agile, Uncle Bob has been there, done that, and has the both the t-shirt and the scars to show for it. This delightful book is part history, part personal stories, and all wisdom. If you want to understand what Agile is and how it came to be, this is the book for you."
Grady Booch
"Bob's frustration colors every sentence of Clean Agile, but it's a justified frustration. What is in the world of Agile development is nothing compared to what could be. This book is Bob's perspective on what to focus on to get to that what could be. And he's been there, so it's worth listening."
Kent Beck
It's good to read Uncle Bob's take on Agile. Whether just beginning, or a seasoned Agilista, you would do well to read this book. I agree with almost all of it. It's just some of the parts make me realize my own shortcomings, darn it. It made me double-check our code coverage (85.09%)."
Jon Kern
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
If you want Agile's true benefits, there are no shortcuts: You need to do Agile right. Clean Agile: Back to Basics will show you how, whether you're a developer, tester, manager, project manager, or customer. Register your book for convenient access to downloads, updates, and/or corrections as they become available. See inside book for details.
- ISBN-100135781868
- ISBN-13978-0135781869
- Edition1st
- PublisherPearson
- Publication dateOctober 17, 2019
- LanguageEnglish
- Dimensions7 x 0.7 x 9 inches
- Print length240 pages
Frequently bought together

Similar items that may ship from close to you
From the brand
From the Publisher
From the Foreword by Jerry Fitzpatrick, Software Renovation Corporation
"It has been 18 years since the Agile Manifesto was published. It is, therefore, ancient history to most of today’s developers. For this reason, your understanding of Agile development may not line up with the intent of its creators.
This book aims to set the record straight. It provides a historical lens through which to view Agile development more fully and accurately. Uncle Bob is one of the smartest people I know, and he has boundless enthusiasm for programming. If anyone can demystify Agile development, it’s him."
Editorial Reviews
About the Author
Robert C. Martin (Uncle Bob) has been a programmer since 1970. He is cofounder of cleancoders.com, which offers online video training for software developers, and is founder of Uncle Bob Consulting LLC, which offers software consulting, training, and skill development services to major corporations worldwide.
Previously, he served as the Master Craftsman at 8th Light Inc., a Chicago-based software consulting firm for three years, as editor-in-chief of the "C++ Report", and as the first chairperson of the Agile Alliance. Mr. Martin has published dozens of articles in various trade journals and is a regular speaker at international conferences and trade shows. He has written and edited many books, including Clean Code, The Clean Coder, and Clean Architecture (all from Pearson).
Product details
- Publisher : Pearson; 1st edition (October 17, 2019)
- Language : English
- Paperback : 240 pages
- ISBN-10 : 0135781868
- ISBN-13 : 978-0135781869
- Item Weight : 12.7 ounces
- Dimensions : 7 x 0.7 x 9 inches
- Best Sellers Rank: #175,812 in Books (See Top 100 in Books)
- #60 in Software Testing
- #194 in Software Development (Books)
- #3,794 in Unknown
- Customer Reviews:
About the author

Robert Cecil Martin (colloquially known as Uncle Bob) is an American software engineer and author. He is a co-author of the Agile Manifesto.
Bio from Wikipedia, the free encyclopedeia. Photo by Tim-bezhashvyly (Own work) [CC BY-SA 4.0 (http://creativecommons.org/licenses/by-sa/4.0)], via Wikimedia Commons.
Customer reviews
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
Learn more how customers reviews work on AmazonReviews with images
-
Top reviews
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
The only thing I'd argue about is the author 's approach to acceptance testing. I believe the more practical and even more 'agile' way would be to let them emerge from implementation and subsequent approval by customer and then be automated instead of trying to automate in advance.
If you are just starting head over XP Explained by Kent Beck and mix that with maybe Scrumban so you get a mix of Scrum and Kanban also try some Lean Startup by Eric Cries ... Most important than all that is to read a lot but use your head and adapt ... listen to your pain and don't push it too far
Cheers
Reviewed in the United States on September 30, 2020
Overall impression: Clean Agile is not about the basics of agile since it is full of today's deprecated agile practices. It would be more basic without those practices. As the author acknowledges, the book is his memories, opinions, rantings, and ravings. For agile basics, look somewhere else.
The Preface is somewhat disappointing in the very first sentences: “This book is not a work of research…”. It feels like giving yourself a license to say incorrect things. I’m in doubt in which way to read the book, and whether to take anything seriously. So, I decided to take the book and its content seriously and disregard these first sentences.
The author mentions the “big teams” term several times. It is in the beginning not clear what exactly is considered “big teams”. Is it any kind of large group of people working on a single complex product regardless of how they are organized? That doesn’t seem to be the case since “many small teams doing small things” is ok. But I’m not sure what is “small things”. E.g. who makes sure that small things fit together? “Many collaborating teams” is mentioned further, so that seems to imply that small teams can together do big things. Unclear.
This lack of clarity is surprising since the preference for small teams over big teams is the key idea behind the word “Agile”.
Chapter 1: Introduction to Agile
It starts with his personal historic recollection. There are several incorrect references to names, papers, and dates. A reader is advised to not quote any of these before doing a proper check. Even recollection of gathering at Snowbird where the Agile Manifesto was created conflicts a bit with recollections from other participants. This is understandable considering how much time has passed and nobody made a detailed recording of what exactly was said or happened.
In the “Agile Overview” part, the author tells a hyperbolic story on how waterfall projects are organized with a strict distinction between different phases in order to bring a message across. After this story, a better way is explained. An iterative way. There is in this and previous part a lot of focus on the planning aspect of iterative development, in the context of doing “projects”.
Chapter: Reasons for Agile
The author explains in a clear and practical way the reasoning and benefits of Agile, through many examples of the way of working and practices that accompany this way of working.
The bill of rights for developer and customer is especially useful and clear.
I do notice in this chapter apparent exclusion of product development system dynamics caused by the complicated structure of many roles. Those matters a lot since this can make or break a practice. An example: “QA should find no faults with the system.”. This is an oversimplification of the problem.
In this same chapter, there is a definition of customer. An example of what is understood as a customer, among others, is the project leader. It seems that whoever holds a budget or has a major influence on payment of developer is a customer. Also, it seems that the money aspect has a large significance in agile software development in the eyes of the author. The one who has authority on money needs to be pleased.
The author makes a remark about a Volkswagen developer a number of times. Yet again an example of not taking organizational and cultural aspects into consideration. After a bit of understanding of German engineering/corporate culture, one can discover that those developers didn’t decide to cheat the EPA test. They had a requirement and they delivered accordingly. A requirement was to make sure that the EPA test succeeds and the whole organizational system surrounding them creates this expectation. Just make sure EPA test succeeds! Most humans yield to such a system or at best warn management (which happened at VW). Only in exception, a developer can resist that. This will never change. The real problem is systemic, and cannot be solved by being a better developer but by changing the system.
Making sure that cars produce very good results in a specific test situation is an established practice in the car industry. Nothing new about this. Diesel gate is just a more extreme manifestation.
Chapter: Becoming Agile
The author doesn’t seem interested in problems of product development with many teams since the problem is “already solved” according to him. Solved a long time ago. 5000 years ago. For the author, the two problems are separate. Whether you do software development or anything else, how to organize many teams is unrelated to software.
The view is astonishing. Especially considering it is purely an opinion and not backed by any further reasoning, research or evidence.
Chapter: Business Practices
The author mentions agile practices that are either discarded nowadays or explained by the author, not as a practice is intended. By far the biggest issue is that iterative development seems to be intended for managers to better manage delivery. Iterative nature (feedback, inspecting and adapting, users involvement) is almost completely lacking in explanation. Though, there is just a general remark that feedback is important in chapter 6 (Becoming Agile).
There are many statements such as this one: “The purpose of an iteration is to generate data for managers”. This thinking is manifested in the explanation of practices:
- Iteration zero is mentioned but in community commonly considered a bad practice (phased development in disguise)
- “The Demo” is used to make sure developers are working and not hiding things from “stakeholders” according to author
- “In Scrum, the customer is called the Product Owner. This is the person (or group) who chooses stories, sets priorities, and provides immediate feedback.” is not correct.
There is a lot of good and clearly explained things in this book. All more technical practices are really nice to read. Unfortunately, the more author moves away from technical practices the more blurry, false or astonishingly illogical it becomes. So, considering a large amount of simplistic or outdated descriptions I’m not sure who should read this book. It only partially gives clarity on what agile basics really is.
Top reviews from other countries
Il décrit avec précision tous les problèmes d'aujourd'hui, les frustrations constantes que nous vivons comme développeurs.
Trop souvent, les gens ne comprennent pas AGILE et leur conception est à des années lumières de ce que AGILE était au départ. Uncle Bob remet les pendules à l'heure, simplement, clairement et avec précision.
Bravo!
I do miss some content around using agile in teams working in enterprise environments and developing on systems such as low code platforms, where implementations of technical practices of agile such as simple design, refactoring and TDD if not close to impossible it’s truly uncharted territory for agile.












