| Saturday | Sunday | Monday | Tuesday | Wednesday | |
|---|---|---|---|---|---|
| 7:30 to 8:15 |
Tarble Breakfast |
Sharples Dining Hall Breakfast |
Sharples Dining Hall Breakfast |
Sharples Dining Hall Breakfast |
|
| 8:30 to Noon |
Dupont 138 Teachers free time Developers meet |
Dupont 138 Favorite probs, misconceptions, assessment; Good problem discussion; MathWorlds/Simcalc; Group formation |
Dupont 138 More problem dev't, assembly, & reporting; Report back; POW constraints; Spring POW reflections; Interface design; Participant math sharing |
Dupont 138 Next step planning; Student involvement; Add'l problem dev't |
|
| Noon to 1:00 |
Tarble Lunch |
Sharples Dining Hall Lunch |
Sharples Dining Hall Lunch |
Sharples Dining Hall Lunch |
|
| 1:00 to 5:00 |
Dupont 138 Intro: Purpose, POWs Sketchpad & Agentsheets |
Dupont 138 Mock up problems; Component assembly |
Dupont 138 Map problems to calendar; 2nd round mock ups |
Dupont 138 Share results |
|
| 5:30 to 7:00 |
Tarble Dinner key-pickup (5-8:30pm) |
Off Campus Dinner |
Ashton House Dinner |
Ashton House Dinner |
Off Campus Dinner |
| 7:30 to 9:30 |
Dupont 138 ShowMe database Play with tools |
Dupont 138 Participant math sharing |
Dupont 138 Discuss interface |
Details:
Saturday night
Dinner and key-pickup
Depending on when people arrive, developers may meet for a while.Sunday
Morning
Teachers meet.
Developers meet.
Afternoon
Intro: Purposes of the week and project. Tristan and Mark. POW intent and environment.
2 hours intro to Sketchpad component, 2 hours AgentSheets.Evening
Dinner
ShowMe presents emerging priorities and curriculum database. Participants play with tools.Monday
Morning
Participants share favorite problem and misconceptions. What makes for a good problem?
What makes for a good assessment around these activities?
2 hours MathWorlds/SimCalc components.
End morning with partitioning into groups.Afternoon
Mocking up and component assembly into problems (intro to script capability).
Evening
Dinner
Participant sharing of math.Tuesday
Morning
More problem development and assembly work.
Report back. What makes for a good problem? Inform with POW format constraints. Discuss the spring POW experience. Plan for interface design piece.
Participant math.Afternoon
Map problems onto the calendar. Second round of mocking up.Evening
Dinner
Discuss interface.Wednesday
Morning
Planning for the next steps and year.
Student involvement.
Additional problem development.
Afternoon
Sharing results.Evening
Dinner for those who are staying.