Design Development Checklist
___ 9/28/17: You should be able to use concepts from the readings to talk about your project with the teaching team (words such as constraint, mapping, visibility etc).
___ 9/28/17: Each team member has posted a sketch of a potential interface element to your team’s board, that are neither too professional nor too rough.
___ 9/29/17: You should have read the readings that Ubuntu presented in class on 9/25.
___ 10/2/17: You can end a brainstorm and start a critique of your proposed ideas.
___ 10/5/17: Selected and started your first two [individual] design challenges.
___ 10/5/17: The team has prototypes that incorporate paper, sticky notes, and transparent cut-outs.
___ 10/5/17: The team can do a “wizard of oz” acting out session of a paper prototype.
___ 10/12/17: Have a draft plan for a usability test, including scripts and scenarios.
___ 10/12/17: You should have an understanding of different types of errors a user can have, and should have made a list of errors the you have found in your paper prototype.
___ 10/16/17: You will have priorities set for building into an automated prototype.
___ 10/18/17: Design Development Phase submitted to your project site.