You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 53 Next »

ITANA steering committee we discussed the possibility of a mid-term ITANA f-2-f workshop (April ).  This workshop would be focused on building out a reference library of conceptual models and example real-life use cases.   There is an email survey making the ITANA email list rounds. 


Proposed ITANA mid-term f-2-f workshop

Confirmed Dates: April 22 - 24

Confirmed venue:   The Talaris Conference Center, Seattle, WA  - Maple Room

Logistics:  Hotels, Parking, Travel

Travel to Campus

The University of Washington is located in the U-District of Seattle.

Parking

I am looking into parking at Talaris. It might be free. Stay tuned.

Parking on campus is limited.  You will need to pay for your own parking if you drive.  See the Spring F2F Parking Page for details if you are driving to campus.

Hotels

NOTE: The Venue Has Changed!

You can stay at the new conference venue:

http://www.talarisconferencecenter.com/

See the Spring F2F Hotel Page for details. The UW does have a price agreement with several hotels close to campus.  (I do not care for the Deca Hotel.  It isn't bad but it also isn't good. YMMV. - ed.)

Other infoThe U-District has a lot of "college" restaurants. Nearby is University Village - an open-air mall with several better restaurants. The nearby neighborhood of Wallingford has lots of good restaurants. There are two small art galleries on campus. There is good bus service downtown. Rowing is really big in the area and you can always go to a bridge and watch crew.


Subject: EA Conceptual Models

Enterprise Architects use a variety of conceptual models and tools to convey their ideas.  (Piet's framework could guide this work well I think - JP)  These include:

    1. Brick Diagrams
      1. Columbia explanation and examples
      2. NIH EA site 
      3. Wisconsin site
      4. Washington site
    2. Pace Layers
      1. Gartner Glossary
      2. Link to Gartner special report
      3. Piet Niederhausen 2012 Presentation
    3. Capability Maps
      1. ITANA capability map
      2. T&L capability map (from the ITANA RATL)
      3. UW-M Advisor capability map
      4. Detailed Cutter article on the use of capability maps
    4. Core Diagrams
      1. T&L Core diagram (from the ITANA RATL)
      2. UW-M Student Advisor Core Diagram
      3. Microsoft Blog on core diagram creation
    5. TIME models
      1. Piet Niederhausen 2012 Presentation
    6. Roadmaps
      1. ITANA Roadmap page
    7. Dot Diagram
      1. 2012 presentation by Jim Phelps
    8. Engagement Value Matrix
      1. 2013 presentation by Chris Eagle

Workshop goals

    1. A deep dive into each tool using a selected use case from Higher Education as an illustrative example (eg using Core diagram to describe the Advising ecosystem on campus)
    2. Document usage of the tool and “how to get started” information for architects 
    3. Find a broad set examples where people have used them

F2F meeting structure

This would be like an (un)Conference where we would be agile in the agenda and deliverables but focused on creating a set of resources for ITANA members

    1. Use break-out groups each concentrating on a topic

Outcomes

    1. In person idea sharing and exchange
    2. A best practices library relating to the use of these tools
    3. A set of guidelines for each tool.  In what context is the tool useful?  Who is the intended audience? What kinds of information does it best convey?
    4. Information that can be applied to one or more problems at the home institution.  Ideally that work can be fed back to the library started in the F2F

Proposed schedule (note: there will be breaks during the morning and afternoon sessions).

 

8:30-11:45 

11:45-1:15 

1:15-5:00

6:00PM

Day 1

No meeting

 

Facilitator: Heidi Barta, UW-IT Organizational Development

    • Set goals for the meeting, 
    • define outcomes, 
    • define work processes,
    • define / identify repository
    • define process for maintaining the content 
    • identify and prioritize topics, 
    • assign leads for topics
    • Review current work / wiki

ad hoc Dinner

Day 2

Continue with selected topics

Lunch

Continue with selected topics

ad hoc Dinner

Day 3

Post-workshop action items

 

No meeting

 

Strawman for an approach

Using principles from hackathons and unconferences.

    1.  Use most of day 1 for stage setting.  I believe the items listed in the agenda above will fill up the time, but by the end of the day we should have topics, leads, and teams to tackle them (topics, not leads).  We might want to encourage teams to eat dinner together and begin discussions on their topics.
    2. Day 2 is hackathon day.  Teams work on their topic, creating all of the outcomes listed above.  If they complete their topic, the can choose another one.  This continues throughout the day.
    3. Day 3 is presentation day.  Each team should present their completed topics to the assembled group.

Questions:

What about partially completed topics?  Do we want to do something with them?

Do we want to do some presentations on day 2, in order to give the attendees who didn't work on the topic a change to provide feedback and still give the teams time to incorporate the feedback into their tool?

 

 

Possible Scenarios

  •  Core diagram in support of advisors
  • Given a portfolio of initiatives, we need to develop a roadmap, manage the portfolio, and otherwise provide stewardship.  We need to demonstrate needed capabilities and dependencies and to promote an architecture favoring user experience driven initiatives.  We need to communicate the approach to stakeholders. What tools would support this analysis?  What tools would communicate needed aspects best

 

 

 

  • No labels