Architekturtransformation in der Praxis

Slide 1

Slide 1 text

Architektur- transformation Stefan Tilkov & Gernot Starke ... sinnvolle Veränderungen durchsetzen

Slide 2

Slide 2 text

Image Credits Sämtliche hier verwendeten Fotos von Personen sind lizenzfrei und stammen von: > https://www.pexels.com > https://unsplash.com/ Ausnahmen sind gekennzeichnet...

Slide 3

Slide 3 text

Es geht um SIE

Slide 4

Slide 4 text

Foto: JAX.de

Slide 5

Slide 5 text

Success Stories Cool People Entertaining Presentations Great New Technology Conference

Slide 6

Slide 6 text

... & Reality

Slide 7

Slide 7 text

(Resistance) «Stereotypes »

Slide 8

Slide 8 text

Professional Skeptic

Slide 9

Slide 9 text

Enthusiast

Slide 10

Slide 10 text

Yeahsayer

Slide 11

Slide 11 text

Legacy Lover

Slide 12

Slide 12 text

Status Protector

Slide 13

Slide 13 text

Vendor Agent

Slide 14

Slide 14 text

reasons-overview Vendor Agent Status Protector Professional Skeptic Yeah -sayer Enthusiast Legacy Lover

Slide 15

Slide 15 text

Enthusiast RISK: just another challenge I always wanted to solve.

Slide 16

Slide 16 text

Professional Skeptic Intelligence & experience

Slide 17

Slide 17 text

Yeahsayer Politics, Intrigue, Cunning

Slide 18

Slide 18 text

Legacy Lover Investments. LOTS of them.

Slide 19

Slide 19 text

Status Protector Comfort zone... Experience

Slide 20

Slide 20 text

Vendor Agent Trust

Slide 21

Slide 21 text

Good & Bad Reasons

Slide 22

Slide 22 text

Why change?

Slide 23

Slide 23 text

Good Reasons

Slide 24

Slide 24 text

Improve World Improve our work / system Improve our business

Slide 25

Slide 25 text

Bad Reasons

Slide 26

Slide 26 text

Shiny new toys Domain allergy Community status CV-driven development Cargo Cult

Slide 27

Slide 27 text

Shiny new toys Domain allergy Community status CV-driven development Cargo Cult especially bad... Don‘t!

Slide 28

Slide 28 text

So what? Watt nu?

Slide 29

Slide 29 text

You return to work from that nice conference. Your ideas are met with resistance. There are three paths. They are labeled quit, give up, work. $>|

Slide 30

Slide 30 text

They are labeled quit, give up, work. $> quit. That might be clever or not. Fatal CannotDecideException. Keynote over – exited. $>|

Slide 31

Slide 31 text

$> give up. No option – try again. (and if you give up again, you‘re awarded weakling-of- the-month, so think twice!)

Slide 32

Slide 32 text

$> work. You need to think and act strategically. But first, listen to the two old men.

Slide 33

Slide 33 text

Change is hard.

Slide 34

Slide 34 text

Politics Economics Organization Architecture Operations Engineering

Slide 35

Slide 35 text

Politics Economics Organization Architecture Operations Engineering one ring to rule them all...

Slide 36

Slide 36 text

Politics Economics Organization Architecture Operations Engineering fun parts

Slide 37

Slide 37 text

Minimize danger zone Change by Abstraction Change by split S/SCS Build from scratch

Slide 38

Slide 38 text

Change By Split Client Type 1 Flawed System Client Type 2 Kopiere für alle Client-Typen 1 Client Type 1 Flawed System Client Type 2 Flawed System Client Type 1 Reduced to Type 1 Client Type 2 Reduced to Type 2 Commons Reduziere und extrahiere Gemeinsamkeiten 2 Client Type 1 Reduced to Type 1 Client Type 2 Reduced to Type 2 New Commons Optimiere Gemeinsamkeiten 3

Slide 39

Slide 39 text

Change By Split (2) Client Type 1 Reduced to Type 1 Client Type 2 Reduced to Type 2 New Commons Optimiere spezifische Teilsysteme („Splits“) New Type 1 System Client Type 1 Client Type 2 New Commons New Type 2 System return to overview

Slide 40

Slide 40 text

Change-By-Abstraction (1) Client Code Flawed Supplier Client Code Abstraction Layer Kapsele die Interaktion mit den schlechten Teilen Lasse sämtlichen Client-Code diese Kapselung nutzen Erstelle einen besseren Supplier Client Code Flawed Supplier Client Code Abstraction Layer Abstraction Layer New Supplier Client Code Flawed Supplier Client Code Client Code Flawed Supplier Client Code Abstraction Layer Martin Fowler nennt das „Branch-By-Abstraction“

Slide 41

Slide 41 text

Change-By-Abstraction (2) Vervollständige den Supplier, ggfs. entferne den alten. Client Code Flawed Supplier Client Code Abstraction Layer Abstraction Layer New Supplier Client Code Flawed Supplier Client Code Abstraction Layer New Supplier return to overview

Slide 42

Slide 42 text

Recipes & Ingredients

Slide 43

Slide 43 text

Ingredients (appropriate) new technology (as desired) 2 Cups of pragmatism 1 XL portion of economics 1 large portion of politics

Slide 44

Slide 44 text

Find allies

Slide 45

Slide 45 text

Disrupt with care

Slide 46

Slide 46 text

Organize organizational change

Slide 47

Slide 47 text

Ensure positive business outcome think & speak „money“

Slide 48

Slide 48 text

Dr. Gernot Starke [email protected] https://www.flickr.com/photos/foto_db/16000636092 Stefan Tilkov [email protected]

Slide 49

Slide 49 text

analyze evaluate improve architecture improvement method Ein (Meta-) Plan

Slide 50

Slide 50 text

Agile Praktiken behutsam aber stringent einführen: • Entwicklung • IT-Betrieb • Vertrieb • Organisation • ...