February 4, 2013   1
    Agile Architecture – 15 Minutes     Game Definition – 15 Minutes     Round One – 30 Minutes     Debrief – 10 Minut...
    International Standard Definition:     The fundamental concepts or properties of a system in its      environment em...
    Functional Definition:     Architecture provides a vision and path for the creation of      services and application...
    Every system has an architecture     Every system needs a shared vision                     Agile Architecture is de...
SYSTEM COMPLEXITY                                       HIGH                                                  Architect   ...
SYSTEM COMPLEXITY                                                 Verbal                                       HIGH       ...
    Conway’s Law       Your architecture will resemble your organization     Therefore, as an architect you should:    ...
    Architects provide the technical background      for business decisions     Every decision involves tradeoffs:      ...
February 4, 2013   10
    Define how you architect, for example:       DRY – Don’t Repeat Yourself       Single Responsibility       Test Dr...
February 4, 2013   12
    Be the architect, but architect as a team              "An army is a team. It lives, eats, sleeps, fights as a       ...
    Make decisions, now!             “Be willing to make decisions. Thats the most             important quality in a goo...
    Provide a vision, not micro-management             “Never tell people how to do things. Tell them what             to...
    Plan, but not too much               “A good plan executed today is better than a               perfect plan executed...
    Listen to your people               “A leader is a [person] who can adapt               principles to circumstances.”...
Upcoming SlideShare
Loading in …5
×

Be an agile architect

982 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
982
On SlideShare
0
From Embeds
0
Number of Embeds
286
Actions
Shares
0
Downloads
14
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Trade-offsChoices limit optionsStrategy mattersChange happens
  • Be an agile architect

    1. 1. February 4, 2013 1
    2. 2.  Agile Architecture – 15 Minutes  Game Definition – 15 Minutes  Round One – 30 Minutes  Debrief – 10 Minutes  Round Two – 25 Minutes  Debrief – 25 MinutesFebruary 4, 2013 2
    3. 3.  International Standard Definition:  The fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution. Source: http://www.iso-architecture.org/42010/defining-architecture.htmlFebruary 4, 2013 3
    4. 4.  Functional Definition:  Architecture provides a vision and path for the creation of services and applications which conform to the fundamental principles of the system’s design.February 4, 2013 4
    5. 5.  Every system has an architecture  Every system needs a shared vision Agile Architecture is deciding when you conceive the architecture and how you will share it?February 4, 2013 5
    6. 6. SYSTEM COMPLEXITY HIGH Architect Architect Just-In-Time Early Emergent Architect LOW Architecture Just-In-Time SMALL < 10 LARGE > 50 TEAM SIZEFebruary 4, 2013 6
    7. 7. SYSTEM COMPLEXITY Verbal HIGH And Document Document Document LOW Verbal And Verbal SMALL < 10 LARGE > 50 TEAM SIZEFebruary 4, 2013 7
    8. 8.  Conway’s Law  Your architecture will resemble your organization  Therefore, as an architect you should:  Provide for loose coupling  Preserve optionality  Design for reuse  Create APIs and SLAsFebruary 4, 2013 8
    9. 9.  Architects provide the technical background for business decisions  Every decision involves tradeoffs:  Jumping on short-term business benefits creates technical debt  Pursuing a tactical upgrade postpones rebuilding from scratch  Preventing hacks means spending time enforcing the architectureFebruary 4, 2013 9
    10. 10. February 4, 2013 10
    11. 11.  Define how you architect, for example:  DRY – Don’t Repeat Yourself  Single Responsibility  Test Driven  Hands-on, no ivory tower architects  Continuous Everything  Developer to Production Tools  Empowered Teams  Agile ManifestoFebruary 4, 2013 11
    12. 12. February 4, 2013 12
    13. 13.  Be the architect, but architect as a team "An army is a team. It lives, eats, sleeps, fights as a team. This individuality stuff is a bunch of bullsh*t." ~ General George S. PattonFebruary 4, 2013 13
    14. 14.  Make decisions, now! “Be willing to make decisions. Thats the most important quality in a good leader.” ~ General George S. PattonFebruary 4, 2013 14
    15. 15.  Provide a vision, not micro-management “Never tell people how to do things. Tell them what to do and they will surprise you with their ingenuity.” ~ General George S. PattonFebruary 4, 2013 15
    16. 16.  Plan, but not too much “A good plan executed today is better than a perfect plan executed at some indefinite point in the future.” ~ General George S. PattonFebruary 4, 2013 16
    17. 17.  Listen to your people “A leader is a [person] who can adapt principles to circumstances.” ~ General George S. PattonFebruary 4, 2013 17

    ×