Specification by Example
Summary Specification by Example is an emerging practice for creating software based on realistic examples, bridging the communication gap between business stakeholders and the dev teams building the software. In this book, author Gojko Adzic distills interviews with successful teams worldwide, sharing how they specify, develop, and deliver software, without defects, in short i...
Summary Specification by Example is an emerging practice for creating software based on realistic examples, bridging the communication gap between business stakeholders and the dev teams building the software. In this book, author Gojko Adzic distills interviews with successful teams worldwide, sharing how they specify, develop, and deliver software, without defects, in short iterative delivery cycles.About the Technology Specification by Example is a collaborative method for specifying requirements and tests. Seven patterns, fully explored in this book, are key to making the method effective. The method has four main benefits: it produces living, reliable documentation; it defines expectations clearly and makes validation efficient; it reduces rework; and, above all, it assures delivery teams and business stakeholders that the software that's built is right for its purpose.About the Book This book distills from the experience of leading teams worldwide effective ways to specify, test, and deliver software in short, iterative delivery cycles. Case studies in this book range from small web startups to large financial institutions, working in many processes including XP, Scrum, and Kanban. This book is written for developers, testers, analysts, and business people working together to build great software. Purchase of the print book comes with an offer of a free PDF, ePub, and Kindle eBook from Manning. Also available is all code from the book.What's InsideCommon process patternsHow to avoid bad practicesFitting SBE in your process50+ case studies For additional resources go to specificationbyexample.com. ===============================================Table of ContentsPart 1 Getting startedKey benefitsKey process patternsLiving documentationInitiating the changesPart 2 Key process patternsDeriving scope from goalsSpecifying collaborativelyIllustrating using examplesRefining the specificationAutomating validation without changing specificationsValidating frequentlyEvolving a documentation systemPart 3 Case studiesuSwitchRainStorIowa Student LoanSabre Airline SolutionsePlan ServicesSongkickConcluding thoughts
Gojko Adzic
戰(zhàn)略軟件交付顧問，專注于敏捷和精益開發(fā)，尤其擅長敏捷測試、實例化需求和行為驅(qū)動開發(fā)。Gojko經(jīng)常在國際上重要的軟件開發(fā)和測試會議上發(fā)言，并運營著英國的敏捷測試用戶小組。最近這十多年來，他一直在財務(wù)和能源交易平臺、移動定位、電子商務(wù)、在線游戲和復(fù)雜配置管理系統(tǒng)等行業(yè)項目中，從事程序員、架構(gòu)師、技術(shù)指導(dǎo)和顧問等工作。除本書外，他還著有Bridging the Communication Gap、Test Driven.Net Development with FitNesse和The Secret Ninja Cucumber Scrolls等書。
張昌貴 (Steven Zhang)
軟件開發(fā)經(jīng)理，CSM, CSPO, CSP，敏捷軟件開發(fā)參與者，軟件開源運動擁護者。
張博超（Jackson Zhang）
軟件開發(fā)工程師，CS...
Gojko Adzic
戰(zhàn)略軟件交付顧問，專注于敏捷和精益開發(fā)，尤其擅長敏捷測試、實例化需求和行為驅(qū)動開發(fā)。Gojko經(jīng)常在國際上重要的軟件開發(fā)和測試會議上發(fā)言，并運營著英國的敏捷測試用戶小組。最近這十多年來，他一直在財務(wù)和能源交易平臺、移動定位、電子商務(wù)、在線游戲和復(fù)雜配置管理系統(tǒng)等行業(yè)項目中，從事程序員、架構(gòu)師、技術(shù)指導(dǎo)和顧問等工作。除本書外，他還著有Bridging the Communication Gap、Test Driven.Net Development with FitNesse和The Secret Ninja Cucumber Scrolls等書。
張昌貴 (Steven Zhang)
軟件開發(fā)經(jīng)理，CSM, CSPO, CSP，敏捷軟件開發(fā)參與者，軟件開源運動擁護者。
張博超（Jackson Zhang）
軟件開發(fā)工程師，CSM, CSPO, CSP。關(guān)注敏捷開發(fā)，積極實踐并推廣各種敏捷方法。個人博客：iagile.me/blog
石永超（Stone Shi）
軟件開發(fā)工程師，CSM，CSPO，敏捷愛好者，InfoQ中文站編輯。關(guān)注高效、高質(zhì)量的軟件開發(fā)方法。