Extreme Programming Explained: Embrace Change (2nd Edition) (XP Series)


Binding : Paperback
ProductGroup : Book
Manufacturer : Addison-Wesley Professional
Label : Addison-Wesley Professional
Publisher : Addison-Wesley Professional
Studio : Addison-Wesley Professional
List Price: USD $37.99
Lowest Used Price: USD $18.50
Lowest New Price: USD $24.98
Price is accurate as of the date/time indicated. Prices and product availability are subject to change. Any price displayed on the Amazon website at the time of purchase will govern the sale of this product.
Features:
Product Description
"In this second edition of Extreme Programming Explained, Kent Beck organizes and presents five years' worth of experiences, growth, and change revolving around XP. If you are seriously interested in understanding how you and your team can start down the path of improvement with XP, you must read this book." --Francesco Cirillo, Chief Executive Officer, XPLabs S.R.L. "The first edition of this book told us what XP was--it changed the way many of us think about software development. This second edition takes it farther and gives us a lot more of the 'why' of XP, the motivations and the principles behind the practices. This is great stuff. Armed with the 'what' and the 'why,' we can now all set out to confidently work on the 'how': how to run our projects better, and how to get agile techniques adopted in our organizations." --Dave Thomas, The Pragmatic Programmers LLC "This book is dynamite! It was revolutionary when it first appeared a few years ago, and this new edition is equally profound.For those who insist on cookbook checklists, there's an excellent chapter on 'primary practices,' but I urge you to begin by truly contemplating the meaning of the opening sentence in the first chapter of Kent Beck's book: 'XP is about social change. ' You should do whatever it takes to ensure that every IT professional and every IT manager--all the way up to the CIO--has a copy of Extreme Programming Explained on his or her desk." --Ed Yourdon, author and consultant "XP is a powerful set of concepts for simplifying the process of software design, development, and testing. It is about minimalism and incrementalism, which are especially useful principles when tackling complex problems that require a balance of creativity and discipline." --Michael A. Cusumano, Professor, MIT Sloan School of Management, and author of The Business of Software"Extreme Programming Explained is the work of a talented and passionate craftsman. Kent Beck has brought together a compelling collection of ideas about programming and management that deserves your full attention. My only beef is that our profession has gotten to a point where such common-sense ideas are labeled 'extreme.'..."--Lou Mazzucchelli, Fellow, Cutter Business Technology Council"If your organization is ready for a change in the way it develops software, there's the slow incremental approach, fixing things one by one, or the fast track, jumping feet first into Extreme Programming. Do not be frightened by the name, it is not that extreme at all. It is mostly good old recipes and common sense, nicely integrated together, getting rid of all the fat that has accumulated over the years." --Philippe Kruchten, UBC, Vancouver, British Columbia"Sometimes revolutionaries get left behind as the movement they started takes on a life of its own. In this book, Kent Beck shows that he remains ahead of the curve, leading XP to its next level. Incorporating five years of feedback, this book takes a fresh look at what it takes to develop better software in less time and for less money. There are no silver bullets here, just a set of practical principles that, when used wisely, can lead to dramatic improvements in software development productivity."--Mary Poppendieck, author of Lean Software Development: An Agile Toolkit "Kent Beck has revised his classic book based on five more years of applying and teaching XP. He shows how the path to XP is both easy and hard: It can be started with fewer practices, and yet it challenges teams to go farther than ever." --William Wake, independent consultant "With new insights, wisdom from experience, and clearer explanations of the art of Extreme Programming, this edition of Beck's classic will help many realize the dream of outstanding software development. " --Joshua Kerievsky, author of Refactoring to Patterns and Founder, Industrial Logic, Inc."XP has changed the way our industry thinks about software development. Its brilliant simplicity, focused execution, and insistence on fact-based planning over speculation have set a new standard for software delivery." --David Trowbridge, Architect, Microsoft Corporation Accountability. Transparency. Responsibility. These are not words that are often applied to software development.In this completely revised introduction to Extreme Programming (XP), Kent Beck describes how to improve your software development by integrating these highly desirable concepts into your daily development process. The first edition of Extreme Programming Explained is a classic. It won awards for its then-radical ideas for improving small-team development, such as having developers write automated tests for their own code and having the whole team plan weekly. Much has changed in five years.This completely rewritten second edition expands the scope of XP to teams of any size by suggesting a program of continuous improvement based on: *Five core values consistent with excellence in software development *Eleven principles for putting those values into action *Thirteen primary and eleven corollary practices to help you push development past its current business and technical limitations Whether you have a small team that is already closely aligned with your customers or a large team in a gigantic or multinational organization, you will find in these pages a wealth of ideas to challenge, inspire, and encourage you and your team members to substantially improve your software development. You will discover how to: *Involve the whole team--XP style *Increase technical collaboration through pair programming and continuous integration *Reduce defects through developer testing *Align business and technical decisions through weekly and quarterly planning *Improve teamwork by setting up an informative, shared workspace You will also find many other concrete ideas for improvement, all based on a philosophy that emphasizes simultaneously increasing the humanity and effectiveness of software development. Every team can improve. Every team can begin improving today. Improvement is possible--beyond what we can currently imagine. Extreme Programming Explained, Second Edition, offers ideas to fuel your improvement for years to come.
Amazon.com Review
Kent Beck's eXtreme Programming eXplained provides an intriguing high-level overview of the author's Extreme Programming (XP) software development methodology. Written for IS managers, project leaders, or programmers, this guide provides a glimpse at the principles behind XP and its potential advantages for small- to mid-size software development teams.

