Extreme Programming Explored
暫譯: 極限編程探討

William C. Wake

  • 出版商: Addison Wesley
  • 出版日期: 2001-07-28
  • 售價: $1,190
  • 貴賓價: 9.5$1,131
  • 語言: 英文
  • 頁數: 192
  • 裝訂: Paperback
  • ISBN: 0201733978
  • ISBN-13: 9780201733976
  • 相關分類: Agile Software
  • 立即出貨(限量) (庫存=1)

買這商品的人也買了...

商品描述

 

Description

 



Back to Top


Appropriate Courses



Back to Top

 

Features

  •  

Back to Top

 

Table Of Contents

 

Forward.
Preface.

 

Acknowledgments.


Introduction.

 

 

 

I. PROGRAMMING.

 

 

 

1. How Do You Write a Program?

 

Program Incrementally and Test First.


2. What is Refactoring?

 

“Refactoring: Improving the Design of Existing Code.” —Martin Fowler.
 

II. TEAM PRACTICES.

 

 


3. What Are XP's Team Practices?

 

 

“We'll Explore These Practices and Their Alternatives.”


4. What is it Like to Program in Pairs?

 

 

Pair Programming is Exhausting but Productive.


5. Where's the Architecture?

 

 

Architecture Shows Up in Spikes, the Metaphor, the First Iteration, and Elsewhere.


6. What is the System Metaphor?

 

 

“The System Metaphor is a Story that Everyone—Customers, Programmers, and Managers—Can Tell About How the System Works,” —Kent Beck.
 

III. PROCESS.

 

 


7. How Do You Plan a Release? What are Stories Like?

 

 

Write, Estimate, and Prioritize Stories.


8. How Do You Plan an Iteration?

 

 

Iteration Planning Can be Thought of as a Board Game.


9. Customer, Programmer, Manager: What is a Typical Day?

 

 

Customer: questions, tests, and steering.
Programmer: testing, coding, and refactoring.
Manager: Project Manager, Tracker, and Coach.


10. Conclusion.
Bibliography.
Index.


Back to Top

 

 

商品描述(中文翻譯)

描述

適合的課程

特點

目錄

前言
致謝
介紹

I. 程式設計

1. 如何撰寫程式?

逐步編寫程式並優先測試。

2. 什麼是重構?

“重構:改善現有程式碼的設計。” — Martin Fowler

II. 團隊實踐

3. XP 的團隊實踐是什麼?

“我們將探索這些實踐及其替代方案。”

4. 成對編程是什麼樣的體驗?

成對編程雖然耗費精力,但卻富有成效。

5. 架構在哪裡?

架構在尖峰、隱喻、第一次迭代及其他地方顯現。

6. 什麼是系統隱喻?

“系統隱喻是一個每個人——客戶、程式設計師和管理者——都能講述的關於系統如何運作的故事。” — Kent Beck

III. 流程

7. 如何計劃一次發佈?故事是什麼樣的?

撰寫、估算並優先排序故事。

8. 如何計劃一次迭代?

迭代計劃可以被視為一種桌上遊戲。

9. 客戶、程式設計師、管理者:典型的一天是什麼樣的?

客戶:提問、測試和指導。
程式設計師:測試、編碼和重構。
管理者:專案經理、追蹤者和教練。

10. 結論。
參考文獻。
索引。