392 Overview

• Prototype vs Mockup: what's the difference? (discuss)
• How rapid is rapid? In this class, first demo of a new app in a week!

Things to un-learn about team work:

• Work on what you know best.
• Divide up the work to get the most done.
• Work on many things at once.
• Assign everyone tasks at the start of each week.
• Plan for a big final push.

Things to un-learn about software development:

• Get all the requirements first.
• Start with the architecture.
• Start with a low-fidelity mockup.
• First implement login, then data entry, then ...
• Measure progress by time spent, code written.

• Build / Reflect / Improve / Repeat
• Learn by doing, not listening to lectures
• Class is for discussion, setting goals, doing work
  • Attendance is critical
• Your key resources:
  • The course web site
  • the web

• I assess teams on their ability to
  • deliver quality product predictably
  • function as a cohesive high morale unit
  • improve constantly through retrospection
  • as demonstrated in weekly results and reflections
• I assess individuals on their
  • contributions to the team and class
  • demonstrations of learning in activity reports
  • engagement in discussions

• I will form teams in a week or so based on the skill survey and tutorial progress.
• I mix things up.
• It's best to NOT team with someone you've worked with before.