Midterm Demos

Demo:

• 15 minutes demo

• 15 minutes discussion

• 30 minute time slot = 15 min demo + 15 min discussion

• 3–5 slides + software demo

  • Opportunity/Problem

  • Architecture overview

  • Team process + health summary

  • Current status

  • Objectives/Plan

Learning activities

for the 3 weeks June 14–June 30 can be preparing for the midterm demo. If you do other learning activities, in this time, you may claim them in subsequent weeks instead.

Scheduling:

• Thursday June 24 to Wednesday, June 30th.

• Common case: Your usual TA meeting time.

• Exception 1: Your usual time conflicts with another group’s usual time. See the spreadsheet (or talk to your TA) for your alternate time.

• Exception 2: You would prefer to bump your usual time on Thursday, June 24 or Friday, June 25th, into the next week. See the spreadsheet (or talk to your TA) for your alternate time.

• Spreadsheet:
  https://docs.google.com/spreadsheets/d/1ucyh43PrZSXYC5SDkHMfQ23A-eSw8ZNDxX323pue8vM/edit?usp=sharing

Peer Activity #1:

The syllabus has peer activity #1 worth 2%. The original deadline was June 13, now extended to June 23.

We recommend that you choose feedback on practice demo as your peer feedback activity — but you can choose something else if you prefer. This is a team activity, and you will write a file in the directory of the team you are giving feedback to. You have been paired with another team (below). You will give each other feedback.

• Axon + LOI

• SpongeFabric + Vulcan

• scena360 + coachella

• InsufficientlyCaffeinated + inliner

• QUAIL + TheWheelerz

• KRAM + Hydra

• moss + Localised

• Houdini + Agnes + rhino (triplet due to odd number of teams)

• LacusLabs + r2

• VoxPopuli + ChickenNuggets

• DiDiDaJi + fnord

• DotDotDash + VivaLaZeez

• alarm + uConverse

• AutumnLeafStudio + BSD

Midterm Peer Feedback:

• The syllabus has midterm peer feedback for 4%, due during the midterm demo period.

• You will give feedback to two different teams (2% each).

• You will do this individually in LEARN.

• You can choose which two demos you want to attend.

• You may also ask questions and give feedback verbally during the discussion period after the demo.

• You MUST select different teams than your teammates. So if there are 4 of you on your team, then collectively you will see 8 different demos, since each of you will see two different ones. The depth of your learning in these courses comes from your project. The breadth comes from learning from your peer’s projects.

Summary of Todos:

• (Team) confirm your demo time with your TA — see spreadsheet

• (Team) schedule practice demos with your assigned practice team

• (Team) plan which teams you will provide individual feedback to during the demos (remember: you MUST select different teams to give feedback to than your teammates do)

• (Team) prepare demo

• (Team) give feedback to practice team on their practice demo (in Git)

• (Team) receive feedback from practice team on their practice demo

• (Team) present your demo

• (Individual) attend two other team’s demos

• (Individual) provide written feedback for those two teams in LEARN