Tweet
Tweet

Slide 1

Slide 1 text

CULTIVATING ARCHITECTURE Birgitta Böckeler @birgitta410 | Martin Fowler @martinfowler

Slide 2

Slide 2 text

CULTIVATING ARCHITECTURE What?

Slide 3

Slide 3 text

http://martinfowler.com/ieeeSoftware/whoNeedsArchitect.pdf

Slide 4

Slide 4 text

Shared understanding Hard to change The important stuff … whatever that is

Slide 5

Slide 5 text

CULTIVATING ARCHITECTURE Why?

Slide 6

Slide 6 text

Cumulative features Time No / Poor Architecture Good Architecture

Slide 7

Slide 7 text

CULTIVATING ARCHITECTURE

Slide 8

Slide 8 text

https://agilemanifesto.org/

Slide 9

Slide 9 text

Autonomy Trust Voice Westrum Organizational Culture Software Delivery Performance Organizational Performance Forsgren et al, State of DevOps Report 2018 https://cloudplatformonline.com/2018-state-of-devops.html predictive relationship

Slide 10

Slide 10 text

“We need some governance”

Slide 11

Slide 11 text

manipulate control rule restrain guide serve as deciding principle have decisive influence Exert a determining or guiding influence to govern

Slide 12

Slide 12 text

guide serve as deciding principle have decisive influence Exert a determining or guiding influence rule to govern

Slide 13

Slide 13 text

Business Architecture Requirements Decisions Practices Principles

Slide 14

Slide 14 text

Organization Unit Unit Unit Team Team Team Team Team Team Team Team Team

Slide 15

Slide 15 text

Decisions Practices Business Architecture Requirements Principles

Slide 16

Slide 16 text

Push & pull the business context

Slide 17

Slide 17 text

No content

Slide 18

Slide 18 text

Decisions Practices Business Architecture Requirements Principles

Slide 19

Slide 19 text

Architecture Requirements

Slide 20

Slide 20 text

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

Slide 21

Slide 21 text

Prioritise Offline Availability Portability Data privacy … …

Slide 22

Slide 22 text

Decisions Practices Business Architecture Requirements Principles

Slide 23

Slide 23 text

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

Slide 24

Slide 24 text

Statement Team Decisions System Qualities Team Decisions Team Decisions Team Decisions guide lead to Require- ments

Slide 25

Slide 25 text

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.”

Slide 26

Slide 26 text

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

Slide 27

Slide 27 text

http://engineering-principles.onejl.uk

Slide 28

Slide 28 text

Sam Newman, “Building Microservices” Rationale Implications

Slide 29

Slide 29 text

Facts over Opinions Hypothesis-driven development Data democratization Enter new market X Customer centricity

Slide 30

Slide 30 text

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

Slide 31

Slide 31 text

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?

Slide 32

Slide 32 text

How to find your principles?

Slide 33

Slide 33 text

Goals What’s holding us back today? What’s moving us forward today? Risks Strengths Opportunities Threats Weaknesses Cross-team relevance Business Architecture Requirements

Slide 34

Slide 34 text

No content

Slide 35

Slide 35 text

Decisions Practices Business Architecture Requirements Principles

Slide 36

Slide 36 text

Technology Radar https://opensource.zalando.com/tech-radar/

Slide 37

Slide 37 text

Promising, experimenting with this on one or more teams TRIAL Neal Ford, “Using the ThoughtWorks Technology Radar to track governance” Proven to work within this enterprise, well supported ADOPT Evaluating for potential experiments, under active research ASSESS Deprecated, don't start new projects using this HOLD

Slide 38

Slide 38 text

Sensible Defaults

Slide 39

Slide 39 text

Decisions Practices Business Architecture Requirements Principles

Slide 40

Slide 40 text

Decision Records http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions

Slide 41

Slide 41 text

CULTIVATING ARCHITECTURE How to make it effective?

Slide 42

Slide 42 text

Autonomy Trust Voice Westrum Organizational Culture Software Delivery Performance Organizational Performance Forsgren et al, State of DevOps Report 2018 https://cloudplatformonline.com/2018-state-of-devops.html predictive relationship Retrospectives Climate for Learning

Slide 43

Slide 43 text

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

Slide 44

Slide 44 text

Reflect & Iterate Talk to each other Record history

Slide 45

Slide 45 text

“I’m ‘just’ a developer - what can _I_ do?” Captured by https://github.com/lolcommits/lolcommits

Slide 46

Slide 46 text

Organization Unit Unit Unit Team Team Team Team Team Team Team Team Team

Slide 47

Slide 47 text

Decisions Practices Business Architecture Requirements Principles

Slide 48

Slide 48 text

CULTIVATING ARCHITECTURE Birgitta Böckeler @birgitta410 | Martin Fowler @martinfowler

Slide 49

Slide 49 text

Resources ● „Who needs an architect“ http://martinfowler.com/ieeeSoftware/whoNeedsArchitect.pdf ● „State of DevOps report 2018“ https://cloudplatformonline.com/2018-state-of-devops.html ● „Using Software Architecture Principles in Practice“ https://www.slideshare.net/EoinWoods1/using-software-architecture- principles-in-practice ● TOGAF‘s definition of Architecture Principles http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap29.html ● “Using the ThoughtWorks Technology Radar to track governance” https://www.thoughtworks.com/insights/blog/using- thoughtworks-technology-radar-track-governance ● Public examples of principles ○ John Lewis http://engineering-principles.onejl.uk/ ○ Scout24 https://github.com/Scout24/scout24-engineering-values-and-principles ○ 12 factor app https://12factor.net/ ○ UK Government Digital Service https://www.gov.uk/guidance/government-design-principles ○ Zalando https://github.com/zalando/engineering-principles#zalandos-engineering-and-architecture-principles ● Public examples of organizational Tech Radars ○ AutoScout24 https://github.com/Scout24/as24-tech-radar ○ Zalando https://opensource.zalando.com/tech-radar/ ○ Porsche https://medium.com/porschedev/technology-radar-vol-2-4833fb31e2fd