The Art of Agile Development [NOOK Book]


The Art of Agile Development contains practical guidance for anyone considering or applying agile development for building valuable software. Plenty of books describe what agile development is or why it helps software projects succeed, but very few combine information for developers, managers, testers, and customers into a single package that they can apply directly.

This book provides no-nonsense advice on agile planning, development, ...

See more details below
The Art of Agile Development

Available on NOOK devices and apps  
  • NOOK Devices
  • Samsung Galaxy Tab 4 NOOK 7.0
  • Samsung Galaxy Tab 4 NOOK 10.1
  • NOOK HD Tablet
  • NOOK HD+ Tablet
  • NOOK eReaders
  • NOOK Color
  • NOOK Tablet
  • Tablet/Phone
  • NOOK for Windows 8 Tablet
  • NOOK for iOS
  • NOOK for Android
  • NOOK Kids for iPad
  • PC/Mac
  • NOOK for Windows 8
  • NOOK for PC
  • NOOK for Mac
  • NOOK for Web

Want a NOOK? Explore Now

NOOK Book (eBook)
$17.99 price
(Save 43%)$31.99 List Price


The Art of Agile Development contains practical guidance for anyone considering or applying agile development for building valuable software. Plenty of books describe what agile development is or why it helps software projects succeed, but very few combine information for developers, managers, testers, and customers into a single package that they can apply directly.

This book provides no-nonsense advice on agile planning, development, delivery, and management taken from the authors' many years of experience with Extreme Programming (XP). You get a gestalt view of the agile development process, including comprehensive guidance for non-technical readers and hands-on technical practices for developers and testers.

The Art of Agile Development gives you clear answers to questions such as:

  • How can we adopt agile development?
  • Do we really need to pair program?
  • What metrics should we report?
  • What if I can't get my customer to participate?
  • How much documentation should we write?
  • When do we design and architect?
  • As a non-developer, how should I work with my agile team?
  • Where is my product roadmap?
  • How does QA fit in?
The book teaches you how to adopt XP practices, describes each practice in detail, then discusses principles that will allow you to modify XP and create your own agile method. In particular, this book tackles the difficult aspects of agile development: the need for cooperation and trust among team members.

Whether you're currently part of an agile team, working with an agile team, or interested in agile development, this book provides the practical tips you need to start practicing agile development. As your experience grows, the book will grow with you, providing exercises and information that will teach you first to understand the rules of agile development, break them, and ultimately abandon rules altogether as you master the art of agile development.

"Jim Shore and Shane Warden expertly explain the practices and benefits of Extreme Programming. They offer advice from their real-world experiences in leading teams. They answer questions about the practices and show contraindications - ways that a practice may be mis-applied. They offer alternatives you can try if there are impediments to applying a practice, such as the lack of an on-site customer.

--Ken Pugh, Author of Jolt Award Winner, Prefactoring

"I will leave a copy of this book with every team I visit."

--Brian Marick, Exampler Consulting
Read More Show Less

Product Details

  • ISBN-13: 9780596553791
  • Publisher: O'Reilly Media, Incorporated
  • Publication date: 10/26/2007
  • Sold by: Barnes & Noble
  • Format: eBook
  • Edition number: 1
  • Pages: 440
  • Sales rank: 639,687
  • File size: 4 MB

Meet the Author

James Shore has been leading teams in Agile development since 1999. A team member on that first project introduced him Ward Cunningham's wiki, where they were talking about a crazy idea called Extreme Programming. Despite the ridiculous name, James tried Extreme Programming on his next project and discovered that it worked far better than it sounded. James has been speaking, teaching, and writing about Agile methods ever since. Today, he continues to lead Agile teams using the best ideas from Scrum, Extreme Programming, and Lean.

James has contributed a large number of projects and ideas to the Agile community. He authored the first test-driven development framework for .NET web programming and coordinated the development of Ward Cunningham's Fit, the first major acceptance-testing tool. In 2005, the Agile Alliance recognized James with their highest honor, the Gordon Pask Award for Contributions to Agile Practice. James is a featured speaker at conferences around the world. He may be found online at

Shane Warden manages Onyx Neon Press, an independent publisher. His areas of expertise include agile software development, language design, and virtual machines for dynamic languages. He is also a published novelist. His books include The Art of Agile Development and Masterminds of Programming.

