The Garage Experience

1. Call for announcements
   • • IGC event Thursday
2. CS 401 Results
3. Interpreting/responding to faculty feedback on documents. What "check" means and when you should remove it.
4. Compiling project descriptions and legal questions
5. Plans must include concrete deliverables what will you be accountable for at each milestone? Even if things are "finished" during the phase, what will the package of accomplishments look like at the milestone check in? Financials should be easy to read.
6. On Pod Meetings - basic format (see Notes Tab) and need names of point people for pod meetings
   • Media (Blair, Amri, Sarah K, Kimari)
   • Kids (Chris, Nate, Jane)
   • Things (Chloe/Will, Joseph, Macki, Caitlin)
   • Software (Josh/Nathan, Riley, Jane/Serene, Sarah A/Ben, Luke)
   • Medicine (Parker/Louis, Sara/Jared)
7. Peer sign-off: read over (1) update, (2) semester plan, (3) financials and offer iteration forward critique - what needs to be done to get this into submission-ready condition? See below for assignments.
8. DUE Friday 5pm: you must have revised documents in the shared folder and you must share them with your project advisor in the manner that s/he prefers with a cover note that makes these easy to digest.

Pod Meeting Agenda (start at 10:30 sharp, finish before 11:15)

1. (2) one minute warm up exercise - get everyone's attention, everyone hears their own and everyone else's voice
2. (1) appoint next week's point person, next week's "Yer Awn" team
3. (2) point person reminds everyone of the class's agenda for the week, upcoming deadlines, etc.
4. (10) brief update from each team (1) what did we finish last week? (2) what do we hope to finish this week? (3) cool discovery/solution (4) headache/concern
5. (30) Yer Awn team has the floor for describing problem/requesting feedback