/grō/ - developing an emergent architecture

by DJ Daugherty

Slide 1

Slide 1 text

No content

Slide 2

Slide 2 text

/grō/ emergent architecture developing an

Slide 3

Slide 3 text

dj daugherty [email protected] @ddaugher

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

i am

Slide 6

Slide 6 text

i am developer.

Slide 7

Slide 7 text

developer. i am tech lead.

Slide 8

Slide 8 text

tech lead. i am developer. business.

Slide 9

Slide 9 text

tech lead. i am developer. business. I create business solutions for business problems…

Slide 10

Slide 10 text

why did I choose this title?

Slide 11

Slide 11 text

grow /ɡrō/ verb undergo natural development by increasing in size and changing physically; progress to maturity.

Slide 12

Slide 12 text

disclosure

Slide 13

Slide 13 text

i struggle with these ideas every day. disclosure

Slide 14

Slide 14 text

think.

Slide 15

Slide 15 text

question the norm.

Slide 16

Slide 16 text

disruption source of

Slide 17

Slide 17 text

technical?

Slide 18

Slide 18 text

business?

Slide 19

Slide 19 text

Architectural design more often than not, struggles to find a place within an agile environment. Unfortunately, big up-front design is second-nature and the designing, building, and maintaining of an architecture does not come for free. Within this talk we will... - explore why technical practices are key to technical excellence - discuss the concepts of intentional yet emergent - discuss how to master incremental planning - discuss how to embrace uncertainty - and understand cost/benefit of constant rework

Slide 20

Slide 20 text

Slide 21

Slide 21 text

Slide 22

Slide 22 text

Slide 23

Slide 23 text

Slide 24

Slide 24 text

Slide 25

Slide 25 text

Slide 26

Slide 26 text

Slide 27

Slide 27 text

Slide 28

Slide 28 text

Slide 29

Slide 29 text

Slide 30

Slide 30 text

Slide 31

Slide 31 text

/grō/ emergent architecture developing an

Slide 32

Slide 32 text

emergent architecture developing an

Slide 33

Slide 33 text

The purpose of architecture is ?

Slide 34

Slide 34 text

to shape the solution and address technical risks. The purpose of architecture is

Slide 35

Slide 35 text

Slide 36

Slide 36 text

intentional vs. emergent

Slide 37

Slide 37 text

intentional vs. emergent

Slide 38

Slide 38 text

intentional vs. emergent

Slide 39

Slide 39 text

intentional ?

Slide 40

Slide 40 text

diagrams, documents intentional ?

Slide 41

Slide 41 text

diagrams, documents hours of meetings intentional ?

Slide 42

Slide 42 text

diagrams, documents hours of meetings no working software intentional ?

Slide 43

Slide 43 text

diagrams, documents hours of meetings no working software intentional ? BUFD

Slide 44

Slide 44 text

emergent ?

Slide 45

Slide 45 text

let's not do any architecture design. let it emerge. emergent ?

Slide 46

Slide 46 text

neither is good.

Slide 47

Slide 47 text

No content

Slide 48

Slide 48 text

emergence is not sufficient!

Slide 49

Slide 49 text

good architecture doesn’t emerge.

Slide 50

Slide 50 text

good architecture doesn’t emerge. it evolves.

Slide 51

Slide 51 text

Slide 52

Slide 52 text

Slide 53

Slide 53 text

Slide 54

Slide 54 text

religious conversation.

Slide 55

Slide 55 text

“agile evangelists claim we (almost) do not need conventional architectural design at all. this emergent approach leads to the simplest and therefore the most optimal architecture possible.”

Slide 56

Slide 56 text

No content

Slide 57

Slide 57 text

No content

Slide 58

Slide 58 text

No content

Slide 59

Slide 59 text

