Architecture is perceived as a heavy-weight activity which does not fit well into an Agile process, so many teams start without it, just to find themselves re-doing the software later because the code structure was not good enough to support maintainability and growth. Because the domain was not understood in the first place, the code that reflects it needs to be changed beyond the point of refactoring, and when that happens some architectural decisions are to be made. That defers the initial software design to a later point, introducing unnecessary delays and costs in the project.
In this presentation filmed during QCon 2007, Coplien and Henney describe how to start with enough architecture to ensure long term success of the project.
Community comments
I love this presentation!
by Sadek Drobi,
Interesting...
by Ilja Preuß,
Re: Interesting...
by Sadek Drobi,
Agile Fragile Architecture summary
by Martien van Steenbergen,
Pity no write up...
by Rob Brown,
Fantastic
by Peter Andersen,
Architecture can't be only made of hope!
by Giovanni Panzeri,
I love this presentation!
by Sadek Drobi,
Your message is awaiting moderation. Thank you for participating in the discussion.
Don’t Play dumb! If you know some stuff celebrate that you know it and put a peg in the ground.
To do agile you should be standing on a firm foundation.
Stability != Static
Interesting...
by Ilja Preuß,
Your message is awaiting moderation. Thank you for participating in the discussion.
though a little bit long-winded.
I also was a bit disappointed that they confuse the adjective "agile" with the *name* "Agile Software Development". Scrum, DSDM and XP are instances of the latter, which is *defined* by the Agile Manifesto.
Re: Interesting...
by Sadek Drobi,
Your message is awaiting moderation. Thank you for participating in the discussion.
Agile software and more precisely Scrum have existed some time before the Agile Manifesto. So it is allright to talk about agile software without referring to the manifesto. Jim for instance AFAIK is one of the pioneers of agile developpement, yet he did not take a part in the Agile Manifesto meeting.
Agile Fragile Architecture summary
by Martien van Steenbergen,
Your message is awaiting moderation. Thank you for participating in the discussion.
"Transcript" below is a copy of wiki.aardrock.com/Agile_Architecture_is_not_Fra...
Free interpretation of [www.infoq.com/presentations/Agile-Architecture-... InfoQ: Agile Architecture Is Not Fragile Architecture]
By James Coplien and Kevlin Henny.
Pity no write up...
by Rob Brown,
Your message is awaiting moderation. Thank you for participating in the discussion.
I liked the presentation with many things mentioned that I liked to hear about but I just can't go back and watch or jump around the video trying to find them again - would have liked a transcript :(
Fantastic
by Peter Andersen,
Your message is awaiting moderation. Thank you for participating in the discussion.
Great work James and Kevlin!
/Peter
www.codelean.com
Architecture can't be only made of hope!
by Giovanni Panzeri,
Your message is awaiting moderation. Thank you for participating in the discussion.
I found many concepts of this presentation while I was reading "Lean Architecture for SW Agile development". I think that the best way to describe the Architecture, is this quote ".. a good up-front architecture can reduce re-factoring. To argue that you should start with a casually or briefly considered design and then let re-factoring bring you to good code structure recalls an old adage ....: Hope is not a plan"