The Art of Agile Development (Paperback)
暫譯: 敏捷開發的藝術 (平裝本)
James Shore, Shane Warden
- 出版商: O'Reilly
- 出版日期: 2007-10-01
- 定價: $1,300
- 售價: 2.3 折 $299
- 語言: 英文
- 頁數: 440
- 裝訂: Paperback
- ISBN: 0596527675
- ISBN-13: 9780596527679
-
相關分類:
Agile Software
-
其他版本:
The Art of Agile Development, 2/e (Paperback)
買這商品的人也買了...
-
$520$416 -
$1,270$1,207 -
$880$695 -
$780$663 -
$980$774 -
$1,045Introduction to Logic and Computer Design (IE-Paperback)
-
$780$663 -
$720$612 -
$580$493 -
$1,980$1,881 -
$450$351 -
$600$510 -
$350$298 -
$1,560$1,326 -
$990$891 -
$600$480 -
$1,872Continuous Integration: Improving Software Quality and Reducing Risk (Paperback)
-
$650$553 -
$2,400$2,280 -
$380$300 -
$780$663 -
$680$530 -
$490$387 -
$1,200$1,020 -
$1,890$1,796
相關主題
商品描述
Description
The Art of Agile Development contains practical guidance for anyone considering or applying agile development for building valuable software. Plenty of books describe what agile development is or why it helps software projects succeed, but very few combine information for developers, managers, testers, and customers into a single package that they can apply directly.
This book provides no-nonsense advice on agile planning, development, delivery, and management taken from the authors' many years of experience with Extreme Programming (XP). You get a gestalt view of the agile development process, including comprehensive guidance for non-technical readers and hands-on technical practices for developers and testers.
The Art of Agile Development gives you clear answers to questions such as:The book teaches you how to adopt XP practices, describes each practice in detail, then discusses principles that will allow you to modify XP and create your own agile method. In particular, this book tackles the difficult aspects of agile development: the need for cooperation and trust among team members.
- How can we adopt agile development?
- Do we really need to pair program?
- What metrics should we report?
- What if I can't get my customer to participate?
- How much documentation should we write?
- When do we design and architect?
- As a non-developer, how should I work with my agile team?
- Where is my product roadmap?
- How does QA fit in?
Whether you're currently part of an agile team, working with an agile team, or interested in agile development, this book provides the practical tips you need to start practicing agile development. As your experience grows, the book will grow with you, providing exercises and information that will teach you first to understand the rules of agile development, break them, and ultimately abandon rules altogether as you master the art of agile development.
"Jim Shore and Shane Warden expertly explain the practices and benefits of Extreme Programming. They offer advice from their real-world experiences in leading teams. They answer questions about the practices and show contraindications - ways that a practice may be mis-applied. They offer alternatives you can try if there are impediments to applying a practice, such as the lack of an on-site customer.
--Ken Pugh, Author of Jolt Award Winner, Prefactoring
"I will leave a copy of this book with every team I visit."
--Brian Marick, Exampler Consulting
商品描述(中文翻譯)
**描述**
《敏捷開發的藝術》提供了對於任何考慮或應用敏捷開發以構建有價值軟體的人的實用指導。許多書籍描述了敏捷開發是什麼或為什麼它有助於軟體專案的成功,但很少有書籍將開發人員、管理者、測試人員和客戶的信息整合成一個可以直接應用的單一包裝。
本書提供了關於敏捷規劃、開發、交付和管理的實用建議,這些建議來自於作者多年來在極限編程(Extreme Programming, XP)方面的經驗。您將獲得敏捷開發過程的整體視圖,包括針對非技術讀者的全面指導以及針對開發人員和測試人員的實用技術實踐。
《敏捷開發的藝術》為您提供了對以下問題的清晰答案:
- 我們如何採用敏捷開發?
- 我們真的需要配對編程嗎?
- 我們應該報告哪些指標?
- 如果我無法讓我的客戶參與,該怎麼辦?
- 我們應該寫多少文檔?
- 我們何時進行設計和架構?
- 作為非開發人員,我應該如何與我的敏捷團隊合作?
- 我的產品路線圖在哪裡?
- 品質保證(QA)如何融入其中?
本書教您如何採用XP實踐,詳細描述每個實踐,然後討論允許您修改XP並創建自己的敏捷方法的原則。特別是,本書處理了敏捷開發中的困難方面:團隊成員之間的合作與信任的需求。
無論您目前是否是敏捷團隊的一部分,或是與敏捷團隊合作,或是對敏捷開發感興趣,本書提供了您開始實踐敏捷開發所需的實用建議。隨著您的經驗增長,本書將與您共同成長,提供練習和信息,教您首先理解敏捷開發的規則,然後打破這些規則,最終在掌握敏捷開發的藝術時完全放棄規則。
“Jim Shore和Shane Warden專業地解釋了極限編程的實踐和好處。他們提供了來自於領導團隊的真實經驗的建議。他們回答了有關實踐的問題,並展示了不當應用的情況——即實踐可能被錯誤應用的方式。他們提供了如果在應用實踐時遇到障礙(例如缺乏現場客戶)可以嘗試的替代方案。”
-- Ken Pugh,《Jolt Award》獲獎作品《Prefactoring》的作者
“我會將這本書的副本留給我訪問的每個團隊。”
-- Brian Marick,Exampler Consulting