The book intends to describe what XP is, its guiding principles, and how it works. Simply written, the book avoids case studies and concrete details in demonstrating the efficacy of XP. Instead, it demonstrates how XP relies on simplicity, unit testing, programming in pairs, communal ownership of code, and customer input on software to motivate code improvement during the development process. As the author notes, these principles are not new, but when they're combined their synergy fosters a new and arguably better way to build and maintain software. Throughout the book, the author presents and explains these principles, such as "rapid feedback" and "play to win," which form the basis of XP.

Generally speaking, XP changes the way programmers work. The book is good at delineating new roles for programmers and managers who Beck calls "coaches." The most striking characteristic of XP is that programmers work in pairs, and that testing is an intrinsic part of the coding process. In a later section, the author even shows where XP works and where it doesn't and offers suggestions for migrating teams and organizations over to the XP process.

In the afterword, the author recounts the experiences that led him to develop and refine XP, an insightful section that should inspire any organization to adopt XP. This book serves as a useful introduction to the philosophy and practice of XP for the manager or programmer who wants a potentially better way to build software. --Richard Dragan

Topics covered: Extreme Programming (XP) software methodology, principles, XP team roles, facilities design, testing, refactoring, the XP software lifecycle, and adopting XP.

Customer Reviews


Thorough Overview of Extreme Programming (XP) (2007-11-06)
"Extreme Programming Explained" offers a thorough and good overview of the Extreme Programming (XP) approach to software development.

This book covers the fundamentals of XP and describes some of the benefits of this approach to developing software. While this approach may not suit all developers, project managers or companies, this book offers an interesting overview of XP.


A must read for any developer (2007-09-23)
I believe the basis in software development for business is in this book.
You can have the technique, the skills, and the money, but you will need the human side for any agile way of working.
This is not the silver bullet, but you NEED to read this book.


Extreme Programming: The evolutionary approach! (2006-09-10)
I came across this book in the Bibliography section of Scott Berkun's "The art of Project Management".

First, the structure. Well, this book is under 200 pages. So when Beck talks about keeping what is essential, he is surely applying it while writing books.

Second, the content. The book takes the reader from understanding business risks associated with software development, to understanding the changing economics of software development & why XP can fit the demands of an ever changing business scenario. The book then establishes what XP is, what are its features, what are the activities, who are the X players & then links the roles, activities, & features together across each phase in a typical XP project. While Beck is persuasive about the usefulness of XP, he has also included a chapter at the end of the book which talks about projects where using XP may not be advisable. And yes, such a project is an outsourced development project.

XP presents many interesting features. Traveling light - or code & tests together being all you need - sounds like a dream; nano-releases - or doing a daily or hourly build so that at any time you have a full system working, no matter the completeness of desired functionality - , building a system story by story, & going back & revisiting scope ever so often are all features that can be immensely valuable to the business & to the project team.

As a result of all this, & more such practices, XP resembles to an extent Darwinian evolution in some ways. Trying many things & keeping what works, designing for today's needs & changing that with tomorrow's requirements tomorrow but not today can be seen as interesting commonalities between Darwinian evolution & XP!

Overall, I think the book is great introduction to XP. I'd have liked case studies as well to understand how well good theory fits general projects of any kind, but this book does not cite too many such projects. Nevertheless, pick it up if you want to understand what the XP evolution is all about.

S!


Nice intro to XP (2006-02-20)
This book is a good introduction to different aspects involved in extreme programming.

The author is the initial proponent of XP. First part of the book explains the present day software development realities(like deadlines etc) and the pitfalls that take place due to these time sensitive expectations. Author moves onto explain the necessity for XP and what are the basic guidelines of XP.

The author should be commened for covering where XP is impractical and should not be used. The book explains the life cycle of a XP project and different roles that are part of this radical process.

XP is not suitable for many present day organizations(due to age old approaches that are already implanted in the system); but should be considered for time sensitive deliverables. This book will definitely give a headsup on how to approach XP.

Small negative: The book takes too much time on what is wrong in other traditional approached to software development(for the size of the title:about 200 pages)


Become a Better Programmer (2005-11-12)
This is an excellent book, short, concise, and well-written. To derive the full benefit of the book, I recommend reading it three times.

The first time you should just try to grasp the concepts of XP and adapt your attitude to be willing to try XP on a real project. If you are a heavy-weight methodology old-timer, this might be a big step for you. Approach it with an open mind.

Only having read the book completely, should you attempt an XP project. That will prepare you for the second reading. Now you can begin to fully grasp the power of its concepts and their implementation. Reading the book retrospectively will shed new light on most of the books contents. Much of what was previously fuzzy or abstract will become lucid.

The third time through should be when you teach using XP. I found more benefit when teaching a formal course than when performing OJT, especially when training those who have more historically traditional development attitudes.
The reason Beck has experienced so much success with XP is because XP works. This book truly explains how to embrace change.

Product Information and Prices stored: January 7 , 2009, 14:24

Leave a Reply