Attendees:  Scott Fullerton (UW-Madison), Paul Hobson (UBC), Leo Fernig (UBC), Vincent Aumont (UBC), Rich Stevenson (UMUC), Sharif Najim (Notre Dame), Bob Winding (Notre Dame), Christian Vinten-Johansen (PSU), Mark Rank (UW-Milwaukee), Jim Phelps (UW-Madison).

Rules:

  1. Topics were submitted via a web form.  Each topic needed a leader and a scribe.
  2. Topic leaders had 5 minutes to pitch their idea to the attendees.
  3. After the topics were pitched, there was a brief round of clarifying questions.
  4. Attendees then voted for topics.  Each attendee had three votes.  They could use all the votes on one topic or spread them across multiple topics.
  5. The topic with highest vote went first.  We worked as a single large group.

Topics:

The two topics that were selected were:

Write-ups

Solution Path Type Diagrams for ITANA

Jim presented a walk through of the concept that Gartner are presenting as a Solution Path Diagram, which seems a natural extension to older methods already presented/used by other analyst groups, e.g. Burton Group Decision Point methods. Discussion of a number of potential examples ensued, including potential examples around perhaps answering question like 'how do I develop an IT Roadmap'.  Some attendees have similar views developed in BPMN already, however we are looking to provide something that is clear, articulate and simple for people to be able to use.

Jim suggested the 'Nexus of Forces' presented by Gartner my be a useful starting point to flesh out some examples of solution paths that would be of value to the wider community. Leo suggested another topic along the lines of 'what are the steps in an architectural review?', thus broadening out the topic from the 'solution' concept.

This was largely because the group felt that a broader range of artifacts are being asked being asked for, particularly where people have no prior art to work from. It was agreed that the deliverables from any work associated with this would need to be Higher Ed flavoured, speaking the language of HE and aimed at campus CIOs as a communication piece. However, we need to think about a broader audience where more widespread use becomes apparent.

Scott raised the interdependency of the processes/solutions which could potentially lead to a taxonomy of documents for ITANA publication.

Architecture of Learning:

ITANA Reference Architecture for the Learning Ecosystem

Capability maps

Lifecycles
Lifecycles needed to support learning

Capabilities can be driven from lifecycle exercises

Existing product roadmaps
Survey existing product roadmaps:

Other EDUCAUSE constituent groups
Reach out to other EDUCAUSE constituent groups. Here are some possible candidates.

  1. Which ones?
  2. How do we reach out?
  3. How do we collaborate?
  4. Survey other groups for useful artifacts, tools, techniques?
  5. Join listservs for a quick learning technology survey?

Outreach

  1. EDUCAUSE 2013
  2. f-2-f workshop for the working group May-June. UW?
  3. ITANA working group.
  4. Space on the ITANA wiki

Accessibility
Subsumed under personas

Current landscape survey
Like the SOA short survey. 15-20 minutes for the respondent. Try to target 30 institutions. Eg:

  1. What LMS are you running?
  2. Do you have a learning plan?
  3. Curriculum development module?
  4. Tools?
  5. Analytics?
  6. Recommendation engine?