Design Development Checklist

___ [by 9/28] 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).

___ [by 9/28] 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.

___ [by 9/29] you should have read the readings that Ubuntu presented in class on 9/25.

___ [by 10/2] you can end a brainstorm and start a critique of your proposed ideas.

___ [by 10/5] selected and started your first two [individual] design challenges.

___ [by 10/5] the team has prototypes that incorporate paper, sticky notes, and transparent cut-outs.

___ [by 10/5] the team can do a “wizard of oz” acting out session of a paper prototype.

___ [by 10/12] have a draft plan for a usability test, including scripts and scenarios.

___ [by 10/12] 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.

___ [by 10/16] you will have priorities set for building into an automated prototype.

___ [by Wed 10/18] Design Development Phase submitted to your project site.