People hate abrupt changes to the way they work.人民仇恨的突然变化，以他们的方式工作。 So changes have to be introduced, slowly but steadily.因此，更改都必须介绍，缓慢但稳定。 Same for introducing agile methodologies to customers.同时引入敏捷方法给客户。 As much as we would all like to believe that the case for agile development, XP in particular, is so strong that all we have to do is “educate” the customer, reality states otherwise.虽然我们大家都希望相信的情况敏捷开发， XP中，尤其是如此强大，所有我们要做的，是“教育”顾客，现实的国家，否则。 In my experience I have found some customers are very afraid to begin with and there isn’t enough time to convince him otherwise before you lose the deal.在我的经验，我发现有些客户是非常害怕，开始与有没有足够的时间说服他，否则之前，你将失去处理。
So what options do we have?那么，选择我们有没有？ Personally I provide a bridge between customers bduf, spec heavy system of thought and my programmers agile style of development.我个人提供一个客户之间的桥梁bduf ，规格沉重的系统的思路和我的程序员敏捷的风格发展。 I am the customer to them.我的客户给他们。 While I provide the specs , with some help, to the people who feel comfortable with documentation.虽然我提供的规格，与一些帮助，对人民谁感觉舒适与文件。 Once the project succeeds I credit it to the agile methodologies and slowly gain enough confidence of the customer to move to increasingly agile system, thereby reducing my role in the process.一旦项目成功i信贷向敏捷方法，慢慢获得足够的信心，客户移动到越来越多的敏捷系统，从而减少了，我的角色，在这个过程中。
Sounds simple?听起来很简单？ In practice it is often frustrating to act as bridge and be responsible for reams of documentation.在实践中，这是往往令人沮丧充当桥梁和负责的大量文件。 Hopefully there will be good tools soon enough to address this space.希望会有很好的工具，尽快不足以解决这个空间。