agile manifesto (#11) the best architectures, requirements and designs emerge from self-organizing teams.

Slide 60

Slide 60 text

No content

Slide 61

Slide 61 text

no more big upfront design

Slide 62

Slide 62 text

agile teams struggle with architecture

Slide 63

Slide 63 text

uncomfortable not having a design first rework is inevitable

Slide 64

Slide 64 text

- cost and benefit of incremental design - must embrace the uncertainty - incremental planning must master:

Slide 65

Slide 65 text

No content

Slide 66

Slide 66 text

/grō/ emergent architecture developing an

Slide 67

Slide 67 text

emergent architecture developing an

Slide 68

Slide 68 text

evolving architecture developing an

Slide 69

Slide 69 text

evolving architecture developing an

Slide 70

Slide 70 text

test driven development continuous integration paired programming refactoring collective code ownership technical practices are key:

Slide 71

Slide 71 text

test driven ‘doing’ continuous integration refactoring collective code ownership technical practices are key: paired programming

Slide 72

Slide 72 text

test driven ‘doing’ continuous ‘feedback’ refactoring collective code ownership technical practices are key: paired programming

Slide 73

Slide 73 text

test driven ‘doing’ refactoring collective code ownership technical practices are key: paired ‘collaboration’ continuous ‘feedback’

Slide 74

Slide 74 text

test driven ‘doing’ continuous ‘feedback’ refactoring collective ownership technical practices are key: paired ‘collaboration’

Slide 75

Slide 75 text

- think big, act small, fail fast, learn rapidly - last responsible moment - simplest thing that works - sprint zero - backlog - working software how do we get there?

Slide 76

Slide 76 text

- think big, act small, fail fast, learn rapidly (Poppendiecks' book Lean Software Development: An Agile Toolkit)

Slide 77

Slide 77 text

thinkBIG.

Slide 78

Slide 78 text

actsmall.

Slide 79

Slide 79 text

failfast.

Slide 80

Slide 80 text

failFAST.

Slide 81

Slide 81 text

learnrapidly.

Slide 82

Slide 82 text

- think big, act small, fail fast, learn rapidly - last responsible moment - simplest thing that works - sprint zero - backlog - working software how do we get there?

Slide 83

Slide 83 text

- last responsible moment

Slide 84

Slide 84 text

my favorite - last responsible moment

Slide 85

Slide 85 text

all about information, the most current information is always the best - last responsible moment

Slide 86

Slide 86 text

"the moment at which failing to make a decision eliminates an important alternative." (Poppendiecks' book Lean Software Development: An Agile Toolkit) - last responsible moment

Slide 87

Slide 87 text

- think big, act small, fail fast, learn rapidly - last responsible moment - simplest thing that works - sprint zero - backlog - working software how do we get there?

Slide 88

Slide 88 text

- simplest thing that works

Slide 89

Slide 89 text

"the art of maximizing the amount of work not done." simplest thing that could work

Slide 90

Slide 90 text

no gold-plating or shaving the yak simplest thing that could work

Slide 91

Slide 91 text

No content

Slide 92

Slide 92 text

- think big, act small, fail fast, learn rapidly - last responsible moment - simplest thing that works - sprint zero - backlog - working software how do we get there?

Slide 93

Slide 93 text

- sprint zero

Slide 94

Slide 94 text

stopping and thinking... building backlog sprint zero

Slide 95

Slide 95 text

- think big, act small, fail fast, learn rapidly - last responsible moment - simplest thing that works - sprint zero - backlog - working software how do we get there?

Slide 96

Slide 96 text

- working software

Slide 97

Slide 97 text

- working architecture

Slide 98

Slide 98 text

"working software is the primary measure of progress." working architecture

Slide 99

Slide 99 text

- think big, act small, fail fast, learn rapidly - last responsible moment - simplest thing that works - sprint zero - backlog - working software how do we get there?

Slide 100

Slide 100 text

- backlog

Slide 101

Slide 101 text

- architectural backlog

Slide 102

Slide 102 text

"-ilities" of a product architectural backlog

Slide 103

Slide 103 text

scalability architectural backlog

Slide 104

Slide 104 text

maintainability architectural backlog

Slide 105

Slide 105 text

usability architectural backlog

Slide 106

Slide 106 text

reliability architectural backlog

Slide 107

Slide 107 text

extensibility architectural backlog

Slide 108

Slide 108 text

reusability architectural backlog

Slide 109

Slide 109 text

security architectural backlog

Slide 110

Slide 110 text

securability architectural backlog

Slide 111

Slide 111 text

robotic uprising

Slide 112

Slide 112 text

1. design emerges. Architecture is a collaboration.

Slide 113

Slide 113 text

1. design evolves. Architecture is a collaboration.

Slide 114

Slide 114 text

1. design evolves. Architecture is a collaboration. 2. big system. big backlog.

Slide 115

Slide 115 text

1. design evolves. Architecture is a collaboration. 2. big system. big backlog. 3. build the simplest architecture that can possibly work

Slide 116

Slide 116 text

1. design evolves. Architecture is a collaboration. 2. big system. big backlog. 3. build the simplest architecture that can possibly work 4. code / model it.

Slide 117

Slide 117 text

1. design evolves. Architecture is a collaboration. 2. big system. big backlog. 3. build the simplest architecture that can possibly work 5. there is no monopoly on innovation 4. code / model it.

Slide 118

Slide 118 text

credit card example

Slide 119

Slide 119 text

data import example

Slide 120

Slide 120 text

noteasy.

Slide 121

Slide 121 text

No content

Slide 122

Slide 122 text

just start!

Slide 123

Slide 123 text

just start! it will stink at ﬁrst.

Slide 124

Slide 124 text

just start! it will stink at ﬁrst. that’s ok.

Slide 125

Slide 125 text

just start! it will stink at ﬁrst. have a ritual. that’s ok.

Slide 126

Slide 126 text

just start! it will stink at ﬁrst. have a ritual. it is ok to fail. that’s ok.

Slide 127

Slide 127 text

just start! it will stink at ﬁrst. have a ritual. it is ok to fail. caﬀeine helps! that’s ok.

Slide 128

Slide 128 text

just start! it will stink at ﬁrst. have a ritual. it is ok to fail. caﬀeine helps! eventually it will stink less. that’s ok.

Slide 129

Slide 129 text

dj daugherty [email protected] @ddaugher thanks. https://speakerdeck.com/ddaugher