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.希望會有很好的工具，盡快不足以解決這個空間。