Hjem

Series Editor Foreword xv Foreword xix Preface xxi Acknowledgments xxix About the Author xxxi
Part I: The Concepts & Fundamentals 1
Chapter 1: Business Strategy with Wardley Mapping 3 The Strategy Cycle 4 The Purpose: The "Why" of Business 6 Visual Representation of the Landscape: The Wardley Map 7 Assessing Efficiency Gaps 19 Understanding Climatic Patterns 20 Applying Doctrinal Principles 29 Deciding on Strategic Actions (Leadership and Gameplay) 35 Summary 37
Chapter 2: Exploring the Problem Space with Strategic Domain-Driven Design and Wardley Mapping 39 Obtaining Domain Knowledge Through Collaboration 39 Domain-Driven Design Patterns and Practices 40 Discovering Subdomains and Mapping Their Evolution Stages 42 Build-or-Buy Decisions with Subdomain Types and Evolution Stages 48 Summary 50
Chapter 3: Designing the Solution Space with Strategic Domain-Driven Design 53 What Are Domain Models and Bounded Contexts? 53 Designing Domain Models and Bounded Contexts 56 Overview of Modeling Techniques 59 Bounded Contexts and Architecture Styles 66 Bounded Contexts and Evolution Stages 69 Strategic Design and Doctrine of Wardley Mapping 71 High Cohesion and Loose Coupling 72 Overview of Context Maps 74 Making Implicit Dependencies Explicit with Context Maps 80 Assessing Change Coupling When Integrating with the Core 81 Context Maps for the Conference Event Planner Example 84 Technical Communication Styles and Context Maps 85 Summary 86
Chapter 4: Implementing the Domain Model with Tactical Domain-Driven Design 89 The Building Blocks of Domain-Driven Models 89 The Ports and Adapters Architecture and Tactical Design 90 Summary 98
Chapter 5: Optimizing for Flow of Change with Team Topologies 101 System Impacts Identified by Conway''s Law 101 Challenges with Functional Silo Teams 101 Requirements for Flow Optimization from a Team Perspective 103 Impact on Software Delivery Performance 104 Team Cognitive Load and Mental Workload 105 The Fundamental Team Topologies 106 Team Interaction Modes 108 Common Interactions Between Team Types 109 Team Topologies Applying Doctrinal Principles of Wardley Mapping 110 Summary 111
Part II: Architecture for Flow 113
Chapter 6 Connecting the Dots 115 Identifying Suitable Streams of Change 115 Assessing Flow of Changes 116 Analyzing Dependencies 118 Managing Constraints 120 Finding Suitable Team Ownership Boundaries 122 Targeting Small Teams 123 Optimizing for Team Cognitive Load 124 Considering a Mix of Mindsets for Adaptive Teams 129 Identify Services Supporting Flow of Change 133 A Possible Team Constellation 134 Identifying Capability Gaps 136 Summary 136
Chapter 7: Visualizing Team Perspectives with Wardley Maps 139 A Wardley Map from a Platform Team Perspective 139 The Value Chain from an Enabling Team Perspective 148 Summary 150
Chapter 8: The Architecture for Flow Canvas 151 Assessing the As-Is Situation 152 Designing the Envisioned To-Be Situation 156 Summary 162
Part III: Evolving a Legacy System for Flow 163
Chapter 9: Designing a Legacy System for Flow 165 Assessing the Status Quo of a Legacy System Example 165 Addressing the Why of Business: The Purpose 166 Examining the Teams of Today 167 Assessing the Current Flow of Change 168 Visualizing the Current Landscape with a Wardley Map 171 Identifying Suitable Streams of Change 174 Categorizing the Problem Domain and Discovering the Core 174 Modularizing the Solution Space: Designing Bounded Contexts 177 Designing Context Maps 182 Visualizing the Future Landscape 186 Finding Suitable Team Ownership Boundaries 189 Optimizing Team Cognitive Load 189 Identifying Services Supporting Flow of Change 190 The Future Team Constellation 192 Identifying Capability Gaps 196 Summary 197
Chapter 10: Implementing Flow Optimization 199 Sharing the Why of Movement 199 Aligning Teams and Evolving Interactions to the System to Build 200 Transitioning with Dynamic Reteaming 203 Forming a Platform Team for Discovery 205 Closing Efficiency Gaps with Cloud Migration Strategies 207 Starting the Cloud Migration Journey with Replatforming 208 Merging the Remaining Infrastructure Team Members into the Platform Team 211 Forming the First Stream-Aligned Teams: Kicking Off the Refactoring Journey 213 Decomposing the Big Ball of Mud Through Incremental Refactoring 214 Evolution of Team Topologies'' Interaction Modes 219 UI Handling 221 Refactoring the Next Bounded Contexts 223 Splitting the Merged Platform Team into Multiple Teams 224 Implementing a Bounded Context with Tactical Design and Serverless Technologies 225 Summary 238
Chapter 11: Fostering Continuous Improvement and Driving Future Change 241 What Is Being Left Behind, and What Is Being Adopted? 241 Providing Opportunity to Switch Teams 243 Organizational Culture and Safety Thinking 243 The Learning Organization 245 Where to Move Next? 248 Summary 251
Chapter 12: Conclusion 253 References 257 Index 265