Extreme Programming Explored

I'm a big fan of eXtreme Programming. I've read XP Installed (the first XP book I read), XP Explained (the first XP book), and Planning XP. I must say I was a big disappointed in this book. Here's the problem: This book doesn't explain XP in enough detail to be useful as a first XP book. But at the same time it does try to explain XP concepts which are already known to anyone who's read one of the XP intro books (Installed or Explained), making it too basic for someone who's been using XP. That leaves this book some where in the middle, with a little bit of introductory material and a little bit of advanced material. I think it's a good second book on XP (read XP Installed first), but if you've been using XP (especially refactoring and test driven development) then this book isn't going to be very helpful for you. Also the book is pretty thin and quite expensive for the small amount of content it contains. In my opinion you'd be better off buying Fowler's Refactoring book and downloading the JUnit docs, and reading Jeffries' XP Installed.

You know what XP is, how to get it up and running, and how to plan projects using it. Now it's time to expand your use of Extreme Programming and learn the best practices of this popular discipline.

In Extreme Programming Explored, you can read about best practices as learned from the concrete experience of successful XP developers. Author and programmer Bill Wake provides answers to practical questions about XP implementation. Using hands-on examples--including code samples written in the Java programming language--this book demonstrates the day-to-day mechanics of working on an XP team and shows well-defined methods for carrying out a successful XP project.

The book is divided into three parts:

• Part 1, Programming--programming incrementally, test-first, and refactoring.
• Part 2, Team Practices--code ownership, integration, overtime, and pair programming; how XP approaches system architecture; and how a system metaphor shapes a common vision, a shared vocabulary, and the architecture.
• Part 3, Processes--how to write stories to plan a release; how to plan iterations; and the activities in a typical day for the customer, the programmer, and the manager of an XP project.

To demonstrate how an XP team uses frequent testing, you'll learn how to develop the core of a library search system by unit testing in small increments. To show how to make code ready for major design changes, the author teaches you how to refactor a Java program that generates a Web page. To see how a system metaphor influences the shape of a system, you'll learn about the effects of different metaphors on customer service and word processing applications. To show how customers and programmers participate in release planning, the book demonstrates writing and estimating stories, and shows how the customer plans a release.

0201733978B07052001

(Pearson Education) Guide for those who wish to learn XP programming and implementation skills. Uses practical examples, including code samples written in Java, to demonstrate the daily workings of an XP team. Begins with the basic programming, then moves into team practices, and finally covers the process of a successful XP project. Softcover. Computer software--Development. This book will be Addison-Wesley's sixth book on the emerging discipline of Extreme Programming. XP is quickly gaining acceptance and popularity because is a programmer-centric way to build software. Each of AW's books is designed to be simple and straightforward (approximately 200 pages) so that programmers can get up-to-speed and employ XP on their next project.