Agile Architecture Agile Dev Practices 2013 Keynote

1,891 views
1,760 views

Published on

Keynote: Agile Dev Practices 2013
Adam Boczek, codecentric – “Agile Architecture – Yet Another Oxymoron?”

We at codecentric, as a technically focused agile organization, get in our projects quite often confronted with the assessment of a customer’s software architecture, or more precisely with the assessment of the existing solution architecture. In many cases it is ok for us to stay in this technical scope and not to touch other, much wider architectural concepts like e.g. enterprise architecture. However, due to the fact, that more and more organizations want to transform to a more agile organization, the alignment between IT and Business, and thus between IT-architecture and Business-architecture becomes much more relevant for us in our projects than in the past and causes many questions to arise. Can we talk in this context about agile architecture? And if so, is it a model of a system or maybe just a process of creating it? Or maybe both? How long can I delay my architectural decisions? Can I refactor my agile architecture? And so on…

In this talk I won’t give you perfect answers to all these questions, however I’m pretty sure I will open your eyes and let you create your own point of view.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,891
On SlideShare
0
From Embeds
0
Number of Embeds
643
Actions
Shares
0
Downloads
51
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Agile Architecture Agile Dev Practices 2013 Keynote

  1. 1. AGILE YET ANOTHER OXYMORON?ARCHITECTUREAdam Boczek@nativeagile@codecentricAgile Dev Practices 2013 | Keynote 06/03/2013| Potsdam | Germany
  2. 2. OXYMORON.#CONTROLLED CHAOS#OPEN SECRET#DARK LIGHT#LIVING DEAD#AGILE ARCHITECTURE?
  3. 3. PROCESS?FLAVOR?BEHAVIOR? AGILE ARCHITECTURE
  4. 4. AGILE ARCHITECTUREAS ANARCHITECTURALPROCESS?
  5. 5. THE MOTIVATIONBECAUSE OF BUSINESSFOR THE BUSINESSBASED ON INNOVATION
  6. 6. TYPES OF INNOVATION#EVOLUTIONARY#REVOLUTIONARY#DISRUPTIVE
  7. 7. VW BEETLE 1938-1978EVOLUTIONARYINNOVATION
  8. 8. ELECTRIC CARREVOLUTIONARY INNOVATION
  9. 9. INTERNETDISRUPTIVE INNOVATION
  10. 10. EVOLUTIONARY INNOVATIONKEEPS YOUR BUSINESS RUNNING ONLYREVOLUTIONARY INNOVATIONGUARANTEES NOWADAYS THE BUSINESS SUCCESSDISRUPTIVE INNOVATIONCAN ALWAYS HAPPEN AND IS EASY TO EVALUATE
  11. 11. THEY (BUSINESS) HAVE THEIR OWNBUSINESS ARCHITECTURE* FACADES PROCESSES GOALS Communication ENTITIES* chris Reynolds
  12. 12. THEY (BUSINESS) MAY WANT TOCHANGE EVERYTHING FACADES PROCESSES GOALS Communication ENTITIES
  13. 13. THEY (BUSINESS)NEED US (IT)
  14. 14. DISCREPANCYBETWEEN BUSINESS NEEDS AND IT DELIVERY Business Need for Change Agile IT Ability To Deliver Architecture? ’80s ’90s ‘00s ‘10s
  15. 15. WE HAVE OUR OWN IT ARCHITECTURE* Functionality Development Scenarios QUALITY DEPLOYMENT* Based on the concept by Philippe Kruchten
  16. 16. Enterprise FACADES PROCESSES Architecture GOALS Communication ENTITIES Functionality Development Scenarios QUALITY DEPLOYMENThttp://blog.codecentric.de/en/2013/01/business-architecture-for-it-dummies/
  17. 17. Enterprise Business Rules Application Business Rules Controllers Interface Adapters Use Cases Frameworks & Drivers EntitiesCLEAN Ext. InterfacesARCHITECTURE** Robert C. Martin (Uncle Bob)
  18. 18. Enterprise Business Rules Application Business Rules Controllers Interface Adapters Use Cases Frameworks & Drivers EntitiesINFLUENCE OFTHE EVOLUTIONARY Ext. InterfacesINNOVATION ON THE IT
  19. 19. Enterprise Business Rules Application Business Rules Controllers Interface Adapters Use Cases Frameworks & Drivers EntitiesINFLUENCE OFTHE REVOLUTIONARY Ext. InterfacesINNOVATION ON THE IT
  20. 20. Enterprise Business Rules Application Business Rules Controllers Interface Adapters Use Cases Frameworks & Drivers EntitiesINFLUENCE OFTHE DISRUPTIVE Ext. InterfacesINNOVATION ON THE IT
  21. 21. AGILE PROCESSBASED “ARCHITECTURE”#Iterative#Incremental
  22. 22. LEAN PROCESSBASED „ARCHITECTURE“#Defer Commitment and Decide As Late As Possible#Deliver As Fast As Possible#See and Optimize the Whole
  23. 23. AGILE ARCHITECTUREAS ANARCHITECTURALPROCESS?
  24. 24. AGILE ARCHITECTUREAS ANARCHITECTURALFLAVOR?
  25. 25. AGILE ARCHITECTURETRANSPARENCY AND INSPECTION?
  26. 26. AGILEARCHITECTUREADAPTATION?
  27. 27. ARCHITECTURE* IS LIKE CONCRETE* By Ian Graham
  28. 28. YOU CAN’T REFACTORARCHITECTUREIF SOMETHING WENT WRONGYOU HAVE TOREDESIGN THESYSTEM…
  29. 29. OR MAYBE…?
  30. 30. CLEANARCHITECTURE Controllers Use CasesActive RecordDomain driven Design EntitiesCQRSAND MORE… Ext. Interfaces
  31. 31. CLEAN HYBRIDARCHITECTURE Controllers Controllers Controllers Use Cases Use Cases Use Cases Entities Entities Entities Active Record Domain Driven CQRS Design Ext. Interfaces
  32. 32. AGILE ARCHITECTUREAS ANARCHITECTURALFLAVOR?
  33. 33. AGILE ARCHITECTUREAS ANARCHITECTURALBEHAVIOR?
  34. 34. I HAD A DREAMTRANSPARENCYINSPECTIONADAPTATION
  35. 35. MEDICAL ROBOTS
  36. 36. HUMANOPTIMIZING HUMAN HEALING
  37. 37. WHAT!?!SYSTEMTHAT ISSELF-OPTIMIZING = PRO-ACTIVESELF-HEALING = RE-ACTIVE
  38. 38. SELF-OPTIMIZINGQUERYOPTIMIZER
  39. 39. SELF-OPTIMIZINGLOADBALANCER
  40. 40. SELF-HEALINGWORKERPROCESSRECYCLING
  41. 41. AGILE ARCHITECTUREMEANSARCHITECTURALINTELLIGENCE ABILITY OF THE SYSTEM TO MONITOR, OPTIMIZE, AND HEAL ITSELF
  42. 42. FOUNDATION OFARCHITECTURAL INTELLIGENCE PERFORMANCE AND SCALABILITY AVAILABILITY AND RESILIENCE EVOLUTION ACCESSIBILITY INTERNATIONALIZATIONQUALITY LOCATION REGULATIONATTRIBUTES USABILITY SECURITY
  43. 43. FOUNDATION OFARCHITECTURAL INTELLIGENCE REVERSIBLE COMPUTATION* LOGICAL REVERSIBILITY Initial Final state state Configuration With State Transition* Lange, McKenzie, Tapp
  44. 44. SIMPLIFICATION#ONE-TO-ONE FUNCTIONS#INPUT AND OUTPUT VALUES#TIMESTAMPS T1 | State 1 T2 | State 2 T3 | State 3 T3 | State 3 Storage T2 | State 2 T1 | State 1
  45. 45. EVENT SOURCINGCAPTURE ALL CHANGES TO AN APPLICATIONSTATE AS A SEQUENCE OF EVENTS* T1 | State 1 T2 | State 2 T3 | State 3 T3 | State 3 T3 | State 3 T3 | State 3 Consumer A T2 | State 2 Consumer B T2 | State 2 Consumer C T2 | State 2 T1 | State 1 T1 | State 1 T1 | State 1* M. Fowler
  46. 46. PLENTY OFAPPLICATIONPOSSIBILITIES #OPERATIONAL INTELLIGENCE #ACTIVE STRATEGY PATTERNS #ADAPTIVE USER EXPERIENCE #AUTOMATIC ERROR REMOVAL AND MORE…
  47. 47. ARCHITECTURAL INTELLIGENCEFOR OPERATIONAL INTELLIGENCE Adaptation Process Execution Platform Jee, Activity Process Control Center Inspection Big Data, Hadoop
  48. 48. AGILE ARCHITECTUREAS ANARCHITECTURALBEHAVIOR?
  49. 49. UP-FRONT ONLYPROCESS? HYBRID ARCHITECTUREFLAVOR? ARCHITECTURALBEHAVIOR? INTELLIGENCE AGILE ARCHITECTURE
  50. 50. Adam Boczek management Consultant Agile Coach Enterprise Architect @nativeagile adam.boczek@codecentric.de http://codecentric.de @codecentricTHANK YOU!

×