{"product_id":"domain-storytelling-9780137458912","title":"Domain Storytelling","description":"\u003cb\u003eBook Synopsis\u003c\/b\u003e\u003cbr\u003e\u003cb\u003eStefan Hofer\u003c\/b\u003e holds a PhD in computer science, and maintains \u003ca href=\"http:\/\/domainstorytelling.org\"\u003edomainstorytelling.org\u003c\/a\u003e, the home of the Domain Storytelling community. Since 2005, he has worked for WPS-Workplace Solutions, helping teams develop software that does the right job the right way. \u003cb\u003eHenning Schwentner\u003c\/b\u003e, programmer, coach, and consultant for WPS-Workplace Solutions, helps teams structure existing software and build new systems with more sustainable architectures. He wrote \u003ca href=\"http:\/\/LeasingNinja.io\"\u003eLeasingNinja.io\u003c\/a\u003e and translated \u003ci\u003eDomain-Driven Design Distilled\u003c\/i\u003e into German. \u003cbr\u003e\u003cbr\u003e\u003cbr\u003e\u003cb\u003eTrade Review\u003c\/b\u003e\u003cbr\u003e\"This book provides a wonderful introduction to an approachable, structured, narrative-based technique for collaborative domain modeling. And for those wanting to go deeper, Stefan and Henning will help you not only to avoid common facilitation pitfalls, but also to integrate the domain knowledge into your everyday development work.\" \u003cbr\u003e \u003ci\u003e--Paul Rayner, author of \u003c\/i\u003eThe EventStorming Handbook \u003cbr\u003e \u003cbr\u003e\"This book is destined to be the definitive resource on Domain Storytelling for many years.\" \u003cbr\u003e \u003ci\u003e--Mike Cohn, co-founder of the Agile Alliance\u003c\/i\u003e \u003cbr\u003e \u003cbr\u003e\"Until now, when people talk about visualization, they usually mean 'words in boxes on a whiteboard.' Representing the user's needs and journeys has been somewhat awkward, with either long form descriptions or series of wireframes. What Stefan and Henning have achieved is a method that shows what's really happening. A Domain Storytelling model shows who's doing what with whom, in what order, and for what purpose, in a clear, truly visual way. It's easy enough to learn how to build these models, but more importantly, an uninitiated reader can understand and critique the models at first sight. That makes Domain Storytelling a powerful communication tool that I believe will become widely used in software product companies and beyond.\" \u003cbr\u003e \u003ci\u003e--Mathias Verraes, curator of Domain-Driven Design Europe\u003c\/i\u003e \u003cbr\u003e \u003cbr\u003e\"This is a great addition to any Domain-Driven Design practitioner's bookshelf.\" \u003cbr\u003e \u003ci\u003e--Julie Lerman, software coach, The Data Farm\u003c\/i\u003e \u003cbr\u003e \u003cbr\u003e\"All organizations are being disrupted through the rapid advance of change, and my job is to teach people how to apply the Kanban method in their business life. In that context we use Domain Storytelling while exploring and extracting value streams in organizations in a very successful way. With their book, Stefan Hofer and Henning Schwentner explain how collaboration can and does lead the way to transforming our ways of working.\" \u003cbr\u003e \u003ci\u003e--Altuğ Bilgin Altıntaş, business agility engineer, accredited Kanban trainer \u0026amp; coach, author of\u003c\/i\u003e Kanban Metodu ile Çeviklik, \u003ci\u003eco-organizer of FlowConf\u003c\/i\u003e \u003cbr\u003e \u003cbr\u003e\"This book is a rare achievement, combining a pragmatic guide to a powerful domain modeling technique and a wealth of distilled insights from key aspects of Domain-Driven Design, without being a tome. The authors present a convincing case that conversational stories told and visualized in a natural language pave the fastest path to quality business software. Be prepared for fingers itching to start your own Domain Storytelling while reading the well-curated case studies.\" \u003cbr\u003e \u003ci\u003e--Xin Yao, chief software architect at Danske Bank\u003c\/i\u003e \u003cbr\u003e \u003cbr\u003e\"Practicing Domain Storytelling is a journey towards deep and true understanding of the problem domain you are working on. While discovering subtle inner workings of the business, be prepared for some unexpected solutions to reveal themselves along the way. This book will put you in a position to embark on that journey on your own and will guide you along the way.\" \u003cbr\u003e \u003ci\u003e--Mufrid Krilic, DDD and Domain Storytelling practitioner\u003c\/i\u003e \u003cbr\u003e \u003cbr\u003e\"Domain Storytelling served as a key bridge between our business, products, and technology stacks, and between our past to our future. Using the practice, everyone who participated—from P\u0026amp;L and Operations team leaders to individual engineers and product leads—levelled-up their understanding of where we intended (and needed) to take the business, aligned with each other, and understood how crossfunctional product and engineering teams would function within the relevant bounded contexts that collectively represented our future business model. And many (even most!) found it a fun and liberating process. \u003cbr\u003e \u003cbr\u003e\"Domain Storytelling is a practical methodology rooted in the language and context of customers and business, so accessible and valuable to cross-functions (not just engineering) within your business. I recommend the book and, more importantly, the methodology!\" \u003cbr\u003e \u003ci\u003e--Jim Banister, chief product officer, Raisin DS GmbH\u003c\/i\u003e \u003cbr\u003e \u003cbr\u003e\"As a product manager I really love visualization. Domain Storytelling was one of the techniques I met at the very beginning of my Domain-Driven Design journey (in 2017). I was impressed, amazed, and at the same time surprised in a very positive way that this is exactly what is needed by someone who facilitates the communication between development teams and business. It is very easy to learn and focuses on the pictographic language that makes it possible for literally everyone to understand and take advantage of. I would recommend using it immediately; don't think too much, just start and go with the flow! Believe me it will be worth it. :)\" \u003cbr\u003e \u003ci\u003e--Zsófia Herendi, product manager\u003c\/i\u003e\u003cbr\u003e\u003cbr\u003e\u003cb\u003eTable of Contents\u003c\/b\u003e\u003cbr\u003e\u003ci\u003eList of Domain Stories xv\u003cbr\u003eSeries Editor Foreword xvii\u003cbr\u003eForeword xxi\u003cbr\u003ePreface xxiii\u003cbr\u003eAcknowledgments xxxi\u003cbr\u003eAbout the Authors xxxiii\u003c\/i\u003e \u003cbr\u003e \u003cbr\u003e \u003cb\u003ePart I: Domain Storytelling Explained 1\u003cbr\u003e\u003cbr\u003eChapter 1: Introduction 3\u003c\/b\u003e \u003cbr\u003eWhat Is Domain Storytelling? 3 \u003cbr\u003eYour First Domain Story 5 \u003cbr\u003e \u003cbr\u003e \u003cb\u003eChapter 2: The Pictographic Language 15\u003c\/b\u003e \u003cbr\u003eActors 16 \u003cbr\u003eWork Objects 16 \u003cbr\u003eActivities 18 \u003cbr\u003eSequence Numbers 18 \u003cbr\u003eAnnotations 19 \u003cbr\u003eModeling Canvas 20 \u003cbr\u003eGroups 22 \u003cbr\u003eColors 24 \u003cbr\u003eNo Conditionals 25 \u003cbr\u003ePutting It All Together 26 \u003cbr\u003eA Grammar for Domain Stories 27 \u003cbr\u003eGood Language Style 31 \u003cbr\u003e \u003cbr\u003e \u003cb\u003eChapter 3: Scenario-Based Modeling 37\u003c\/b\u003e \u003cbr\u003eWhat Are Scenarios? 37 \u003cbr\u003eScenarios in Domain Storytelling 39 \u003cbr\u003eConcrete Examples as Scenarios 43 \u003cbr\u003eKeeping an Overview 43 \u003cbr\u003e \u003cbr\u003e \u003cb\u003eChapter 4: Scope 45\u003c\/b\u003e \u003cbr\u003eGranularity 45 \u003cbr\u003ePoint in Time (As-Is vs. To-Be) 48 \u003cbr\u003eDomain Purity (Pure vs. Digitalized) 49 \u003cbr\u003eCombining the Scope Factors: A Typical Journey 51 \u003cbr\u003e \u003cbr\u003e \u003cb\u003eChapter 5: Modeling Tools 55\u003c\/b\u003e \u003cbr\u003eModeling on Paper or Boards 55 \u003cbr\u003eModeling with Software Tools 60 \u003cbr\u003eChoosing a Tool 63 \u003cbr\u003e \u003cbr\u003e \u003cb\u003eChapter 6: The Workshop Format 67\u003c\/b\u003e \u003cbr\u003eBefore the Workshop 68 \u003cbr\u003eThe Workshop 72 \u003cbr\u003eAfter the Workshop 79 \u003cbr\u003eTo-Be Workshops 80 \u003cbr\u003eRemote Workshops 82 \u003cbr\u003eThe Moderator 83 \u003cbr\u003eThe Modeler as Separate Role 85 \u003cbr\u003eModerated Mode vs. Co-Op Mode 85 \u003cbr\u003e \u003cbr\u003e \u003cb\u003eChapter 7: Relationship to Other Modeling Methods 87\u003c\/b\u003e \u003cbr\u003eDomain-Driven Design 87 \u003cbr\u003eEventStorming 89 \u003cbr\u003eUser Story Mapping 91 \u003cbr\u003eExample Mapping 93 \u003cbr\u003eStorystorming 95 \u003cbr\u003eUse Cases 98 \u003cbr\u003eUML 99 \u003cbr\u003eBPMN 100 \u003cbr\u003eSummary 101 \u003cbr\u003e \u003cbr\u003e \u003cb\u003ePart II: Using and Adapting Domain Storytelling for Different Purposes 103\u003cbr\u003e\u003cbr\u003eChapter 8: Case Study--Alphorn Auto Leasing Inc. 105\u003c\/b\u003e \u003cbr\u003eExplore Alphorn--The Domain as a Whole 106 \u003cbr\u003eDrill Down into Risk Assessment--Understanding an Important Subdomain 108 \u003cbr\u003eClear Up Risk Assessment--Avoid Technical Jargon 109 \u003cbr\u003eOptimize Risk Assessment--The To-Be Process 111 \u003cbr\u003eIntroduce New Software--Combine Business Processes with IT Support 111 \u003cbr\u003eSummary 112 \u003cbr\u003e \u003cbr\u003e \u003cb\u003eChapter 9: Learning Domain Language 115\u003c\/b\u003e \u003cbr\u003eSpeaking and Listening to Understand Each Other 117 \u003cbr\u003eOrganizations Speak Many Domain Languages 122 \u003cbr\u003eUsing Natural Languages 124 \u003cbr\u003eLost in Translation 126 \u003cbr\u003eWhat to Read Next? 126 \u003cbr\u003e \u003cbr\u003e \u003cb\u003eChapter 10: Finding Boundaries 129\u003c\/b\u003e \u003cbr\u003eThe Joy of Multiple Models 131 \u003cbr\u003eA Heuristic for Finding Subdomains 132 \u003cbr\u003eFrom Subdomains to Bounded Contexts 138 \u003cbr\u003eFrom Context Boundaries to Team Boundaries 141 \u003cbr\u003eWhat to Read Next? 142 \u003cbr\u003e \u003cbr\u003e \u003cb\u003eChapter 11: Working with Requirements 145\u003c\/b\u003e \u003cbr\u003eSoftware Development as a Series of Conversations 148 \u003cbr\u003eFrom Domain Stories to Requirements 149 \u003cbr\u003eAdapt the Recipe 158 \u003cbr\u003eLimitations 158 \u003cbr\u003eWhat to Read Next? 159 \u003cbr\u003e \u003cbr\u003e \u003cb\u003eChapter 12: Modeling in Code 161\u003c\/b\u003e \u003cbr\u003eFrom Domain Stories to Domain Model 163 \u003cbr\u003eImplementing the Domain Model 170 \u003cbr\u003eWhat to Read Next? 179 \u003cbr\u003e \u003cbr\u003e \u003cb\u003eChapter 13: Supporting Organizational Change 181\u003c\/b\u003e \u003cbr\u003eChanging People's Workflows 183 \u003cbr\u003eDigitalizing Work 188 \u003cbr\u003eWhat to Read Next? 191 \u003cbr\u003e \u003cbr\u003e \u003cb\u003eChapter 14: Deciding Make or Buy and Choosing Off-the-Shelf Software 193\u003c\/b\u003e \u003cbr\u003eUnderstand the Processes of Off-the-Shelf Solutions 196 \u003cbr\u003eWhat to Read Next? 201 \u003cbr\u003e \u003cbr\u003e \u003cb\u003eChapter 15: Finding Shadow IT 203\u003c\/b\u003e \u003cbr\u003eNot Only Software Developers Develop Software 205 \u003cbr\u003eMaking Hidden Software Systems Visible 205 \u003cbr\u003eWhat to Read Next? 209 \u003cbr\u003e \u003cbr\u003e \u003cb\u003eChapter 16: Conclusion 211\u003c\/b\u003e \u003cbr\u003eThe Future of Domain Storytelling 211 \u003cbr\u003eThe Essence of Domain Storytelling 212 \u003cbr\u003e \u003cbr\u003e \u003cb\u003eAppendix: The History of Domain Storytelling 213\u003c\/b\u003e \u003cbr\u003e \u003cbr\u003e \u003ci\u003eGlossary 219\u003cbr\u003eBibliography 221\u003cbr\u003eIndex 229\u003c\/i\u003e","brand":"Pearson Education (US)","offers":[{"title":"Default Title","offer_id":49399842439511,"sku":"9780137458912","price":28.49,"currency_code":"GBP","in_stock":false}],"url":"https:\/\/bookcurl.com\/products\/domain-storytelling-9780137458912","provider":"Book Curl","version":"1.0","type":"link"}