in d ealing with complexity ENGN2219/COMP6719 2020 - - PowerPoint PPT Presentation

in d ealing with complexity
SMART_READER_LITE
LIVE PREVIEW

in d ealing with complexity ENGN2219/COMP6719 2020 - - PowerPoint PPT Presentation

The Role of Simulation in d ealing with complexity ENGN2219/COMP6719 2020 Shayne.Flint@anu.edu.au Research School of Computer Science College of Engineering and Computer Science Agenda Thinking about complexity Dave


slide-1
SLIDE 1

The Role of Simulation

in dealing with complexity

Shayne.Flint@anu.edu.au Research School of Computer Science College of Engineering and Computer Science

ENGN2219/COMP6719 – 2020

slide-2
SLIDE 2

Agenda …

  • Thinking about complexity

– Dave Snowden’s Cynefin Framework

  • Dealing with complexity

– System Dynamics – Boyd’s OODA loop

  • The role of simulation

– Brooks’ Law example

2

slide-3
SLIDE 3

Thinking About Complexity…

3

slide-4
SLIDE 4

Thinking about complexity …

  • The Cynefin sense-making framework

– Pronounced “KUN-iv-in” (It’s a Welsh word!) – Created in 1999 by Dave Snowden – http://cognitive-edge.com

  • We require different kinds of thinking for

– Simple Problems – Complicated Problems – Complex Problems – Chaotic Problems

4

slide-5
SLIDE 5

Unpredictable

5

Predictable

The Cynefin Sense-making Framework

slide-6
SLIDE 6

6

Predictable

Unpredictable

The Cynefin Sense-making Framework

Complicated Simple

slide-7
SLIDE 7

7

Predictable

Complex

The Cynefin Sense-making Framework

Complicated

Unpredictable

Chaotic Simple

slide-8
SLIDE 8

8

slide-9
SLIDE 9

9

slide-10
SLIDE 10

10

slide-11
SLIDE 11
slide-12
SLIDE 12

12

Dealing with Complexity

slide-13
SLIDE 13
slide-14
SLIDE 14

Dealing with complexity

  • Experimentation is at the core

– Probe – with safe to run experiments – Sense – what works & what doesn’t – Respond – with emergent practices

  • System Dynamics modeling and simulation can

help

  • We will also look at why Agility is important

when dealing with complexity

14

slide-15
SLIDE 15

System Dynamics

  • An approach to understanding the

behavior of complex systems over time

– Developed by Jay Forrester at MIT in the 1950’s – Originally focussed on industrial processes – Now widely used for policy analysis and design

  • Systems are represented using

– Causal Loop Diagrams (CLD) – Stock and Flow Diagrams (SFD)

15

slide-16
SLIDE 16

CLD Example – using Exit Mould

16

slide-17
SLIDE 17

CLD Example – using Exit Mould

17

SYMPTOM SYMPTOM

Mould on my bathroom tiles

slide-18
SLIDE 18

CLD Example – using Exit Mould

18

SYMPTOM SYMPTOM FIX FIX

+

Mould on my bathroom tiles Apply Exit Mould and wipe down tiles

slide-19
SLIDE 19

CLD Example – using Exit Mould

19

SYMPTOM SYMPTOM FIX FIX

+

Mould on my bathroom tiles Apply Exit Mould and wipe down tiles

slide-20
SLIDE 20

CLD Example – using Exit Mould

20

SYMPTOM SYMPTOM FIX FIX UNEXPECTED CONSEQUENCE UNEXPECTED CONSEQUENCE

  • +

+

Mould on my bathroom tiles Apply Exit Mould and wipe down tiles delay

slide-21
SLIDE 21

CLD Example – using Exit Mould

21

SYMPTOM SYMPTOM FIX FIX UNEXPECTED CONSEQUENCE UNEXPECTED CONSEQUENCE

  • +

+

Mould on my bathroom tiles Apply Exit Mould and wipe down tiles Exit Mould damages grout and tile surface

slide-22
SLIDE 22

CLD Example – using Exit Mould

22

SYMPTOM SYMPTOM FIX FIX UNEXPECTED CONSEQUENCE UNEXPECTED CONSEQUENCE PROBLEM PROBLEM

  • +

+ +

