Arismore - Réussir la transition vers la continuous Architecture
- 2. © Arismore 2 • Why continuous architecture • What is continuous architecture • How to do continuous architecture • Impacts on organization and architects
- 3. © Arismore 4 The issue HTTP://XKCD.COM/974/
- 4. © Arismore 5 Let’s ride together
- 5. © Arismore 6 “I'm never in favor of writing code poorly, but I am in favor of writing code to reflect your current understanding of a problem even if that understanding is partial.” Ward Cunningham
- 7. © Arismore 8 Why now Agility is feedback
- 8. © Arismore 9 What is Continuous Architecture Continuous architecture is architecture when you stop “Big Up Front Design Only” Continuous architecture is architecture with shorter and richer feedback loops
- 9. © Arismore 10 Why continuous architecture is better? Create feedback to enhance your current understanding of the problem
- 10. © Arismore 11 Why continuous architecture is better?
- 11. © Arismore 12 Predefined Sequence is evil Sequence is not the evil Predefined sequence is the evil
- 12. © Arismore 13 Beyond predefined sequence Vision Analyse Scenario Refactor Govern Decide Learn TestMeasure Validate Situational intelligence and playbooks
- 13. HOW
- 14. © Arismore 15 10+ key practices for Continuous architecture 1. Architecture is Collaborative 2. Decisions: defer and respect 3. Measure 4. Shared governance log 5. Principles over rules 6. Open repository mandatory 7. Information Not documents 8. Multiply viewpoints 9. Use patterns wisely 10. Manage debt 11. Automate more
- 15. © Arismore 16 10+ key practices for Continuous architecture Architecture is Collaborative You never talk alone
- 16. © Arismore 17 10+ key practices for Continuous architecture Decisions: Defer and Respect Create options and limit irreversibility
- 17. © Arismore 18 10+ key practices for Continuous architecture Measure Measure the fit for purposeness of your architecture
- 18. © Arismore 19 10+ key practices for Continuous architecture Shared governance log Build on transparency
- 19. © Arismore 20 10+ key practices for Continuous architecture Principles over rules Principles inspire, rules limit
- 20. © Arismore 21 10+ key practices for Continuous architecture Open repository mandatory Share and reuse information, publish early drafts
- 21. © Arismore 22 10+ key practices for Continuous architecture Information Not documents Have a trusted source of truth
- 22. © Arismore 23 10+ key practices for Continuous architecture Multiply viewpoints Involve more stakeholders and capture more concerns
- 23. © Arismore 24 10+ key practices for Continuous architecture Use patterns wisely Do better design up front freely and fastly
- 24. © Arismore 25 10+ key practices for Continuous Architecture Manage debt Create awareness and pay it regularly
- 25. © Arismore 26 10+ key practices for Continuous architecture Automate more Concentrate on your value added activities
- 26. Impacts
- 27. © Arismore 28 Impact on organization
- 28. © Arismore 29 Impact on Architects Never ask permission to do your job correctly
- 29. © Arismore 30 Where to start?
- 30. © Arismore 31 You’ve been warned
- 31. © Arismore 32 Questions? Thank you
- 32. Contact : Renaud PHELIZON Manager 137, bureau de la Colline 92213 Saint-Cloud Cedex - France Direct Line : +33 1 78 16 48 30 – Mobile : +33 6 03 52 22 36 Standard : + 331 55 57 21 60 – Fax : +33 1 55 57 04 45 E-mail : renaud.phelizon@arismore.fr 33
Editor's Notes
- #6: Crib Goch
- #9: Continuous architecture or agile architecture or Emergent Design or Evolutionnary Architecture, all these terms refers to the same topic and to the same idea : Stop doing only Big Up Front Design There are not new subjects, some are here for more than 10 years or more, many are related to « agile approach » There are many different answers, approaches, “philosophy” to the same problem If you do only Big Up Front Design, you never enhance your design based on your new understanding. Briefly, BUFD don’t learn. It’s true that these subjects become more on the radar of the IT community at large. Why now Because we need (I mean our bussiness) need to be agile. And what is the main point in agile: feedback loops
- #10: So what is Continuous Architecture Continous architecture is a way to define, build and refactor the architecture of a system to reflect the current understanding of the problem and the fit for purpose of the designed solution « Continuous architecture « highlights the fact that you continuously improve your understanding and that you should always improve the architecture of the system It's not technology driven, even if it's probably technology accelerated
- #11: Continuous architecture is better because you benefit from feedback
- #12: Good enough architecture Always improving Just enough architecture effort Just in time architecture effort Because of no Big Up Front Design Only You will be always « value driven » Better focus on the right thing You will produce « just enough architecture » Better use of architecture ressource You will produce just in time architecture Better reflect of current understanding
- #13: Sequence is not the evil Predefined sequence is the evil Waterfall is a predefined sequence In some way, agile (eg scrum) is also a predefined sequence What if it is not predefined sequence? Adapt situational awareness Situational intelligence combines traditional situational awareness with the collective intelligence of those at the center of a situation, resulting in a dynamic process in which data is gathered and interpreted and the information is shared.
- #14: More power More responsibility Based on what we already know and what we learned, what is the best thing to do now ?
- #17: Collaborative modelling & deciding Information sharing Transparency of decision Collective ownership of design No single source of good ideas, no monopoly of innovation Pair architecturing Community of architecture
- #18: Decision create inflexibility, the longer you should defer a decision, the longer you should benefit from feedback Defer the decision to the last responsible moment How can I make my decision reversible? Do I need to make this decision? What can I do allow me to defer the decision? Decision are temporary in continuous architecture, but that is why it is even more important to respect them.
- #19: Measure the value proposition of your architecture Measure usages Measure technical debt
- #20: Decisions are base for next action, not secret Create a space where each stakeholder may have the current decisions
- #21: Principles are guidelines, rules are constraints Principle inspires, rule limits Principle is strong and stable, rule is weak and unstable
- #22: Share information comprehensively Structure and unstructure Classify and unclassify Test new solutions (analytics, machine learning) NB: It’s just an information architecture problem, we should be good at it
- #23: Why we love documents: easy to mail, easy to print, “one stop shopping” Problems with document: dissemination, uncontrolled versions, people don’t read document anymore Solution: share information on the network yes, it is possible
- #24: Multiply viewpoints will allow to To involve more stakeholders To capture more concerns To manage granularity level of analysis To be rightly focus To be more easily understood
- #25: Don’t reinvent Do better design up front freely and fastly Be wise, there are antipatterns
- #26: Create awareness on debt Define some metrics Give insights not fear Pay it regularly
- #27: Create awareness on debt Define some metrics Give insights not fear Pay it regularly
- #29: If agility is truly important, the organization should adapt Continuous governance « decision on demand »
- #30: New mindset Architecture Craftmanship !
- #31: It’s up to you Is there willingness? Where is energy?