Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Cultivating Architecture in an Agile World

Cultivating Architecture in an Agile World

Agile Tour Vienna (Vienna, Österreich)
https://www.agiletourvienna.at/

Change is inevitable. So is software. Thus, agile practices and a DevOps mindset took over, driven by the need to holistically speed up the software development process. At the same time, we strive to establish autonomous development teams who can move as independently of each other as possible.

When the goal is to achieve speed and scalability, how does architecture governance look like in such a decentralised setup? If everything seems to change all the time, how to spot “the parts that are hard to change” and can they even exist? Why do architectural approaches sometimes become bottlenecks instead of providing value and why has “software architect” become a negative term for so many people?

There is no one-size-fits-it-all architecture and there is no dogmatic pseudo-agile “no architecture”. Good architectural work is still crucial, especially if we need to go fast. Prefering evolvability over predictability is key, but requires deep understanding how differnt dimensions of software projects interact with each other. We’ll discuss how to support the mechanics of evolution and we’ll look at some of the most common pitfalls that lead to disasters - and how to avoid them.

E6c61f085d7aceaf97b7bd00e9195514?s=128

SQUER Solutions

September 20, 2019
Tweet

Transcript

  1. None
  2. None
  3. None
  4. Perry and Wolf Ralph Johnson Martin Fowler Martin Fowler

  5. None
  6. None
  7. None
  8. Cumulative features Time Poor Architecture Good Architecture Martin Fowler: Design

    Stamina Hypothesis
  9. DevOps Research & Assessment LLC: State of DevOps Report 2019

  10. https://agilemanifesto.org/principles.html

  11. None
  12. None
  13. None
  14. None
  15. None
  16. None
  17. None
  18. Requirements Security Scalability Consistency Performance most negotiable least negotiable

  19. None
  20. Requirements Security Scalability Consistency Performance

  21. Requirements Security Scalability Consistency Performance

  22. None
  23. None
  24. None
  25. Ford, Parson, Kua

  26. atomic holistic triggered continuous

  27. You wanted a banana but what you got was a

    gorilla holding the banana and the entire jungle.
  28. atomic holistic triggered continuous cycle dependency check

  29. None
  30. atomic holistic triggered continuous cycle dependency check consumer driven contracts

  31. None
  32. None
  33. None
  34. atomic holistic triggered continuous cycle dependency check consumer driven contracts

    chaos monkeys
  35. None
  36. None
  37. atomic holistic triggered continuous cycle dependency check consumer driven contracts

    chaos monkeys architectural tests
  38. None
  39. None
  40. None
  41. atomic holistic triggered continuous cycle dependency check consumer driven contracts

    chaos monkeys architectural tests budgets
  42. None
  43. None
  44. None
  45. None
  46. None
  47. None
  48. • •

  49. atomic holistic triggered continuous cycle dependency check consumer driven contracts

    chaos monkeys architectural tests shadow availability budgets
  50. None
  51. None
  52. None
  53. None
  54. None
  55. None
  56. None
  57. Values/Principles/Practices

  58. None
  59. None
  60. None
  61. Values/Principles/Practices technology radar

  62. None
  63. Values/Principles/Practices technology radar ADRs

  64. Values/Principles/Practices technology radar ADRs

  65. None