Agenda:
Tuesday 11/20/2012 @ 11 EST.
1) Get everyone on Google Hangout
2) Introductions. Tell us a little bit about yourself
Brenda Reeb - Data Architect, Rochester
Bruce Alexander - Enterprise Arch, Michigan State, Startings a couple of next projects with EA getting involved at the beginning. Exciting time!
Jim Phelps - Wisconsin - Madison, Chair of ITANA
Wayde Nie - McMaster U, just starting out an ERP project
Kasia Azzara, Columbia
Chris Eagle, Michigan
Russ Connacher, UC - Berkeley. Here to ginve out how to get the ship sailing”
3) Discussion:
Question: is it like a capability map?
Answer: that is one kind of an anchor model
The article doesn’t give examples. But does say a lot of the value is in the actual *creation* of the model.
Link to the article
The author didn’t say *who* to include when creating one.
Brenda: include people who have a really good sense of how the organization operates - but the author didn’t name a role.
Bruce: The Anchor model may change over time. Your first anchor model may not be the same model you want as you mature your understanding of the topic.
Russ: What level do you start at? Invite the V.P?
Jim: has done a couple of them - below the director level “really bright managers”. Important to have “people who are trusted” create the model. -- “Who did this? Oh. They know what they’re talking about”
How much can the architect speed up the cycle? Jim: The team really needs to internalize the thought process - and that takes time.
Brenda gave an example of a local grocery store that listed all the touch points of customers, and created an AHA moment - they could see all the customer experiences and no data integration between them.
Chris - told story of drawing ad hoc capability diagram on whiteboard to move discussion away from technology-level discussion.
Russ: Should Anchor model be the first tool out? or just a tool in a tool box. Brenda: just one tool.
Jim suggested a screen-to-screen to talk about single page diagrams as an EA tool.
Chris - use it when you need an “anchor”
Russ: Berkeley going through an IT reorg towards customer domains. Large chunks are easy, but details are hard. Anchor model could be used for that.
Jim will send out UW-M’s question framework.
http://eadirections.wordpress.com/2011/11/07/ea-tips-anchor-models/
Jim showed decision diagram used for “whether to involve architecture into a new project”
Jim suggests that we create a working group to provide tools that ITANA members could use to get EA started on campus - look for case studies to use.
Might not be just starting up EA - but starting up a new domain on campus.
Link to Jim’s examplehttps://docs.google.com/document/d/13wAbcNCOvN9dgpP4JwjeA2wm4hTiAOkfOlWr8hSGu88/edit?pli=1
Kasia - Colombia has very little governance. So hard to get EA buy-in. Jim gave example of lining up 2 key non-IT people who pushed the creation of the Arch Review Board. Jim also referred to Paul Hobson’s Educause presentation on a continuum of governance from ‘little g’ to ‘big G’ governance.
Building influence is really important in Higher Ed.
Brenda - working on influence all the time (50% of the work). Sense of timing is really important.
Jim - future discussion could be “influence scan”. Identifying levels of influence and where they are on spectrum from supporter to detractor.
Russ - let’s get a group of interested people, and select a chairman from that group.