An easy read detailing a lot of good practices of working in a team. Some of the technical examples might not fit you or seem a bit outdated, but still most of the advice is solid. Also back of book includes a handy recap card which you can refer to later. Recommended:)

I was looking for a really high level book on Agile. The 1st book I got was not for beginners... I needed an intro book. This book was a good beginner book.

This book is easy to read and it was very similar to the Pragmatic Programmer style. I now want a book just like this but for SCRUM and XP. Overall I'm glad I read this book. I've already set the wheels in motion to apply some of the Agile procedures mentioned in this book.

The only CON I have for this book is that it may be a little too idealistic. When you work with different personalities, nothing ever goes as easy as the author says it does. But with that being said, the intent of what he was trying to get across was good.

Excellent technical book. Could be revolutionary to beginners. Very good read. Small chapters, with small sections.

Extremely digestible with very well-thought out examples and ideas. I loved the examples of what each practice looked like to start out, as well as ideally. Would 100% recommend.

Proven practices for making the best out of agile development. Great book to refer to for integrating or reinforcing some of these practices over time.

This is a book for both developers unfamiliar with agile principles and best practices, as well as seasoned professionals who want a refresher course. It is an easy read.

Great read, short and concise.

I really enjoyed it, it speaks about practices from a very high level, you could probably go more in-depth about each subject, but I think that is what makes this book unique.

Contains great lessons, but is not too heavy of a read.

A coherent sequence of tips for programmers, carefully, clearly and cogently explained. A useful handbook.

This book is sometimes pitched as the successor to "The Pragmatic Programmer," but I didn't think it was all that.

The practices in this book are genuinely good and worth thinking about. The presentation format - essentially a long list of advice - could use some work.

Some good quotes:

Agile development uses feedback to make constant adjustments in a highly collaborative environment.

Software development doesn’t happen in a chart, an IDE, or a design tool; it happens in your head.

No plan survives contact with the enemy. - Helmuth von Moltke

As U.S. President Eisenhower said, “The plan is worthless. The planning is essential.”

You can’t freeze requirements any more than you can freeze markets, competition, learning, evolution, or growth.

Reading this shortly after having read Debug It! felt like it was touching (and reinforcing) some of the same points, making both books more interesting when read together.

Some interesting tidbits but not much new given the current agile literature. For developers trying to get into agile I would suggest to read a standard Scrum/XP/... introduction and the deep-dive into programming stuff with, e.g., Robert Martin's Clean Code or Lasse Koskela's Test Driven.