May 11 2010, co-located with The Open Group conference
Two main topics were selected.
1. Implementing TOGAF - what parts work. Lessons learned. Use of TOGAF with other frameworks.
One approach that worked was to use TOGAF with TM Forum frameworks, even though we are in the manufacturing industry, not telecommunications.
One of the hard things as you go round the ADM is finding business architects for Phase B.
Our company made the conscious decision to deploy SOA, later we found that much of what we were doing matched TOGAF 9. We used a spreadsheet as as repository, and it worked well, later we transferred it into a tool and generated a metamodel.
Is there value to be gained from generalising architectures for reuse? A wiki can be a good way to start your enterprise continuum/ architecture repository. Central governance is necessary when deploying, it gives a necessary feedback loop.
We have to work out how to connect RUP processes with our TOGAF deliverables.
Often using TOGAF gives a formal process based on many man years of development so is worth putting in place up front
Could you live without doing it?
You should start with a repository, keep it simple, create a wiki or use a spreadsheet
Create a metamodel , use the metamodel as the way you record the information you need to know about your artefacts
Hire somebody who is TOGAF trained or TOGAF knowledgeable
You need to have a working governance framework to keep all EA deliverables up to date
2. Selling EA to Senior Managers
Don't use the A word
Don't boil the ocean
Phrase IT solution ideas in their terms, in terms of obstacles to delivery
Talk about quick wins
Get them to describe their vision of how they should be working and relate it to what they do architecturally
Can we reconcile disparate visions? And present it back as an EA piece of work