Diese Präsentation wurde erfolgreich gemeldet.
Die SlideShare-Präsentation wird heruntergeladen. ×

Agile Architecture Agile Dev Practices 2013 Keynote

Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Wird geladen in …3
×

Hier ansehen

1 von 50 Anzeige

Agile Architecture Agile Dev Practices 2013 Keynote

Herunterladen, um offline zu lesen

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.

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.

Anzeige
Anzeige

Weitere Verwandte Inhalte

Diashows für Sie (20)

Anzeige

Ähnlich wie Agile Architecture Agile Dev Practices 2013 Keynote (20)

Anzeige

Aktuellste (20)

Agile Architecture Agile Dev Practices 2013 Keynote

  1. 1. AGILE YET ANOTHER OXYMORON? ARCHITECTURE Adam Boczek @nativeagile @codecentric Agile 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 ARCHITECTURE AS AN ARCHITECTURAL PROCESS?
  5. 5. THE MOTIVATION BECAUSE OF BUSINESS FOR THE BUSINESS BASED ON INNOVATION
  6. 6. TYPES OF INNOVATION #EVOLUTIONARY #REVOLUTIONARY #DISRUPTIVE
  7. 7. VW BEETLE 1938-1978 EVOLUTIONARY INNOVATION
  8. 8. ELECTRIC CAR REVOLUTIONARY INNOVATION
  9. 9. INTERNET DISRUPTIVE INNOVATION
  10. 10. EVOLUTIONARY INNOVATION KEEPS YOUR BUSINESS RUNNING ONLY REVOLUTIONARY INNOVATION GUARANTEES NOWADAYS THE BUSINESS SUCCESS DISRUPTIVE INNOVATION CAN ALWAYS HAPPEN AND IS EASY TO EVALUATE
  11. 11. THEY (BUSINESS) HAVE THEIR OWN BUSINESS ARCHITECTURE* FACADES PROCESSES GOALS Communication ENTITIES * chris Reynolds
  12. 12. THEY (BUSINESS) MAY WANT TO CHANGE EVERYTHING FACADES PROCESSES GOALS Communication ENTITIES
  13. 13. THEY (BUSINESS) NEED US (IT)
  14. 14. DISCREPANCY BETWEEN 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 DEPLOYMENT http://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 Entities CLEAN Ext. Interfaces ARCHITECTURE* * Robert C. Martin (Uncle Bob)
  18. 18. Enterprise Business Rules Application Business Rules Controllers Interface Adapters Use Cases Frameworks & Drivers Entities INFLUENCE OF THE EVOLUTIONARY Ext. Interfaces INNOVATION ON THE IT
  19. 19. Enterprise Business Rules Application Business Rules Controllers Interface Adapters Use Cases Frameworks & Drivers Entities INFLUENCE OF THE REVOLUTIONARY Ext. Interfaces INNOVATION ON THE IT
  20. 20. Enterprise Business Rules Application Business Rules Controllers Interface Adapters Use Cases Frameworks & Drivers Entities INFLUENCE OF THE DISRUPTIVE Ext. Interfaces INNOVATION ON THE IT
  21. 21. AGILE PROCESS BASED “ARCHITECTURE” #Iterative #Incremental
  22. 22. LEAN PROCESS BASED „ARCHITECTURE“ #Defer Commitment and Decide As Late As Possible #Deliver As Fast As Possible #See and Optimize the Whole
  23. 23. AGILE ARCHITECTURE AS AN ARCHITECTURAL PROCESS?
  24. 24. AGILE ARCHITECTURE AS AN ARCHITECTURAL FLAVOR?
  25. 25. AGILE ARCHITECTURE TRANSPARENCY AND INSPECTION?
  26. 26. AGILE ARCHITECTURE ADAPTATION?
  27. 27. ARCHITECTURE* IS LIKE CONCRETE * By Ian Graham
  28. 28. YOU CAN’T REFACTOR ARCHITECTURE IF SOMETHING WENT WRONG YOU HAVE TO REDESIGN THE SYSTEM…
  29. 29. OR MAYBE…?
  30. 30. CLEAN ARCHITECTURE Controllers Use Cases Active Record Domain driven Design Entities CQRS AND MORE… Ext. Interfaces
  31. 31. CLEAN HYBRID ARCHITECTURE Controllers Controllers Controllers Use Cases Use Cases Use Cases Entities Entities Entities Active Record Domain Driven CQRS Design Ext. Interfaces
  32. 32. AGILE ARCHITECTURE AS AN ARCHITECTURAL FLAVOR?
  33. 33. AGILE ARCHITECTURE AS AN ARCHITECTURAL BEHAVIOR?
  34. 34. I HAD A DREAM TRANSPARENCY INSPECTION ADAPTATION
  35. 35. MEDICAL ROBOTS
  36. 36. HUMAN OPTIMIZING HUMAN HEALING
  37. 37. WHAT!?! SYSTEM THAT IS SELF-OPTIMIZING = PRO-ACTIVE SELF-HEALING = RE-ACTIVE
  38. 38. SELF-OPTIMIZING QUERY OPTIMIZER
  39. 39. SELF-OPTIMIZING LOAD BALANCER
  40. 40. SELF-HEALING WORKER PROCESS RECYCLING
  41. 41. AGILE ARCHITECTURE MEANS ARCHITECTURAL INTELLIGENCE ABILITY OF THE SYSTEM TO MONITOR, OPTIMIZE, AND HEAL ITSELF
  42. 42. FOUNDATION OF ARCHITECTURAL INTELLIGENCE PERFORMANCE AND SCALABILITY AVAILABILITY AND RESILIENCE EVOLUTION ACCESSIBILITY INTERNATIONALIZATION QUALITY LOCATION REGULATION ATTRIBUTES USABILITY SECURITY
  43. 43. FOUNDATION OF ARCHITECTURAL 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 SOURCING CAPTURE ALL CHANGES TO AN APPLICATION STATE 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 OF APPLICATION POSSIBILITIES #OPERATIONAL INTELLIGENCE #ACTIVE STRATEGY PATTERNS #ADAPTIVE USER EXPERIENCE #AUTOMATIC ERROR REMOVAL AND MORE…
  47. 47. ARCHITECTURAL INTELLIGENCE FOR OPERATIONAL INTELLIGENCE Adaptation Process Execution Platform Jee, Activity Process Control Center Inspection Big Data, Hadoop
  48. 48. AGILE ARCHITECTURE AS AN ARCHITECTURAL BEHAVIOR?
  49. 49. UP-FRONT ONLY PROCESS? HYBRID ARCHITECTURE FLAVOR? ARCHITECTURAL BEHAVIOR? INTELLIGENCE AGILE ARCHITECTURE
  50. 50. Adam Boczek management Consultant Agile Coach Enterprise Architect @nativeagile adam.boczek@codecentric.de http://codecentric.de @codecentric THANK YOU!

×