The following are notes from the ITANA Discussion Session 2012 at EDUCAUSE.

Attendees:  We had 17 people attend the discussion session.  The attendees where mixed about 50:50 between people who were brand new to ITANA, just learning about ITANA for the first time and those who had heard about ITANA and were at least lurkers on the list. 

Agenda:  Jim introduced ITANA and discussed what we are about and how people can engage.  We then used the ITANA Capability Map to work through the four strategic capabilities.  We discussed "How ITANA could better meet these capabilities".  Below is the outcome of that conversation.   Jim then closed by pointing out that we were using an EA best practice by using a capability map to plan our strategy.

The Strategic Capabilities for ITANA:

See the Capability Map and its discussion pages on the ITANA web site: http://itana.org/capability-map/

Knowledge Transfer

  1. Case studies
  2. Vendors roadmaps and architectural change
  3. "Body of knowledge" framework HE methodology
  4. Rotating webinar series on local practices
  5. Document standards/artifacts for projects
  6. Marketing talking points. Re: value of architecture to business

Outreach

  1. How to sell architecture to the campus
  2. Demonstrating architecture to developers, leaders: showing its not just delay
  3. Educause live/partnerships
  4. Presenting with other professional groups
  5. Marketing to the b usiness the value of architecture

Community

  1. Informal knowledge transfer: mentors, case studies
  2. Personal case studies
  3. Organizational group training. Ad hoc

Practice

(wg= Working Group, cs = Case Study, pg = Peer Group)

  1. Tool to assess maturity and a scan/survey of higher ed institutions and their maturity level (wg)
  2. templates for evaluating components of architecture (artifacts that guide review (cs, wg)
  3. Tools for ARB's (cs, wg)
  4. Templates for project team (cs, wg)
  5. How do you start up an "Architecture" Get started guide wg
  6. How do you find the right point of engagement (strategic rather than reactive) pg
  7. Governance and architecture
  8. How to leverage faculty experts for help
  • No labels