Read More Show Less

Table of Contents

For the Pragmatists;
Who Should Read This Book;
About the Études;
About Pronouns;
Using Code Examples;
Safari® Enabled;
How to Contact Us;
Getting Started;
Chapter 1: Why Agile?;
1.1 Understanding Success;
1.2 Beyond Deadlines;
1.3 The Importance of Organizational Success;
1.4 Enter Agility;
Chapter 2: How to Be Agile;
2.1 Agile Methods;
2.2 Don’t Make Your Own Method;
2.3 The Road to Mastery;
2.4 Find a Mentor;
Chapter 3: Understanding XP;
3.1 The XP Lifecycle;
3.2 The XP Team;
3.3 XP Concepts;
Chapter 4: Adopting XP;
4.1 Is XP Right for Us?;
4.2 Go!;
4.3 Assess Your Agility;
Practicing XP;
Chapter 5: Thinking;
5.1 Pair Programming;
5.2 Energized Work;
5.3 Informative Workspace;
5.4 Root-Cause Analysis;
5.5 Retrospectives;
Chapter 6: Collaborating;
6.1 Trust;
6.2 Sit Together;
6.3 Real Customer Involvement;
6.4 Ubiquitous Language;
6.5 Stand-Up Meetings;
6.6 Coding Standards;
6.7 Iteration Demo;
6.8 Reporting;
Chapter 7: Releasing;
7.1 “Done Done”;
7.2 No Bugs;
7.3 Version Control;
7.4 Ten-Minute Build;
7.5 Continuous Integration;
7.6 Collective Code Ownership;
7.7 Documentation;
Chapter 8: Planning;
8.1 Vision;
8.2 Release Planning;
8.3 The Planning Game;
8.4 Risk Management;
8.5 Iteration Planning;
8.6 Slack;
8.7 Stories;
8.8 Estimating;
Chapter 9: Developing;
9.1 Incremental Requirements;
9.2 Customer Tests;
9.3 Test-Driven Development;
9.4 Refactoring;
9.5 Simple Design;
9.6 Incremental Design and Architecture;
9.7 Spike Solutions;
9.8 Performance Optimization;
9.9 Exploratory Testing;
Mastering Agility;
Chapter 10: Values and Principles;
10.1 Commonalities;
10.2 About Values, Principles, and Practices;
10.3 Further Reading;
Chapter 11: Improve the Process;
11.1 Understand Your Project;
11.2 Tune and Adapt;
11.3 Break the Rules;
Chapter 12: Rely on People;
12.1 Build Effective Relationships;
12.2 Let the Right People Do the Right Things;
12.3 Build the Process for the People;
Chapter 13: Eliminate Waste;
13.1 Work in Small, Reversible Steps;
13.2 Fail Fast;
13.3 Maximize Work Not Done;
13.4 Pursue Throughput;
Chapter 14: Deliver Value;
14.1 Exploit Your Agility;
14.2 Only Releasable Code Has Value;
14.3 Deliver Business Results;
14.4 Deliver Frequently;
Chapter 15: Seek Technical Excellence;
15.1 Software Doesn’t Exist;
15.2 Design Is for Understanding;
15.3 Design Trade-offs;
15.4 Quality with a Name;
15.5 Great Design;
15.6 Universal Design Principles;
15.7 Principles in Practice;
15.8 Pursue Mastery;
Read More Show Less

Customer Reviews

Average Rating 4.5
( 3 )
Rating Distribution

5 Star


4 Star


3 Star


2 Star


1 Star


Your Rating:

Your Name: Create a Pen Name or

Barnes & Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation


  • - By submitting a review, you grant to Barnes & and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Terms of Use.
  • - Barnes & reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously
