book

Collaborative Software Design

Name: Collaborative Software Design
ISBN: 9781633439252

by Kenny Baas, Evelyn van Kelle, Gien Verschatse

December 2024

Intermediate to advanced

416 pages

14h

English

Manning Publications

Read now

Unlock full access

Collaborative Software Design
Copyright
dedication
contents
front matter
forewordsprefaceacknowledgmentsabout this bookWho should read this book?How this book is organized: a roadmapliveBook discussion forumabout the authorsabout the cover illustration
1 The need for collaborative software design
1.1 Design decisions gone wrong at BigScreen1.1.1 Understanding the landscape1.1.2 BigScreen’s attempt at refactoring1.2 BigScreen: How collaborative modeling helped to improve design decisions1.2.1 Our approach for BigScreen1.2.2 The new architecture1.2.3 A brief history of software design1.2.4 The Agile theater1.2.5 Enabling teams to do collaborative software design1.3 Collaborative software design as a catalyst for better design decisions1.3.1 Collaborative modeling, design, and architecture1.3.2 Collaborative modeling ingredients and potential benefits of facilitation1.3.3 The effect of social dynamics on collaborative modeling sessions1.3.4 Collaborative decision-makingSummary
2 What is collaborative modeling?
2.1 Understanding the business problems2.1.1 What problems are we trying to solve?2.1.2 What is collaborative modeling?2.1.3 Exploring business problems using collaborative modeling2.2 Domain-Driven Design and collaborative modeling2.2.1 What is Domain-Driven Design?2.2.2 Who are the stakeholders?2.2.3 Why DDD and collaborative modeling go hand in hand2.3 Different collaborative modeling tools2.3.1 Collaborative modeling in the problem and solution space2.3.2 EventStorming2.3.3 Example Mapping2.3.4 Domain Storytelling2.3.5 When to use what tool2.4 Collaborative software design catalysts2.5 Further readingSummary
3 Using collaborative modeling for design and architecture
3.1 What is software design and architecture?3.1.1 The importance of meaning and definitions3.1.2 What is software architecture?3.1.3 What is software design?3.1.4 What are sociotechnical systems?3.1.5 Design decisions and collaborative modeling3.2 Heuristics for collaborative modeling3.2.1 What are heuristics?3.2.2 Competing heuristics3.2.3 How to use heuristics3.3 Driving the design by understanding the business3.3.1 Designing boundaries3.3.2 Why boundaries are designed through collaboration3.3.3 From design to architecture3.4 Collaborative software design catalysts3.5 Chapter heuristics3.6 Further readingSummary
4 The ingredients of collaborative modeling
4.1 The collaborative modeling stages4.1.1 Why use our stages?4.1.2 The stages4.2 Preparing for a session4.2.1 Preparing the content4.2.2 Preparing the space4.3 Sensemaking4.3.1 Conscious and unconscious minds4.3.2 Opening up conversations4.3.3 What is sensemaking?4.3.4 Why would you do sensemaking?4.3.5 In-person or remote?4.3.6 Premortem4.4 Check-in and check-out4.4.1 What is a check-in and check-out?4.4.2 Characteristics of a check-in and check-out4.4.3 Why would you do a check-in and check-out?4.4.4 Capturing feedback through check-outs4.5 Different collaboration styles for modeling with tools4.5.1 Together, Alone4.5.2 Split and Merge4.5.3 Small Group Diverge and Converge4.5.4 Liberating structures: 1-2-4-All4.5.5 Ensemble4.5.6 Fishbowl4.5.7 Anarchy!4.5.8 Guerilla4.5.9 The secret modeler4.5.10 How to use the styles4.6 Retrospective4.6.1 Evaluating the outcome of the session4.6.2 When we don’t do a retrospective4.7 Collaborative software design catalysts4.8 Chapter heuristics4.9 Further readingSummary
5 Facilitating collaborative modeling
5.1 The role of a facilitator5.1.1 The facilitator as an observer5.1.2 Other stances of a facilitator5.2 The core competencies of a facilitator5.2.1 Neutrality5.2.2 Observing5.2.3 Compassion5.2.4 Using and learning the core competencies5.3 Skill set of a facilitator5.3.1 Clear communication5.3.2 Active listening5.3.3 Holding space5.4 Facilitating sensemaking and collaborative styles5.4.1 Why do you need a facilitator?5.4.2 The role of a facilitator during sensemaking5.4.3 Facilitating check-ins and check-outs5.4.4 Preparing to facilitate sensemaking5.4.5 Facilitating collaborative styles5.4.6 What if you’re not the facilitator?5.5 Dealing with remote facilitation5.5.1 Benefits and potential downsides of the different forms5.5.2 Preparing a remote facilitation5.6 Collaborative software design catalysts5.7 Chapter heuristics5.8 Further readingSummary

