Your Amazon Prime 30-day FREE trial includes:
| Delivery Options | ![]() |
Without Prime |
|---|---|---|
| Standard Delivery | FREE | From £2.99* |
| Premium Delivery | FREE | £3.95 |
| Same-Day Delivery (on eligible orders over £20 to selected postcodes) Details | FREE | £5.99 |
Unlimited Premium Delivery is available to Amazon Prime members. To join, select "Yes, I want a free trial with FREE Premium Delivery on this order." above the Add to Basket button and confirm your Amazon Prime free trial sign-up.
Important: Your credit card will NOT be charged when you start your free trial or if you cancel during the trial period. If you're happy with Amazon Prime, do nothing. At the end of the free trial, you will be charged £95/year for Prime (annual) membership or £8.99/month for Prime (monthly) membership.
Buy new:
£27.99£27.99
FREE delivery:
Saturday, Jan 13
in the UK
Dispatches from: Amazon Sold by: Amazon
Buy used £21.64
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.
Follow the Authors
OK
Extreme Programming Explained: Embrace Change Paperback – Illustrated, 16 Nov. 2004
Purchase options and add-ons
― 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
From the Back Cover
― 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 F
About the Author
Kent Beck consistently challenges software engineering dogma, promoting ideas like patterns, test-driven development, and Extreme Programming. Currently affiliated with Three Rivers Institute and Agitar Software, he is the author of many Addison-Wesley titles.
Cynthia Andres holds a B.S. in psychology with advanced work in organizational behavior, decision analysis, and women’s studies. She has worked with Kent on the social aspects of Extreme Programming since its inception. She is also affiliated with Three Rivers Institute.
0
- ISBN-109780321278654
- ISBN-13978-0321278654
- Edition2nd
- PublisherAddison-Wesley Professional
- Publication date16 Nov. 2004
- LanguageEnglish
- Dimensions18.67 x 2.03 x 23.5 cm
- Print length216 pages
Frequently bought together

What do customers buy after viewing this item?
From the brand
-
Addison-Wesley is a premiere publisher of books and eBooks for those working with technology.
This includes resources for programmers, developers, administrators, data scientists and engineers, team managers, students, and more.
-
Who are our authors?
Our authors are the creators, innovators, and thought leaders in computer science and technology including Donald Knuth, Bjarne Stroustrup, Brendan Gregg, Martin Fowler, Robert C. Martin.
Are our books for professionals only?
Our catalogue includes tutorials, references, guides, and deep dives for all levels, including never haven written a line of code to being in the industry for 40+ years and wanting to upskill.
Why Choose Addison Wesley?
We have been publishing the leading texts on computer science for decades and our titles appear on numerous "most recommended" lists.
-
-
Signature Series
Books in the series are personally chosen by expert advisors who are proud to put their signatures on the covers.
-
Professional Computing Series
Brian W. Kernighan created this series to provide serious programmers & networking professionals with practical reference books.
-
Professional Scrum Series
Deep insights into overcoming the challenges that both teams and organizations face as they seek to reap the benefits of agility.
-
Robert C. Martin Series
For software developers, team-leaders, business analysts & managers who want to increase their skill to the level of a Master Craftsman
-
Data & Analytics Series
Practical knowledge for solving problems & answering questions with data with a focus on infrastructure, algorithms and visualization.
-
The C++ In-Depth Series
Bjarne Stroustrup designer of C++ selected this collection to provide programmers with reliable information on C++ programming language
Product details
- ASIN : 0321278658
- Publisher : Addison-Wesley Professional; 2nd edition (16 Nov. 2004)
- Language : English
- Paperback : 216 pages
- ISBN-10 : 9780321278654
- ISBN-13 : 978-0321278654
- Dimensions : 18.67 x 2.03 x 23.5 cm
- Best Sellers Rank: 114,604 in Books (See Top 100 in Books)
- 79 in Amazon Online Shopping
- 103 in Operational Productivity
- 144 in Functional Programming
- Customer reviews:
About the authors

Discover more of the author’s books, see similar authors, read author blogs and more

