Page History

...

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

1.  Core diagram in support of advisors
2. 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

...