Cultivating Architecture (2022)

Presented at Xpand Jordan 2022

Transcript

1. Cultivating Architecture Birgitta Böckeler | @birgitta410 October 2022
2. Autonomous Teams
3. https://agilemanifesto.org/
4. Autonomous Teams
5. Motivation Flexibility Scaling Why autonomy?
6. Decentralisation Autonomous Teams && Architecture
7. “We need some governance!”
8. manipulate control rule restrain guide serve as deciding principle have decisive influence Exert a determining or guiding influence to govern
9. guide serve as deciding principle have decisive influence Exert a determining or guiding influence rule to govern
10. [ Side note on automation of governance ]
11. Decision Records Default Practices Business Goals Architecture Characteristics Architecture Principles Building blocks of a Guidance-based approach
12. Decision Records Default Practices Business Goals Architecture Characteristics Architecture Principles
13. Push & pull the business context
14. https://blog.pragmaticengineer.com/ the-product-minded-engineer/ Gergely Orosz Reward “product- minded engineers”
16. Decision Records Default Practices Business Goals Architecture Characteristics Architecture Principles
17. Architecture Characteristics
18. Accessibility Auditability Availability Compliance Configurability Data integrity Distributability Extensibility Internationalization Monitoring Performance Portability Resilience / Fault Tolerance Scalability Security Supportability Usability Upgradability Responsiveness Testability Recoverability Data Privacy Find your focus … Traceability
19. Prioritise Offline Availability Portability Data privacy … …
20. Prioritise
21. Decision Records Default Practices Business Goals Architecture Characteristics Architecture Principles
22. https://www.slideshare.net/EoinWoods1/using-software-architecture-principles-in-practice “A declarative statement made with the intention of guiding architectural design decisions in order to achieve one or more qualities of a system.” - Eoin Woods Architecture Principles
23. Statement Team Decisions System Qualities Team Decisions Team Decisions Team Decisions guide lead to Architecture Characteristics
24. Example http://engineering-principles.onejl.uk/ “A declarative statement made with the intention of guiding architectural design decisions in order to achieve one or more qualities of a system.”
25. http://engineering-principles.onejl.uk/ http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap29.html in order to achieve one or more qualities of a system. made with the intention of guiding architectural design decisions A declarative statement
26. http://engineering-principles.onejl.uk
27. Sam Newman, “Building Microservices” Rationale Implications
28. Facts over Opinions Hypothesis-driven development Data democratization Enter new market X Customer centricity
29. Authorizations are role-based Eliminate integration databases Do ongoing user research Design for Pace of Change Build Differentiators Open Integration Standards Reusable Components Scale Horizontally Cloud Native Production Ready Automate Repetitive Tasks Clean Code Continuous Delivery Consistent Environments Maintainability Performance Importance Release Early and Often Security First Loosely Coupled Security, Compliance and Data Privacy AWS First Be Bold Data-driven/ metric-driven Infrastructure as Code Have a multidisciplinary team Eliminate accidental complexity Consistent interfaces and data flows Small and Simple Smarts in the Nodes, not the Network Encapsulate legacy Minimal customisation of COTS/SaaS Organise around Business Capabilities Consolidate and cleanse data Minimize technology variation Cleaning is part of work well done You build it, you run it Apply principle of least privileges Data is a shared asset Small independent services Facts over Opinions Autonomy over Economies of Scale Decisions at latest responsible moment Single Source of Truth Data freshness Domain Integrity Sensitive data are exchanged securely Existing experiences over different variations Asynchronous interactions over synchronous coupling
30. Authorizations are role-based Eliminate integration databases Do ongoing user research Design for Pace of Change Build Differentiators Open Integration Standards Reusable Components Scale Horizontally Cloud Native Production Ready Automate Repetitive Tasks Clean Code Continuous Delivery Consistent Environments Maintainability Performance Importance Release Early and Often Security First Loosely Coupled Security, Compliance and Data Privacy AWS First Be Bold Data-driven/ metric-driven Infrastructure as Code Have a multidisciplinary team Eliminate accidental complexity Consistent interfaces and data flows Small and Simple Smarts in the Nodes, not the Network Encapsulate legacy Minimal customisation of COTS/SaaS Organise around Business Capabilities Consolidate and cleanse data Minimize technology variation Cleaning is part of work well done You build it, you run it Apply principle of least privileges Data is a shared asset Small independent services Facts over Opinions Autonomy over Economies of Scale Decisions at latest responsible moment Single Source of Truth Data freshness Domain Integrity Sensitive data are exchanged securely Existing experiences over different variations Asynchronous interactions over synchronous coupling Focus Consensus Official Blessing Why bother with your own principles?
31. How to find your principles?
32. Goals What’s holding us back today? What’s moving us forward today? Risks Strengths Opportunities Threats Weaknesses Cross-team relevance Business Goals Architecture Characteristics
34. Decision Records Default Practices Business Goals Architecture Characteristics Architecture Principles
35. Sensible Default Practices Thoughtworks Technology Podcast, “Starting out with sensible default practices” https://www.thoughtworks.com/en-de/insights/podcasts/technology-podcasts/sensible-defaults
36. Technology Radar https://thoughtworks.com/radar
37. Build your own Technology Radar https://opensource.zalando.com/tech-radar/
38. Promising, experimenting with this on one or more teams TRIAL https://www.thoughtworks.com/insights/blog/using-thoughtworks-technology-radar-track-governance Proven to work within this organisation, well supported ADOPT Evaluating for potential experiments, under active research ASSESS Deprecated, don't start new projects using this HOLD Level of guidance
39. Decision Records Default Practices Business Goals Architecture Characteristics Architecture Principles
40. Decision Records https://cognitect.com/blog/2011/11/15/documenting-architecture-decisions
41. Business Goals are connected Architecture Characteristics are defined Decisions Records are documented Default Practices are documented and evolved Architecture Principles are continuously discussed, understood and evolved Building blocks of a Guidance-based approach
42. CULTIVATING ARCHITECTURE How to make it effective?
43. Autonomy Trust Voice Westrum Organizational Culture Software Delivery Performance Forsgren et al, State of DevOps Report 2018 https://puppet.com/resources/report/2018-state-devops-report predictive relationship Climate for Learning
44. guide serve as deciding principle have decisive influence Exert a determining or guiding influence rule foster learning culture to govern telling people what to do
45. CULTIVATING ARCHITECTURE Approach governance through a learning lens Nudge effectively
46. https://www.bi.team/publications/east-four-simple-ways-to-apply-behavioural-insights/
47. “Harness the power of defaults” “Show that most people perform the desired behaviour” “Prompt people when they are likely to be most receptive” “Design rewards and sanctions for maximum effects”
48. Business Goals are connected Architecture Characteristics are defined Decisions Records are documented Default Practices are documented and evolved Architecture Principles are continuously discussed, understood and evolved Building blocks of a Guidance-based approach Learning culture Effective nudging
49. Cultivating Architecture Birgitta Böckeler | @birgitta410