You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 10
Next »
Travel, parking, hotels, etc. | Schedule and agendas | Working documents and links | Captured flip-charts and notes |
Schedule
The Face2Face begins at Lunch on Wednesday and ends at Lunch on Friday.
| 8:30-11:45am | 11:45-1:15 | 1:15-5:00pm | 6:00pm |
---|
Day 1: Wednesday | No meeting | Lunch | TBD | TBD |
---|
Day 2: Thursday | TBD | Lunch | TBD | TBD |
---|
Day 3: Friday | TBD | Lunch | No meeting | |
---|
Goals and Approach
Workshop goal
Topic(s)
Influence and Leadership Skills for Architects - driving strategic decisions
Examples:
Getting Concensus -- Voting Structures, Minimum Specs (Liberating Structures), Affinity Diagrams
Sharing Knowledge -- Stories, Metaphors, Images
Managing Meetings -- Flip Chart Management, Capture and Collect
Building Relationships -- Eight Ways to Influence
Inspiring Action -- Linking to the outcome. Inspiring stories
Getting work done -- Unconference, Kanban Board
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
- Use break-out groups each concentrating on a topic
Outcomes
- In person idea sharing and exchange
- A best practices library relating to the use of these tools
- 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?
- 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
Strawman for an approach
Using principles from hackathons and unconferences.
- Use most of day 1 for stage setting. The items listed in Topics provide a starting point and by the end of the day we should have topics, leads, and teams to tackle them (topics, not leads). Teams are encouraged to eat dinner together and begin discussions on their topics.
- 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.
- 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