Kent Beck is the founder and director of Three Rivers Institute (TRI). His career has combined the practice of software development with reflection, innovation, and communication. His contributions to software development include patterns for software, the rediscovery of test-first programming, the xUnit family of developer testing tools, and Extreme Programming. He currently divides his time between writing, programming, and coaching. Beck is the author/co-author of Implementation Patterns, Extreme Programming Explained: Embrace Change 2nd Edition, Contributing to Eclipse, Test-Driven Development: By Example, Planning Extreme Programming, Smalltalk Best Practice Patterns, and the JUnit Pocket Guide. He received his B.S. and M.S. in Computer Science from the University of Oregon.
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 analyses reviews to verify trustworthiness.
Learn more how customers reviews work on Amazon-
Top reviews
Top reviews from United Kingdom
There was a problem filtering reviews right now. Please try again later.
The first edition of this book marked a watershed in the way I thought about software. I did leave many questions unanswered, however, as our team struggled to implement the practices 'out of the box'. Perhaps a bit too much revolutionary zeal.
The breadth of the second edition is far greater. It explains the principles so that you can adapt them to your own circumstances, without subverting their original intent. As such it is a far more usefull book than the first edition, even if it lacks the bold audacity of the former - or maybe the ideas of XP dont seem so left of field anymore.
The first edition of the book was published in 1999. Although iterative methodologies were being used at that time, the waterfall process was predominantly used. Although Royce does in fact describe a partially-iterative approach, most implementations were strictly waterfall in application: the phases of requirements specification, design, construction, integration, testing, installation, and maintenance were each executed, then frozen and signed-off in strict order.
At the same time, software-development toolsets were becoming more powerful. In addition, some programming languages, such as Smalltalk and Java, where becoming flexible enough to model real-world problems and to generate and deploy code from these models. This ability to generate software rapidly, and to elicit feedback quickly from the end-customer, allowed software developers to:
* Iterate the waterfall process many times in one project by implementing a software system incrementally;
* Be able to deal with requirements that change as a response to business change rather than having them frozen at the beginning of the project.
This approach, along with other features, coalesced into XP. XP has a number of features in common in with other software-development methodologies and a few unique ones. The common features are that projects are iterative, ie they repeat the same activities in a cyclical fashion, incrementally deploying the system at the end of each iteration, resulting in rapid feedback of any issues. It puts emphasis on intense communication between end-customers and developers.
The features that are unique to XP are:
* a simple documentation set, especially for requirements and design - the key artefacts are automated tests and code.
* visible artefacts on public display in the work environment, so that newcomers can see the status of the project in a few seconds. This is an idea derived from Lean process of business improvement.
* pair programming, where two developers sit at the same workstation and work on the same code. The idea is to lower the number of defects without having a lengthy, off-line code review.
* to aim to develop the simplest thing that could work.
The projects to which XP is best suited have the following characteristics:
* highly uncertain or rapidly-changing requirements;
* having lower formality - for example less likely to be of a mission-critical nature and less likely to have a high systems-engineering element;
* a high degree of human-computer interaction (GUIs), rather than, say, a real-time messaging system;
* the stakeholders (especially the developers) have experience of, or are willing to support, highly-collaborative methods of working;
* having a contract that supports iterative working and promotes customer-supplier collaboration.
XP has been subjected to a number of criticisms - some more justified than others.
The most common criticism is that it encourages "hacker" indiscipline. This would certainly be justified if XP's other practices were not followed. However, the practices of pair-programming, the emphasis on testing and limiting the hours of the working week seem far-removed from the work of a lone hacker.
However, another criticism - that pair programming (mandated by XP) is not suited to all developers - has more credence. The statement that those who do not wish pair are shown the door may not be workable (or desirable) in some environments.
Another criticism is that system design is ignored. Certainly, the first edition or the book downplayed system design. The new edition states more clearly the importance of design but that it should be as lightweight as possible. For this to work efficiently, the team needs to be seeded with a number of experienced XP practitioners.
Another criticism is that XP is silent over how projects interface with other corporate planning activities such as corporate reporting and programme management. This is a valid criticism but links can be made to recognised governance frameworks such as (PRINCE2), either directly, or via other practices such as DSDM or Scrum.
So why did this book create such a stir when it first published in 1999? Several other iterative methodologies where in use before this date: Evo (60s); Spiral model (80s); RAD, DSDM, Scrum, RUP, ICONIX (all early- to mid-90s).
Several factors contributed to XP's notoriety. It had a polemical tone; it was a developer-led call-to-arms against a perceived bureaucracy. This was felt to prevent direct contact between developers and end-customers and lead to a lack of rapid feedback, leading to frustration in both camps. In addition, some non-XP practitioners became irritated at the publicity XP received. These people re-stated the (sometimes-justified) criticisms - which of course led to more publicity for XP.
The strident tone has been smoothed in the second edition: a more reflective and holistic view is evidenced. However, the practices seem as radical as ever, for example, the suggestion of making incremental software changes to live system on a daily basis.
Even in its second edition, Extreme Programming Explain remains a powerful and controversial read. Essential for all software and systems engineers - even if only to find out what all the fuss is about.
Would recommend it to anyone.
This book is not for me or any developer. Kent Beck is introducing the concepts of XP to the audience. In my case, the book is trying to preach the converted. I was looking for advice on HOW to implement the Extreme programming concepts. Instead i got a slight overview of WHAT XP is.
If you know nothing about XP, buy this book.
If you know about XP and want advice on HOW to implement XP. DO NOT buy this book.