Mould on my bathroom tiles Apply Exit Mould and wipe down tiles Exit Mould damages grout and tile surface Damage encourages growth of deep mould

slide-23
SLIDE 23

CLD Example – using Exit Mould

23

SYMPTOM SYMPTOM FIX FIX UNEXPECTED CONSEQUENCE UNEXPECTED CONSEQUENCE PROBLEM PROBLEM

  • +

+ + +

Mould on my bathroom tiles Apply Exit Mould and wipe down tiles Exit Mould damages grout and tile surface Damage encourages growth of deep mould

slide-24
SLIDE 24

24

“Fixes That Fail”

This is an example of a System Archetype

(a common pattern of behaviour)

slide-25
SLIDE 25

Other Fixes that Fail …

  • The war on terror
  • Building freeways
  • Borrowing money to pay interest
  • Cutting maintenance and repair costs

25

slide-26
SLIDE 26

Dealing with a staff shortage …

26

SYMPTOM SYMPTOM

Staff Shortage

(cannot employ new people)

slide-27
SLIDE 27

Dealing with a staff shortage …

27

SYMPTOM SYMPTOM FIX FIX

+

Staff Shortage

(cannot employ new people)

slide-28
SLIDE 28

Dealing with a staff shortage …

28

SYMPTOM SYMPTOM FIX FIX

+

Increase overtime Staff Shortage

(cannot employ new people)

slide-29
SLIDE 29

Dealing with a staff shortage …

29

SYMPTOM SYMPTOM FIX FIX

  • +

Increase overtime Staff Shortage

(cannot employ new people)

slide-30
SLIDE 30

Dealing with a staff shortage …

30

SYMPTOM SYMPTOM FIX FIX UNEXPECTED CONSEQUENCE UNEXPECTED CONSEQUENCE

  • +

+

Increase overtime Staff Shortage

(cannot employ new people)

slide-31
SLIDE 31

Dealing with a staff shortage …

31

SYMPTOM SYMPTOM FIX FIX UNEXPECTED CONSEQUENCE UNEXPECTED CONSEQUENCE

  • +

+

Increase overtime Physical and mental health issues Staff Shortage

(cannot employ new people)

slide-32
SLIDE 32

Dealing with a staff shortage …

32

SYMPTOM SYMPTOM FIX FIX UNEXPECTED CONSEQUENCE UNEXPECTED CONSEQUENCE PROBLEM PROBLEM

  • +

+ +

Increase overtime Physical and mental health issues Staff Shortage

(cannot employ new people)

slide-33
SLIDE 33

Dealing with a staff shortage …

33

SYMPTOM SYMPTOM FIX FIX UNEXPECTED CONSEQUENCE UNEXPECTED CONSEQUENCE PROBLEM PROBLEM

  • +

+ + +

Increase overtime Physical and mental health issues Increased sick leave Staff Shortage

(cannot employ new people)

slide-34
SLIDE 34

There are many such archetypes …

  • System Archetypes describe patterns of

behavior that surface in many different domains

  • They help us

– think about the possible behavior of complex systems – understand why a complex system behaves the way it does, and – identify things we can do to change that behavior (ie. the things that work and don’t work).

34

slide-35
SLIDE 35

The need for agility

35

slide-36
SLIDE 36

John Boyd

  • Fighter pilot
  • Military, sport and

business strategist

36

slide-37
SLIDE 37

Boyd’s OODA Loop

  • A continuous process of learning and change in

competitive environments

37

slide-38
SLIDE 38

Speed is the key to success

  • Success comes from getting around your OODA loop

more quickly than your competitor

– Business, Nature, Sport, Politics …

  • If your competitor is quicker than you:

– Your competitor's behavior will eventually appear chaotic – you will be confused – You will make bad decisions - based on ‘Orientation’ and ‘Observations’ that are no longer valid – You will lose or fail

  • Complex systems often evolve rapidly

– You need to experiment, learn and act quickly

38

slide-39
SLIDE 39

The role of simulation

39

slide-40
SLIDE 40

How can simulation help

  • We can simulate the behavior of complex systems

– eg. System Dynamics Stock & Flow models

  • We can do this quickly

– In order to get through our OODA loop quickly

  • We can run many simulations based on different

parameters