Sort by: Showing all of 3 Customer Reviews
  • Posted February 24, 2009

    more from this reviewer


    The Art of Agile Development written by James Shore and Shane Warden is about managing a successful eXtreme Programming (XP) team. It reveals many possible ways of leading an agile team through a software project. The book is full of examples, explanations, tips and good practices.

    Great deal of issues covered in this book would make it hard to read but the authors made a tremendous work organizing the book's contents. There are cross-links between chapters and topics which help to find solutions to problems. Each topic has uniform structure consisting of subtopics, questions, results, contraindications, alternatives and further reading which helps a lot in finding answers and making decisions during an agile project. I was astonished how much information can be packed on only 400 pages. That is amazing.

    Parts I and II of this book contain author's approach to XP. Part I helps to get started with eXtreme Programming and Part II provides detailed guidance for each of XP's practices. Part III is full of ideas that can help to understand XP and agile development more deeply.

    I have read this book because I had heard that it is worth reading. I work as a software architect and project manager and I found this book very valuable. It is especially useful for anyone who is, will be or wants to be part of an agile team. This also includes programmers, domain experts, testers, project and product managers, designers and business analysts. It may also be handy for aware customers. If you have anything in common with agile development you should read this book.

    Was this review helpful? Yes  No   Report this review
  • Anonymous

    Posted December 22, 2007

    A reviewer

    This book is very well-timed. Now that agile development practices are 'crossing the chasm' towards professionally accepted standards, this book reminds us that 'agile' is neither a narrow, prescriptive set of standardized practices, nor a free-for-all smorgasbord of every possible practice. This book will give teams and their management the information necessary to make informed decisions about the make-up of a software product team, and how it operates. The Art of Agile Development is intelligent, thoughtful, professional, and realistic. It is based on years of varied experiences, and it reveals a well-tested set of recommendations. Part I The book starts out with high-altitude answers to 'Why?' and 'How?' and a satisfying definition of 'success.' This is followed by a story of a hypothetical XP team. The story is full of dialog revealing the day-to-day functioning of a well-running team as a new hire joins the team. That dialog may seem contrived, but it's likely more of a composite of things heard on various teams. Yes, agile teams do enjoy their work, and people who enjoy their work talk about it as portrayed. I think this portrayal brings forth an important decision for the reader: Do you suspect that your development teams could truly run more smoothly, or are you merely looking for a way to dismiss this weird new 'agile movement' and get on with your agonizing career? 'Either way, keep reading!' Part II The second section of the book is a detailed exploration of the development practices recommended by the authors. There are a number of practices recognizable from XP, with some additional thoughtful practices, some realistic alterations, and some notable replacements. As I said, this is neither a full buffet, nor is it a restrictive diet. This is a menu prepared by two experienced chefs. They talk about contraindications and alternatives for each practice, but they also warn of the pitfalls of removing key ingredients. Each chapter, or practice, comes with embedded boxes highlighting important points, and 'allies,' which are the names of other related 'and supporting' practices and their page numbers. These allies appear in little grey boxes in the margins. They give you the ability to use the book as a reference, but they also paint an important picture of how the practices fit together. I have to give special credit to the authors for the chapter they call simply 'Trust.' Under 'alternatives' they state rather clearly that there are none. No replacement for trust! It seems so obvious, and yet teams struggle every day because they don't have it. The authors, thankfully, provide suggestions for establishing lasting trust. Another noteworthy chapter is 'No Bugs.' If you're standing in the bookstore trying to decide whether or not to buy the book, turn to this chapter. These practices bring numerous others into focus. Again, if you're thinking 'pipe dream,' keep reading. If you follow this menu conscientiously and rigorously, you will arrive at the sweet dessert of extremely high-quality code. Part III Have you ever had a delicious meal at a friend's house, obtained the recipe, tried it for yourself, and thought 'Oh, that didn't turn out well!' What can you do? It takes experience 'and that means real time in the kitchen' before you can comfortably tweak a chef's recipe. You can also go back to your experienced friend and ask for advice or clarification. This book provides the same opportunity. Read Parts I and II, go try it for a while, then come back to Part III. This section describes the underlying values and principles behind the agile practices, and will help your new process and your team's existing culture work together towards greater and greater success. If a lot of the chapter titles in this section sound like Lean product-development principles, well, I think that's intentional. It is perhaps difficult to pinpoint what is truly 'agile.' This book represents true agility

    Was this review helpful? Yes  No   Report this review
  • Anonymous

    Posted June 10, 2011

    No text was provided for this review.

Sort by: Showing all of 3 Customer Reviews

If you find inappropriate content, please report it to Barnes & Noble
Why is this product inappropriate?
Comments (optional)