STEAM Camps Review

From Open Source Ecology
Revision as of 23:22, 1 April 2020 by Marcin (talk | contribs) (Created page with "=Strength= =Suggestions= #Refine and polish curriculum completely to about 16 one hour lessons with detaled, full curriculum. #Before/During/After Unit: ##Before: go over al...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Strength

Suggestions

  1. Refine and polish curriculum completely to about 16 one hour lessons with detaled, full curriculum.
  2. Before/During/After Unit:
    1. Before: go over all the lessons, so you're practicing during Camp, not seeing material for the first time
    2. During: Focus on collaborative teaching to make life easy for instructors, all 12 in same or near time zone. Or otherwise work out the collaborative teaching aspect.
    3. After: Incentive Challenge, and 1 hour Design Sprint every Saturday, with 1 hour prep beforehand.
  3. Do only 9 day events; other programs could exist, but that is not the STEAM Camp
  4. Define clear Product to be developed within the 5 Dev Days
  5. Secure enough Instructors so each prepares a 1 hour lesson. Rationale: the curriculum needs to be refined, and is a full time effort for ~4 people until the curriculum is done. Part time development with about 16 instructors would solve this.
  6. Promise clarity on the next event: organizing 12x12 with $72k theoretical budget
    1. $80 COCA for $12k advertising costs
    2. $12k at $4k/month to an Event Planner
    3. $25k allocated to an Incentive Challenge for Product
  7. Divide up 16 lessons between future participants for