Jim Phelps from Wisconsin (the other UW) is talking about different models of enterprise architecture implementations.
– Informal / Ad hoc architecture
– Isolated architect – buried in one group
– Federated architecture – architecture deputies around campus working together
– Head architect with Domain architects
– central architecture review of projects.
Identity management seems to be the gateway architecture. Portfolio and project management seems to be an entry point for architectural planning.
Laws seem to motivate.
Mark Poepping from Carnegie Mellon is talking about “Architecture to Action” – what does architecture mean in terms of action – the measure of architecture is in its practical ability to help do better work in a better way. Architecture is social work – about building momentum over time, through a portfolio of success and reputation. But how do we measure the success of architects and architecture?
Ways to gain traction – how is architecture connected?
Some models –
– connected by leadership (CIO/CTO/Boss decrees/enforces)
– connected by process (Portfolio management for projects, business process review (continuing service support))
– connected behind the scenes (ad hoc discussions, alignment, social work)
(Oren comments that this last bullet should be “connected by relationships”)
Areas to leverage traction
– WHere to apply architecture (scope of influence)
– some models:
– enterprise plus research support
There’s a lot of discussion that bubbled out of the back channel now on the relative responsibilities of architects to do actual operational work vs. just taking the institutional view (or as Shel characterized it is “working in the ivory tower”).
Elements of traction
1. what we do (operating architecture, how does it work?)
2. How we think about it (models pictures, how to organize thinking)
3. How we talk about it
4. What we could do (benchmark, research experiment, fasibility, familiarity)
5. What we should do ((default postures, formative guidance)
6. what we shoudld be concerned about these days
7. How should something be done
8. How’s it goin?
Technorati Tags: CSG, CSG-Spring-2007, IT-architecture, architecture