From Business Goals to Software Requirements with Impact Mapping and Domain Storytelling

Slide 1

Slide 1 text

From Business Goals to Software Requirements with Impact Mapping and Domain Storytelling DDD Europe 2025 Mufrid Krilic, Coder, Coach, Consultant at CoWork Henning Schwentner, Coder, Coach, Consultant at WPS

Slide 2

Slide 2 text

No content

Slide 3

Slide 3 text

Given the business goal….

Slide 4

Slide 4 text

From Business Goals to Impacts Workshop Part 1

Slide 5

Slide 5 text

Impact Mapping ▪ “An impact map is a visualization of scope and underlying assumptions, created collaboratively, by (senior) technical and business people” ▪ Gojko Adzic, Impact Mapping, the book impactmapping.org

Slide 6

Slide 6 text

Four questions to ask to facilitate the conversation about business intent! • Business goal Why? • Role/Actor Who? • Impact How? • Deliverable • Experiment What? Software Goes Here Prioritize Here!

Slide 7

Slide 7 text

Software Requirements Prioritization Prioritize on the Impacts!

Slide 8

Slide 8 text

Software Requirements Prioritization Easier to agree on prioritization with stakeholders

Slide 9

Slide 9 text

Software Requirements Prioritization Prioritization aligned with the business intent!

Slide 10

Slide 10 text

No content

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

Actors Who can contribute to the goal?

Slide 13

Slide 13 text

Actors Who can obstruct us reaching the goal?

Slide 14

Slide 14 text

Actors Whose behavior do we want to impact?

Slide 15

Slide 15 text

Impact Behavior change!

Slide 16

Slide 16 text

Impact Measurable!

Slide 17

Slide 17 text

Break 10 minutes! Helping Build Domain-Driven Product Organizations

Slide 18

Slide 18 text

Wrap-up Where to go from here?

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

Practice! Start on Monday! Somewhere in safe environments then improve!

Slide 21

Slide 21 text

Book by Gojko Adzic impactmapping.org Impact Mapping: Making a big impact with software products and projects

Slide 22

Slide 22 text

Book by Stefan Hofer and Henning Schwentner domainstorytelling.org Collaborative, Visual and Agile Way to Build Domain-Driven Software

Slide 23

Slide 23 text

• “Domain-Driven Design Enthusiast” • CoWork – Consultant and Coach • Tight-Loose-Tight • Product and Technology Leadership Helping Build Domain-Driven Product Organizations

Slide 24

Slide 24 text

Henning Schwentner https://hschwentner.io in/henningschwentner [email protected]

Slide 25

Slide 25 text

No content

Slide 26

Slide 26 text

Images • Vecteezy.com • Tim Hüfner • https://unsplash.com/@joshua_hoehne • https://unsplash.com/@kattyukawa • https://unsplash.com/@brett_jordan