Executable Specifications with Scrum: A Practical Guide to Agile Requirements Discovery (Paperback)
Mario Cardinal
- 出版商: Addison Wesley
- 出版日期: 2013-08-08
- 售價: $1,155
- 貴賓價: 9.5 折 $1,097
- 語言: 英文
- 頁數: 192
- 裝訂: Paperback
- ISBN: 0321784138
- ISBN-13: 9780321784131
-
相關分類:
Agile Software
立即出貨 (庫存=1)
買這商品的人也買了...
-
$1,230$1,169 -
$1,980$1,881 -
$650The Art of Agile Development (Paperback)
-
$620$527 -
$1,890$1,796 -
$590$502 -
$780$663 -
$520$411 -
$780$616 -
$580$452 -
$1,130$961 -
$400$380 -
$820$648 -
$940$700 -
$480$379 -
$680$537 -
$380$300 -
$680$537 -
$480$408 -
$620$484 -
$300$234 -
$400$316 -
$780$616 -
$80$76 -
$580$458
相關主題
商品描述
Most books about specifications still assume that requirements can be known up front and won’t change much during your project. In today’s “real world,” however, you must specify and build software in the face of high and continuing uncertainty. Scrum and other agile methods have evolved to reflect this reality. Now, there’s a complete guide to specifying software in agile environments when prerequisites are unclear, requirements are difficult to grasp, and anything about your project could change.
Long-time agile coach and enterprise architect Mario Cardinal shows how to create executable specifications and use them to test software behavior against requirements. Cardinal shows how to trawl requirements incrementally, step-by-step, using a vision-centric and emergent iterative practice that is designed for agility. Writing for analysts, architects, developers, and managers, Cardinal makes a strong case for the iterative discovery of requirements. Then, he moves from theory to practice, fully explaining the technical mechanisms and empirical techniques you need to gain full value from executable specifications.
You’ll learn to connect specifications with software under construction, link requirements to architecture, and automate requirements verification within the Scrum framework. Above all, Cardinal will help you solve the paramount challenge of software development: not only to solve the problem right, but also to solve the right problem.
You will learn how to
• Establish more effective agile roles for analysts and architects
• Integrate and simplify the best techniques from FIT, ATDD, and BDD
• Identify “core certainties” on which your project team should rely to ensure requirements discovery
• Manage uncertainty by discovering stakeholder desires through short feedback loops
• Specify as you go while writing small chunks of requirements
• Use storyboarding and paper prototyping to improve conversations with stakeholders
• Express stakeholder desires that are requirements with user stories
• Refine your user stories, and plan more effective Scrum sprints
• Confirm user stories by scripting behaviors with scenarios
• Transform scenarios into automated tests that easily confirm your software’s expected behavior as designs emerge and specifications evolve
• Ensure higher-quality software by specifying nonfunctional requirements
Long-time agile coach and enterprise architect Mario Cardinal shows how to create executable specifications and use them to test software behavior against requirements. Cardinal shows how to trawl requirements incrementally, step-by-step, using a vision-centric and emergent iterative practice that is designed for agility. Writing for analysts, architects, developers, and managers, Cardinal makes a strong case for the iterative discovery of requirements. Then, he moves from theory to practice, fully explaining the technical mechanisms and empirical techniques you need to gain full value from executable specifications.
You’ll learn to connect specifications with software under construction, link requirements to architecture, and automate requirements verification within the Scrum framework. Above all, Cardinal will help you solve the paramount challenge of software development: not only to solve the problem right, but also to solve the right problem.
You will learn how to
• Establish more effective agile roles for analysts and architects
• Integrate and simplify the best techniques from FIT, ATDD, and BDD
• Identify “core certainties” on which your project team should rely to ensure requirements discovery
• Manage uncertainty by discovering stakeholder desires through short feedback loops
• Specify as you go while writing small chunks of requirements
• Use storyboarding and paper prototyping to improve conversations with stakeholders
• Express stakeholder desires that are requirements with user stories
• Refine your user stories, and plan more effective Scrum sprints
• Confirm user stories by scripting behaviors with scenarios
• Transform scenarios into automated tests that easily confirm your software’s expected behavior as designs emerge and specifications evolve
• Ensure higher-quality software by specifying nonfunctional requirements
商品描述(中文翻譯)
大多數關於規格的書籍仍然假設需求可以事先確定,並且在項目進行期間不會有太多變化。然而,在今天的「現實世界」中,您必須在高度不確定性的情況下指定和建立軟體。Scrum和其他敏捷方法已經演變以反映這一現實。現在,有一本完整的指南,教您在需求不明確、難以理解且項目的任何內容都可能變化時,在敏捷環境中指定軟體。
長期從事敏捷教練和企業架構師的Mario Cardinal展示了如何創建可執行的規格並使用它們來測試軟體行為是否符合需求。Cardinal展示了如何以適應性為設計的願景中心和新興迭代實踐,逐步進行需求挖掘。Cardinal針對分析師、架構師、開發人員和經理寫作,強烈主張迭代發現需求。然後,他從理論轉向實踐,充分解釋了您需要從可執行的規格中獲得完整價值的技術機制和實證技術。
您將學習如何:
• 為分析師和架構師建立更有效的敏捷角色
• 整合並簡化FIT、ATDD和BDD的最佳技術
• 確定項目團隊應依賴的「核心確定性」,以確保需求發現
• 通過短期反饋循環發現利益相關者的期望
• 在撰寫小塊需求時進行規格
• 使用故事板和紙上原型改進與利益相關者的對話
• 以用戶故事的形式表達利益相關者的期望需求
• 進一步完善您的用戶故事,並計劃更有效的Scrum迭代
• 通過腳本化行為場景確認用戶故事
• 將場景轉化為自動化測試,以便在設計出現和規格演變時輕鬆確認軟體的預期行為
• 通過指定非功能性需求確保更高質量的軟體