91
edits
(first draft of workshop agenda) |
m (→Activities) |
||
Line 38: | Line 38: | ||
There is limited time during the workshop, so priority is on achieving some escape velocity rather than "completing" a project. We will consider it a success if each project ends the workshop with 1) initial ''<u>progress and momentum</u>'' on the project's goals, and 2) concrete, energized <u>''plans''</u> for next steps (e.g., "let's keep working on X and [submit it to Y, etc.]) | There is limited time during the workshop, so priority is on achieving some escape velocity rather than "completing" a project. We will consider it a success if each project ends the workshop with 1) initial ''<u>progress and momentum</u>'' on the project's goals, and 2) concrete, energized <u>''plans''</u> for next steps (e.g., "let's keep working on X and [submit it to Y, etc.]) | ||
==== | ==== Activities ==== | ||
The intent is for progress on the projects to be documented on the evolving project pages, which may link to prototypes/wireframes/proposal docs/code repos, or contain reading lists, or other markers of progress to share. Progress will happen via a mix of work sprints (synchronous and asynchronous) over the course of '''Day 1''', along with lightning talks and feedback from other workshop participants, and then culminating in a second/final progress report and closing call to action on '''Day 2'''. | The intent is for progress on the projects to be documented on the evolving project pages, which may link to prototypes/wireframes/proposal docs/code repos, or contain reading lists, or other markers of progress to share. Progress will happen via a mix of work sprints (synchronous and asynchronous) over the course of '''Day 1''', along with lightning talks and feedback from other workshop participants, and then culminating in a second/final progress report and closing call to action on '''Day 2'''. | ||
edits