Wednesday 1 February
| Time |
Scenario development session | Demo development session | Facilitator |
|---|---|---|---|
| 09.00 - 09.30 | Coffee and Registration | ||
| 09.30 - 10.00 | Welcome, housekeeping, introductions & overview of goals:
|
Plenary session | PW + AJ |
| 10.00 - 10.15 | SCAPE Scenario exemplars - Outlining the issue and criteria by which the solution will be evaluated - The solution and how it meets the criteria |
Plenary session | CW & PW |
| 10.15 - 11.15 | Individual reports on SCAPE activities from each attendee. Build map of issues and solutions |
Plenary session | PW AJ (scribe) |
| 11.15 - 11.45 | Coffee Allocate small groups to paired issue/solutions (and dev) |
Plenary session | AJ+PW |
| 11.45 - 13.00 | Brainstorm and refine in small groups: - what will be shown in the demo on day 3 - report back to all |
Plenary session | |
| 13.00 - 14.00 | Lunch | ||
| 14.00 - 15.30 | Brainstorm on lonely issues and lonely solutions: Part 1: Group brainstorm Part 2: Refinement/prioritisation in small groups, allocate owners Part 3: Report back and capture thoughts on evaluation |
Development time (allocated devs only) |
|
| 15.30 - 16.00 | Coffee | |
|
| 16.00 - 16.45 | Write up new issues and solutions on the wiki |
Plenary session | |
| 16.45 - 17.30 | Practitioners meet and review new issues (Remaining devs start development) |
Development time (all devs) |
PW |
| 17.30 | Close | ||
| Time TBC | Event dinner | |
Thursday 2 February
| Time |
Scenario development session | Demo development session | Facilitator |
|---|---|---|---|
| 09.00 - 09.15 | Coffee | ||
| 09.15 - 09.30 | Welcome back, overview of agenda for the day | Plenary session | |
| 09.30 - 09.45 | Check in time |
Plenary session | |
| 09.45 - 10.00 | Devs who started earliest, report back |
Plenary session |
|
| 10.00 - 11.00 | Continue group work - packaging, jyplzer etc. Address lonely issues and lonely solutions from brainstorming session |
Plenary session | |
| 11.00 - 11.15 | Coffee | ||
| 11.15 - 13.15 | Continue group work - packaging, jyplzer etc. Address lonely issues and lonely solutions from brainstorming session |
||
| 13.15 - 14.15 | Lunch | ||
| 14.15 - 16.00 | Project status reports - REF (and related tool testing activities) |
||
| 16.00 - 16.15 | Coffee |
Development time | |
| 16.15 - 17.30 | Project status report PT | |
|
| Time TBC | Cultural Walk |
Friday 3 February
| Time |
Scenario development session | Demo development session | Facilitator |
|---|---|---|---|
| 09.00 - 09.15 | Coffee | ||
| 09.15 - 09.30 | Agenda for the day Reporting back from groups |
Plenary session | |
| 09.30 - 10.30 | Project status report and brainstorm - PW | ||
| 10.30 - 11.00 | Blog writing | ||
| 11.00 - 11.15 | Coffee | ||
| 11.15 - 11.30 | Review issue and solution gaps (see Etherpad ) |
||
| 11.15 - 12.15 | Brainstorming session: quantifying evaluation Flesh out and write up Evaluation Plan on the wiki |
Development time | |
| 12.15 - 13.00 | Loose ends and integration Including: -TB WP 2 Task 7 issues - policy |
Development time | |
| 13.00 - 13.45 | Lunch | ||
| 13.45 - 14.45 | Report back to group Issue champion to evaluate solution against criteria in Evaluation Plan |
Plenary session | |
| 14.45 - 15.00 | Coffee | ||
| 15.00 - 15.30 | Reports and evaluation continue | Plenary session | |
| 15.30 - 16.00 | Wrap up and event evaluation - anonymous feedback - group discussion |
Plenary session | |
| 16.00 | Close |
Labels:
None
1 Comment
comments.show.hideJan 20, 2012
Miguel Ferreira
Dear Andy,
Some questions on the agenda:
- Its not clear when the parallel sessions are going to happen. Can you please make this clearer by adding new columns to the agenda (one per each track)?
- The item "Individual reports on SCAPE activities from each attendee." should this be indexed at the attendee level or the WP level?
- What is "Check in time"?