Taming Complexity_ An Adventuree Logbook (Day 3)

Transcript

1. Taming Complexity An Adventure Logbook Day 3
5. Day 3 - 7 Things I learned about complexity
6. Me • aka Riccardo Capraro • DevOps / SRE / Platform / Cloud
7. Cynefin
10. 1. Complexity vs Complex (Adaptive) Systems
11. What is Complexity? Exchange Share
12. What is a Complex Adaptive System? Exchange Share
13. What is a Complex Adaptive System? Exchange Share
14. What is a Complex Adaptive System? Exchange
15. • Complex -> dynamic network of interactions What is a Complex Adaptive System? Exchange
16. • Complex -> dynamic network of interactions • Whole system > sum of components What is a Complex Adaptive System? Exchange
17. • Complex -> dynamic network of interactions • Whole system > sum of components • Agents interact and evolve with the system What is a Complex Adaptive System? Exchange
18. 2. Over-constraining Systems leads to Chaos
25. 3. Chaos: Crisis and Innovation
32. 4. The role of Experts
35. 5. What makes Software Architecture difficult?
39. 6. Be confused
41. 7. So it’s Complex? What then?
42. So it’s Complex? What then? • Create a portfolio of safe-to-fail experiments
43. So it’s Complex? What then? • Create a portfolio of safe-to-fail experiments • Exploration requires different skills from exploitation
44. So it’s Complex? What then? • Create a portfolio of safe-to-fail experiments • Exploration requires different skills from exploitation • Hypotheses must be coherent
45. So it’s Complex? What then? • Create a portfolio of safe-to-fail experiments • Exploration requires different skills from exploitation • Hypotheses must be coherent • Cluster before categorizing -> Do not assume structure
46. So it’s Complex? What then? • Create a portfolio of safe-to-fail experiments • Exploration requires different skills from exploitation • Hypotheses must be coherent • Cluster before categorizing -> Do not assume structure • Know modulators, create fast real-time feedback loops, modify modulator so that the system evolves in a sustainable and coherent way
47. Summary
48. Summary 1. Complex / Complex Adaptive System (complexity theory)
49. Summary 1. Complex / Complex Adaptive System (complexity theory) 2. Over-constraining systems leads to Chaos
50. Summary 1. Complex / Complex Adaptive System (complexity theory) 2. Over-constraining systems leads to Chaos 3. Chaos: Crisis and Innovation
51. Summary 1. Complex / Complex Adaptive System (complexity theory) 2. Over-constraining systems leads to Chaos 3. Chaos: Crisis and Innovation 4. What makes Software Architecture difficult?
52. Summary 1. Complex / Complex Adaptive System (complexity theory) 2. Over-constraining systems leads to Chaos 3. Chaos: Crisis and Innovation 4. What makes Software Architecture difficult? 5. The role of experts
53. Summary 1. Complex / Complex Adaptive System (complexity theory) 2. Over-constraining systems leads to Chaos 3. Chaos: Crisis and Innovation 4. What makes Software Architecture difficult? 5. The role of experts 6. Be confused
54. Summary 1. Complex / Complex Adaptive System (complexity theory) 2. Over-constraining systems leads to Chaos 3. Chaos: Crisis and Innovation 4. What makes Software Architecture difficult? 5. The role of experts 6. Be confused 7. So it’s Complex? What then?
55. What’s next?
56. Day 4 Cynefin Applied: making sense of Complexity
57. Day 4 Cynefin Applied: making sense of Complexity • How can we use Cynefin in our domain (running production systems)?
58. Day 4 Cynefin Applied: making sense of Complexity • How can we use Cynefin in our domain (running production systems)? • Highlight the difference in perspective between different Actors
59. References • Listen to the Cynefin framework explained by Dave Snowden • Learn about residuality theory with Barry O’Reilly
62. Bonus
63. What do we do when things are unclear? • Intuition / gut feeling • Stressor analysis • Skepticism • Pairing up • Framing uncertainty • Asking stupid questions • Thoughts and prayers • Find a domain expert • Find the smallest step to gain insights • 5 why + Apollo • Dig into benefits: is this beneficial and for whom (requirements) • Know how much effort goes into what • Find out if they know what they really want • Reduce the complexity by finding information • Find the expert or a part of the problem • Wardley mapping Frameworks
64. What makes Software Architecture difficult? • Many ways to do things, cannot say which one is right • It is about tradeoffs • It is a bet into the future (things change) • Unclear business needs • Do we have the right requirements? The no Jesus rule -> assume requirements are wrong • Assumptions, product discovery • We can use different methodologies for different environments • Waterfall to wrong domain