the goldilocks zone of lightweight architectural
play

The Goldilocks Zone of lightweight architectural governance Jonny - PowerPoint PPT Presentation

The Goldilocks Zone of lightweight architectural governance Jonny LeRoy @jahnnie ThoughtWorks THE G WORD GOVERNANCE GOVERNANCE GOVERNANCE GOVERNANCE WHY GOVERNANCE? Steer the ship WHY GOVERNANCE? Avoid the rocks Alignment


  1. “The Goldilocks Zone” of lightweight architectural governance Jonny LeRoy @jahnnie ThoughtWorks

  2. THE “G” WORD GOVERNANCE

  3. GOVERNANCE

  4. GOVERNANCE

  5. GOVERNANCE

  6. WHY GOVERNANCE?

  7. Steer the ship WHY GOVERNANCE? Avoid the rocks

  8. Alignment with strategy WHY GOVERNANCE? Risk management

  9. THE GOVERNANCER 6

  10. µServices Autonomous “2-pizza” teams

  11. THE GOVERNANCER 8

  12. “When 2-pizza teams plan a banquet”

  13. TWO FAILURE MODES Rigidity Chaos

  14. TWO FAILURE MODES ”Goldilocks zone” Rigidity Chaos

  15. THE NEED FOR SPEED

  16. THE NEED FOR SPEED The department of “no” No department

  17. 1 from MANDATE to VISION + PRINCIPLES If you want to build a ship, don't drum up people to collect wood and don't assign them tasks and work, but rather teach them to long for the endless immensity of the sea. Antoine de Saint-Exupéry

  18. 1. Ship it and iterate. 2. Make changes small, make them often. 3. Technical debt is a useful tool. 4. Solve problems at the root. 5. Do not accept deviant system behaviour. 6. Write code to be read. 7. Write code to be debugged. 8. If you can’t show it’s a bottleneck, don’t optimise it. 9. Unblock others whenever you can. 10. Leave the codebase better than you found it. https://monzo.com/blog/2018/06/29/engineering-principles/ https://12factor.net/

  19. 1. Ship it and iterate. 2. Make changes small, make them often. 3. Technical debt is a useful tool. 4. Solve problems at the root. 5. Do not accept deviant system behaviour. 6. Write code to be read. 7. Write code to be debugged. 8. If you can’t show it’s a bottleneck, don’t optimise it. 9. Unblock others whenever you can. 10. Leave the codebase better than you found it. https://monzo.com/blog/2018/06/29/engineering-principles/ https://12factor.net/

  20. 16

  21. ORGANIZATIONAL and SOFTWARE DELIVERY PERFORMANCE COMMERCIAL - Profitability - Productivity THROUGHPUT - Market share - Lead time - Number of customers - Deployment frequency NON-COMMERCIAL STABILITY - Quantity of products/ services - Mean time to restore (MTTR) - Operating efficiency - Change fail percentage - Customer satisfaction - Quality of products/services - Achieving organizational goals

  22. SPEED + STABILITY no longer in conflict … but what about RISK ? THROUGHPUT - Lead time - Deployment frequency STABILITY - Mean time to restore (MTTR) - Change fail percentage

  23. 2 AUTOMATE COMPLIANCE MAFEX Robocop Figure 010

  24. 2 AUTOMATE COMPLIANCE

  25. SECURITY AUTOMATION Archery Zap Snyk Git-secrets Quay.io Grafeas OpenSCAP Brakeman Find Security Bugs ...

  26. OTHER DIMENSIONS Quality Performance Resilience Regulatory Architectural characteristics Cost …

  27. BUT IT’S HARD WE’RE NOT EXPERTS WE’VE NEVER DONE THIS (we don’t trust our people)

  28. THE SECURITY SANDWICH

  29. THE SECURITY SANDWICH

  30. fixing THE SECURITY SANDWICH - Automation - Capability building - Expert help

  31. 3 ENROLL GATEKEEPERS AS COLLABORATORS

  32. FOR YOUR REFERENCE (ARCHITECTURE) (IMPLEMENTATION)

  33. How do you extend the shelf-life of your reference architecture ?

  34. Your architectural mandates are really just hypotheses to test ...

  35. from FORK AND FORGET to FEEDBACK LOOPS harvest > predict

  36. WE’RE ESCAPING THE MONOLITH But where are we going after that?

  37. PAVING the ROAD to the PIT OF SUCCESS

  38. ONBOARDING , DEVELOPER EXPERIENCE and PRODUCT THINKING

  39. WE’RE NOT A SHIP WE’RE A FLOTILLA and we don’t have enough experts for each team

  40. 4 RETHINK your COMMUNICATION PATTERNS

  41. A rchitecture D ecision R ecords

  42. 4 RETHINK your COMMUNICATION PATTERNS North / South East / West

  43. TECH RADAR for lightweight ARCHITECTURE GOVERNANCE - Bottom-up sharing of successes and failures 
 - Opportunity for governance / review 
 - Alignment around shared vision 
 - Balance standardization and innovation 
 - Inclusive and fun learning opportunity

  44. STICKIES AT THE READY CUSTOMIZE THE RINGS + QUADRANTS End of life / retire Packages, initiatives RADAR OF RADARS Radars per team, group, portfolio, organization PROCESS / GUIDELINES FOR MOVING RINGS Success criteria for assess, trial or adopt WIP LIMITS How much experimentation at one time? What is your risk tolerance?

  45. THE MAJOR SHIFTS REQUIRED - From MANDATE to VISION and PRINCIPLES - AUTOMATE COMPLIANCE - Enroll GATEKEEPERS as COLLABORATORS - RETHINK your COMMUNICATION PATTERNS - PRODUCT THINKING / SERVICE MENTALITY - COMFORT with EVOLUTION

  46. how to get started GO TO WHERE START THE THE ACTION IS CONVERSATION

  47. SERVANT LEADERSHIP , ARCHITECTURE GOVERNANCE and your TALENT STRATEGY

  48. When 2-pizza teams plan a banquet! “The Goldilocks Zone” of lightweight architectural governance Jonny LeRoy thoughtworks.com/careers

  49. Rate today ’s session Session page on oreillysacon.com/ny O’Reilly Events App

Recommend


More recommend