Week 6 To-Do’s
Readings
Each student must individually select at least one starred item and at least one other item from this week’s reading list to read/watch. More details are available on the Information page under Deliverable 1c.
Articulate User Stories
Each member of the team chooses one of the features/ideas you articulated in last week’s design arguments (you should have 4 to 5 features/ideas in total, one per design argument). Each member follows the user story structure shown in lecture to create an epic user story and 2 - 3 user stories for that epic. Use your personas, affinity diagram, and HTA analysis to guide you. Once everyone has finished a draft of their user stories, meet as a team to discuss and refine them. Your design document should include:
- The 4 to 5 epic user stories, each with 2 - 3 associated user stories, as artifacts.
Create Storyboards based on User Stories
Each team member expands their feature/idea and user stories into a storyboard. Focus on how that feature/idea for your app/product can help solve any identified user problems, make the process easier, better, faster, etc. Once everyone has finished a draft of their own storyboard, meet as a team to discuss, critique, and refine everyone’s storyboards. Your design document should include:
- Images of the 4 - 5 final storyboards as artifacts. Make sure the images are legible (include a link to a higher resolution image or shared link if you used Miro, Figma, Google Draw etc.)
- A brief 250 - 500 word write-up discussing what you learned from the user stories and storyboards.
Team meeting and design document
Conduct this week’s team meeting or discussion in and/or out of class. Update your design document with the meeting minutes and the outcomes of this week’s activities. More details are available on the Information page under Deliverable 2a.
Write your midterm report
Write a report to consolidate the activities you did so far, spanning the following key design stages: empathize, define, and ideate (partially). The midterm report describes the rationales, reasoning, insights, and outcomes you had in those stages, and the solid logical connections between these stages: e.g., how the outcomes of a previous stage influence the next stage. Contents in the design document could be re-used only with sufficient refinement (instead of copied directly); note that a design report is a well-presented, coherent, and logical essay rather than a collection of fragmented notes like those in the design document. Please carefully read the detailed requirements on the Information page under Deliverable 2b.
Due next week
- Week 6 reading reflections (1c)
- Design document section #5 (2a)
- Midterm report (2b)