Mick Adams set opening context “Systemic tsunami across the financial system in 2008 will be felt by business for years to come.”
The impact reflected in business driver categories: cost reduction, risk avoidance, value, now time-market. Corresponding IT response: meet target, practical and pragmatic, demonstrable, and now.
“The modular structure of TOGAF 9 allows organizations to maximize returns now”.
Mapping of IT response to TOGAF: meet target = business drivers/vision; where is it = systemic options evaluation; practical and pragmatic = customized to business cycle; now = iterative quick and dirty.
“Enterprise architecture delivery takes many forms”. “Architecture is being realized in a multitude of ways within organizations of all types”.
Continuum diagram with two aspects: top is architecture framework & method from “pragmatic light touch” to “detailed rigorous”. Bottom is organizational complexity from “straightforward” to “Complex”.
Message is pragmatic light touch works best with a straightforward organization. [I would add straightforward & mature (business & engineering discipline are in place and valued).
Now, Mick is speaking of TOGAF 9 sections and selecting artifacts & processes that match your situation. Similar thoughts expressed by Chris Forde of Amex this morning.
Transitioned to Architecture Development Method (ADM crop circle) and how to select a atypical starting point and then iterate through. [This (modularity) is one of the new concepts in TOGAF 9 that most appeals to me.]
“Don’t do everything all at once. Only do what you have to.” “If there is any debate over [a portion] don’t do it and see what happens”.
In respect to customizing TOGAF 9, “the architect must drive adoption by industrializing how value will be unlocked”. “It’s your choice how to realize the value; we do recommend using practicable timeliness that match business demand”.
[I’m thinking the modularity of TOGAF 9 forces the architect to be an architect, not a documenter. This is a very good thing for architects and the organizations they support. To pick and choose the right path(s) and deliverables, you need to “get” what you are doing.]
Good, business-focused, pragmatic messages from Mick Adams of Capgemini.