– That is, we can run a series of different ‘experiments’ – To find out what works & what doesn’t

40

slide-41
SLIDE 41

SFD Simulation Example - Brooks’ Law

  • Fred Brooks

– Turing Award 1999 – Author of “The Mythical Man-Month” – Author of “No Silver Bullet”

41

slide-42
SLIDE 42

SFD Simulation Example - Brooks’ Law

42

“Adding manpower to a late software project makes it later.”

Brooks’ Law

  • Note that in his book ‘The Mythical Man-Month’, Brooks

says that this law is an ‘outrageous oversimplification’.

  • In reality, adding people to a project is a complex problem
  • We can explore this problem using System Dynamics and

Simulation.

slide-43
SLIDE 43

SFD Simulation Example - Brooks’ Law

43

https://insightmaker.com/insight/4648/Clone-of-Brooks-Law

slide-44
SLIDE 44

Live Demonstration

slide-45
SLIDE 45

SFD Simulation Example - Brooks’ Law

45

  • No new developers at day 100
slide-46
SLIDE 46

SFD Simulation Example - Brooks’ Law

46

  • 5 new developers at day 100
slide-47
SLIDE 47

SFD Simulation Example - Brooks’ Law

47

  • 15 new developers at day 100
slide-48
SLIDE 48

SFD Simulation Example - Brooks’ Law

48

  • 15 new developers at day 100, decreased communications
slide-49
SLIDE 49

SFD Simulation Example - Brooks’ Law

  • But, how do we reduce communication?

– Fewer meetings? – Restrictions on email use? – ...

  • … and what are the consequences?

– More mistakes? – Duplication of work? – ...

  • Additional complexity …

– Need to add these aspects to the model

49

slide-50
SLIDE 50

Exploring online SFD simulations

  • https://insightmaker.com

– Free & Open – Supports Collaboration – Huge repository of models you can play with

50

slide-51
SLIDE 51

Exploring online SFD simulations

51

https://insightmaker.com/insight/12842/2014-Weather-Climate-E xtreme-Loss-of-Arable-Land-and-Ocean-Fertility-The-World3-Mo del-Forecaster

slide-52
SLIDE 52

Exploring online SFD simulations

52

https://insightmaker.com/insight/101411/Air-Transport-Causal-Loop-Diagram

slide-53
SLIDE 53

Exploring online SFD simulations

53

https://insightmaker.com/insight/7682/Implementing-Chronic-Care-Management

slide-54
SLIDE 54

Exploring online SFD simulations

54

https://insightmaker.com/insight/188271/Upgrade-of-Kermack-McKendrick-Epidemic-SIR-Infectious-Disease-Model-Metrics-by-Guy-Lakeman

slide-55
SLIDE 55

Additional Material …

55

System Dynamics

– Wikipedia, “System Dynamics”

  • https://en.wikipedia.org/wiki/System_dynamics

– Insight Maker, “Free modeling and simulation in your browser”

  • https://insightmaker.com

Cynefin Framework

– Snowden, “Making Sense of Complexity”, Lean, Agile & Scrum Conference 2013

  • https://www.youtube.com/watch?v=y6RfqmTZejU

– O’Sullivan, “Domain Driven Design for Everyone Else”, dev.to

  • https://dev.to/barryosull/domain-driven-design-for-everyone-else-a9

– Snowden and Boone, “A Leader’s Framework for Decision Making”, Harvard Business Review, Nov 2007

  • https://hbr.org/2007/11/a-leaders-framework-for-decision-making

OODA Loops

– Adolph, “What lessons can the agile community learn from a maverick fighter pilot?”, Agile’06

  • https://ieeexplore.ieee.org/document/1667567/
slide-56
SLIDE 56

Additional Material …

56

Fred Brooks

– Wikipedia, “Fred Brooks”

  • https://en.wikipedia.org/wiki/Fred_Brooks

– Brooks, Fredrick P. (1975). “The Mythical Man-Month: essays in software engineering.” Reading, Massachusetts: Addison-Wesley.

  • Amazon

– Brooks, F. P., Jr. (1987). “No Silver Bullet – Essence and Accidents of Software Engineering”. Computer. 20 (4): 10-19

  • ACM
slide-57
SLIDE 57

Questions ?

57