Team discussed schedule for usability test

• Need to figure out who we need to use for our second usability test
• First usability test – Rebecca, Jill, Karen Byrd
• What’s the purpose of usability test one? First feedback on incomplete prototype to make sure we’re going down the right path. To assess our current status, is the content appropriate, feedback on navigation, initial functionality, organization of content.
• First usability test plan walkthrough in Shahron’s class on April 7. First usability test sent to Rebecca, Jill, Karen on April 8. We’ll ask Nada to contact them and tell them what the plan is.
• Usability test feedback to Bean by April 12.
• Over this weekend, each team puts together their own idea of tasks for users to do in the first usability test in their subcomponent, as well as suggested questions.

Tuesday April 6 – we’ll spend time as a team creating first usability test and usability testing plan.

• Sue went over what’s in the wiki at this point – she’s been adding thoughts/suggestions as we go along.
• Ryan said that the requirements can be submitted to any developer and we will include a page for future enhancements.
• Components of the Requirements Document – these are on the Wiki
• Need to draft a section of what LATIST is
• A synthesis of all teams’ content/task analyses will be created for the design doc

Draft design document due April 22. Discussed Interview Responsibilities at DAU

1. Design document – written document requiring lots of writing and editing
2. Usability test plan – team will write up evaluation section
3. Final presentation – team will create presentation and decide how it will be presented

Three teams

Design document – Sally, Sue, Debra

Final presentation – Conrad, Salim, Shantell

Usability – Ryan, George, James

Each team will:

• Gather info from others
• Decide on format
• Edit/proofread
• Write as required
• Analyze, synthesize, summarize

Anything else as required.