解析极限编程——拥抱变化（第二版）（中英文对照） (2008 年度畅销榜NO.735 )

这的确是一本好书，无论你是一个已经和客户紧密联系在一起的小团队，还是有一个在大组织或跨国组织中的大团队，你都会在其中发现如下的思想去挑战、启发和鼓励你的团队成员去切实改进你们的软件开发：

一本很一般的书，如果时间不多的话就别在那上面浪费时间了，内容不实用。

为什么这里显示有货，但转到当当网就没货了呢？

使用XP对业务和软件开发有多大帮助呢,学习一下,了解一下

影响整个团队——XP风格
通过结对编程和持续集成来增加技术协作
通过开发人员的测试减少缺陷
通过每周和每季度计划校准业务和技术决策
通过建立富有信息的共享工作空间来改进团队协作

这的确是一本好书，无论你是一个已经和客户紧密联系在一起的小团队，还是有一个在大组织或跨国组织中的大团队，你都会在其中发现如下的思想去挑战、启发和鼓励你的团队成员去切实改进你们的软件开发：

原书链接：
http://www.amazon.com/gp/product/0321278658/qid=1149836942/sr=11-1/ref=sr_11_1/002-3067279-0520004?n=283155

原书评内容：
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.

翻译书评：

这是一本优秀的书，篇幅不大，文笔简练，写得很不错。要想从本书中获取最多的知识，我建议读它三遍。

第一遍你应该尽力去领会极限编程的概念，尽量培养在实际项目中尝试极限编程的兴趣。如果你已经应用重量级开发方法很长时间的话，这可能是比较艰难的过程。以开放的心态
来看待和接受它。

你应该在把这本书全部看一遍之后再开始尝试极限编程项目。因为那是后续过程的准备工作。现在你可以开始领会极限编程概念和实施过程的威力。不时回头翻一翻这本书，你会对书中的概念有新的理解，许多以前模糊抽象的概念可能就变得清晰而具体了。

第三遍应该是在你传授极限编程开发方法的时候。比较实施极限开发过程而言，我在讲述相关课程的时候获益更多，尤其是给那些有传统开发方法背景的人讲课。

Beck在极限编程方面如此成功的原因就是因为极限编程确实有用。这本书真正在解释如何拥抱变化。

原书链接：
http://www.amazon.com/gp/product/0321278658/qid=1149836942/sr=11-1/ref=sr_11_1/002-3067279-0520004?n=283155

原书评内容：
I came across this book in the Bibliography section of Scott Berkuns "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 todays needs & changing that with tomorrows 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. Id 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.

翻译书评：
我是在Scott Berkun的《项目管理艺术》(《The art of Project Management》)一书的参考书目部分中发现这本书的。

首先说书的结构。这本书不足200页。Beck说他只谈本质，他在写书的时候也确实紧扣这一点。

再谈谈书的内容。该书将读者从理解软件开发相关的业务风险的角度，转为理解软件开发中变化的业务需求，以及为什么XP能够适应不断变化的业务应用环境。继而通过一个典型的XP项目中的各个阶段来描述XP的定义，其特征，行为，人员，人员和角色、行为、特征间的联系。尽管Beck是想让人们认识到XP的作用，但是在书的结尾部分，他还是用一章的内容来说明那些不建议用XP的情况，比如外包开发项目。

XP有许多有趣的特征。交通灯－或者说代码与测试，就是你所有你需要的东西－听起来象说梦话。极小交付－或者每日甚至每小时编译，这样的话，你总是有一个可以运行的完整系统，当然，期望功能还不一定完成了。一个用户功能完成之后再开始下一个用户功能；回顾代码等等，这些特性对业务和对项目团队来说都是及其宝贵的。

所有这些XP特性以及相关的实践，让XP在某种程度上与达尔文的进化论有点类似。尝试解决一些问题；保持系统的可运行状态；今天只设计今天的需求，对于明天的需求，只要今天还不需要，就不要做设计；这些都是达尔文的进化论和XP的相似之处。

总而言之，我觉得这本书对XP有很好的介绍。我个人更喜欢学习实例，以及理解好理论如何与一般的项目结合，可惜这本书并没有引用很多这样的项目实例。不过，如果你想要理解XP革命到底是什么的话，你可以读一下这本书。

原书链接：
http://www.amazon.com/gp/product/0321278658/qid=1149836942/sr=11-1/ref=sr_11_1/002-3067279-0520004?n=283155

原书评内容：
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)


翻译书评:
《对XP介绍得不错》
这本书对极限编程涉及的不同方面有很不错的介绍。
本书的作者是XP的最初提出者。书中第一章介绍了当前软件开发的现实情况（比如最后期限等）以及这些时间方面相关期望所引起的缺陷。然后作者介绍了XP的必要性和XP的基本准则。
接着作者着手介绍不适合、不应使用XP的情况。书中介绍了XP项目的生命周期，以及在此激进过程中的各个不同的角色。
对当前的许多组织，XP并不适合（由于老的方法已经在系统中得以广泛应用）；但是对于交付时间紧迫的项目，XP值得考虑。这本书一定会为如何实践XP引发广泛讨论。
小小的缺点：这本书花费太多时间在其他传统的软件开发方法上了（200页）

5555555555555555555,刚要下单，竟然说缺货