...
Overview
Below are the notes that were collected during the workshop.
...
Location: Madison Wisconsin. Campus meeting rooms.
Dates: May 20 - May 22. 2.5 days.
Agenda
Day | Time | Topic | Facilitator
| Scribe
| Location |
---|
Monday May 20 | 9:00 - 9:30 | Review agenda and deliverables
| Jim, Leo
| | Pyle center, Room 225 |
| 9:30 - 10:30 | Normin: Review terminology, structure of capability maps
| Jim
| Scott | Pyle center Room 225 , Webex |
| 10:30-12:00 | Learners: review object model and scenarios | Jim | Scott | Pyle center, Room 225, Webex |
| 12:00-12:30
| Review parking lot items
| Jim | Scott
| |
| 12:30-1:30 | Lunch | | |
|
| 1:30-2:30 | Instructors: review object model and scenarios | Jim | Leo
| Pyle center Room 225, Webex |
| 2:30-4:30
| Capabilities that supportinstructors
| Jim | Leo
| Pyle center, Room 225 |
| 4:30-5:00
| Review and action items and parking lot items
| Jim | Leo | Pyle center, Room 225 |
Tuesday May 21 | 9:00 - 9:30 | Review agenda and deliverables
| Jim, Leo
| | Pyle center, Room 225 |
| 9:30 - 10:30 | Mentors: review object model and scenarios | Jim | Laura | Pyle center Room 225, Webex |
| 10:30-12:00 | Capabilities that support mentors | Jim | Laura | Pyle center, Room 225 |
| 12:00-12:30
| Review parking lot items | | | |
| 12:30-1:30 | Lunch | | |
|
| 1:30-2:30 | Content developers: review object model and scenarios | Jim | Rich | Pyle center Room 225, Webex |
| 2:30-4:30
| Capabilities that support content developers
| Jim | Rich | Pyle center,Room 225 |
Wednesday May 22 | 9:00 - 12:00 | Review workshop accomplishments. Determine next steps:
- Possible video session with wider ITANA group
- Rich's presentation
- A possible publication
- Wiki artifacts next steps
- Maturity survey
- Engagement with other groups (eg ELI)
| Jim, Leo |
| Pyle center, Room 225 |
Organization of topics
The key organizing principle for the capabilities is the concept of a role (instructor, learner, content developer). Capabilities support a role in a particular process. A concrete illustration of the process is a scenario. Examples:
...
Scenario = role+learning context. Capabilities support scenarios.
Procedures and mechanics
- Each session has a facilitator who is responsible for:
- Time tracking
- Staying on topic
- One conversation at a time
- Parking lot
- Each session has a scribe who puts the narrative straight into a Google doc
- Parking lot is and easel pad (scribe can transcribe these items after the session)
- Diagrams are done on whiteboards and/or easel pads. After the session these can be photgraphed and transcribed to out tool of choice (to be determined)
Workshop session checklist.
The workshop is divided into 4 sections: Learner, Instructor, Mentor and Content Developer. For each role we will be developing a capability map. For each we need to ensure we cover these topics:
- Capabilities:
- Strategic: Students' educational goals
- Operational: Eg: Class scheduling, grades collection
- Infrastructure: Eg: IAM, workflow
- Scenarios. Have we identified a set of scenarios that illustrate the salient features of the problem space
- Data elements. Calling out any obvious data elements from the problem space
- We should call out any obvious applications that are relevant (registration, degree audit etc)
Attendees
Attending f-2-f
- Jim Phelps.Enterprise Architect University of Wisconsin--Madison, Chair ITANA (jamesphelps@wisc.edu)
- Jeanne Blochwitz (blochwitz@doit.wisc.edu)
- Jeff Bohrer Sr. Learning Technology Consultant & Manager, Learn@UW-Madison (jbohrer@doit.wisc.edu)
- Jim Helwig Portal Project Manager. University of Wisconsin--Madison. (jim.helwig@doit.wisc.edu)
- Leo Fernig. Enterprise Architect. University of British Columbia. (leo.fernig@ubc.ca)
- Scott Fullerton. Senior IT Architect. University of Wisconsin--Madison. (sfullerton@wisc.edu)
- Richmond Stevenson, Assistant Vice President, Enterprise Architecture and Strategy UMUC (richmond.stevenson@umuc.edu)
- Laura Gekeler LMS Administrator, University of Notre Dame (LGekeler@nd.edu)
Attending remotely (webex)
- Carol F. Bershad University of Washington (cbershad@u.washington.edu)
- Steve diFilipo VP/CIO Cecil College. Leader of the Mobile Technologies constituent group (sdifilipo@cecil.edu)
- Glenn Donaldson. Senior Application Architect, OCIO Enterprise Applications/Ent. Architecture. The Ohio State University. (donaldson.6@osu.edu)
...