6 The influence of ranking
6.1 Ranking explained6.1.1 What is ranking?6.1.2 Implicit versus explicit ranking6.1.3 Symbolic violence6.1.4 Epistemic injustice6.2 Becoming aware of ranking during collaboration and software design6.2.1 Group ranking6.2.2 People6.3 Facilitating ranking6.3.1 Analyzing the group rank6.3.2 Own, play, and share your rank6.3.3 Making the group aware of their rank6.4 Collaborative software design catalysts6.5 Chapter heuristics6.6 Further readingSummary
7 The effect and opportunities of cognitive bias
7.1 Cognitive bias explained7.1.1 What is cognitive bias?7.1.2 What does cognitive bias look like?7.1.3 System 1 and System 2: A crash course7.1.4 Embracing cognitive bias7.2 Cognitive bias during collaboration and software design7.2.1 Confirmation bias7.2.2 The law of triviality7.2.3 False-consensus effect7.2.4 Availability bias7.2.5 Loss aversion7.2.6 Additive bias7.3 Facilitating cognitive bias7.3.1 Self-fulfilling prophecy7.3.2 Altering behavior through nudges7.3.3 The different dimensions of nudges7.3.4 Becoming a choice architect7.4 Collaborative software design catalysts7.5 Chapter heuristics7.6 Further readingSummary
8 Resistance and conflict resolution
8.1 Why people show resistance and have conflicts8.1.1 What conflict is all about8.1.2 Edge behavior8.1.3 What is resistance?8.2 Resistance and conflict during collaboration8.2.1 Recognizing resistance and conflict in collaborative modeling8.2.2 The effect of resistance and conflict on software design8.2.3 Resistance and conflict as learning opportunities8.3 Facilitating toward a resolution8.3.1 Resistance and conflict in practice8.3.2 Kissing the group over the edge8.3.3 Creating role fluidity8.4 Collaborative software design catalysts8.5 Chapter heuristics8.6 Further readingSummary
9 Making sustainable design decisions
9.1 Decisions, decisions, decisions9.1.1 What is a decision anyway?9.1.2 Decision vs. outcome9.1.3 What you need to make a decision9.1.4 Reactive vs. proactive decisions9.1.5 Sustainability in software design9.2 Decision-making styles and levels of buy-in9.2.1 Autocracy vs. democracy9.2.2 Creating buy-in on decisions9.2.3 Buy-in on software design decisions9.3 Facilitating sustainable design decisions9.3.1 Moving toward a majority vote9.3.2 Go fishing!9.4 Collaborative software design catalysts9.5 Chapter heuristics9.6 Further readingSummary
10 Managing unsolvable problems
10.1 Polarities: Some problems can’t be solved10.1.1 What are polarities?10.1.2 Recognizing polarities10.1.3 Common polarities in collaborative modeling10.1.4 Crusaders and tradition bearers10.2 Visualizing a polarity10.2.1 Creating a shared understanding of a polarity10.2.2 Managing the polarity10.3 Managing polarities during collaborative modeling10.3.1 Getting stuck in a polarity10.3.2 Managing a polarity as facilitator10.3.3 Letting the group manage the polarity10.4 Collaborative software design catalysts10.5 Chapter heuristics10.6 Further readingSummary
11 Communicating and documenting decisions
11.1 Formalizing a decision11.1.1 Finding the consequences11.1.2 Capturing the decision11.2 Spreading the knowledge through the company11.2.1 Communicating decisions11.3 Keeping the decision alive11.3.1 The modeling process as a whirlpool11.3.2 Don’t fall in love with your model11.4 Collaborative software design catalysts11.5 Chapter heuristics11.6 Further readingSummary
12 Collaborative modeling beyond software design
12.1 Moving toward understanding the context12.1.1 Focusing on customer needs12.1.2 Connecting business strategy, product, and software architecture12.2 Collaborative modeling beyond software design12.2.1 Different roles, different modeling needs12.2.2 Customer journeys and EventStorming: A love story12.2.3 Aligning capabilities with your strategy12.3 Moving toward implementation12.3.1 When to go from collaborative modeling to coding12.3.2 From collaborative modeling to code12.4 Collaborative software design catalysts12.5 Chapter heuristics12.6 Further readingSummary
Appendix A.
index

Content preview from Collaborative Software Design

12 Collaborative modeling beyond software design

This chapter covers

Understanding the context through collaborative modeling with managing roles
Collaborating with user researchers and product and engineering managers
Moving toward implementation through collaborative modeling

We hope you’ve gotten a good understanding of why designing software requires collaborative software design with stakeholders. We also hope this book has been helpful as you take the first steps and understand how to do so. We discussed the different stages you’ll go through during collaborative modeling and what facilitation skills are needed to help the group move past certain blockers. We covered the social dynamics that come into play when bringing a diverse group ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Publisher Resources

ISBN: 9781633439252Publisher Support Publisher Website

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills

Collaborative Software Design

by Kenny Baas, Evelyn van Kelle, Gien Verschatse

12 Collaborative modeling beyond software design

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.