Learning objectives

• Identify, model and validate user needs and goals for specific market segments, using an iterative hierarchical process
• Design and validate MVP UX prototypes building upon established interface paradigms
• Design and validate MVP UX prototypes for emerging and novel types of interfaces
• Design methods to rapidly measure and validate such hypothesis, facilitating a data driven decision process
• Map out user needs, existing alternatives, market segments, unique value propositions and solutions provided by your augmented reality app using a lean business model canvas
• Create user story maps for your augmented reality app in order to hierarchically model high level goals, activities and tasks as basis for scoping the prototype
• Prioritize what slices of the user story map tasks you would translate into the wireframes and storyboard that would make up a first teration for your augmented reality app prototype
• Define how your augmented reality app prototype will enable you to validate whether it solves a user "problem" for a specific market "segment" and to what degree that is reflected in your MVP minimum viable product "solution"
• Use UX prototyping techniques to communicate with a diverse set of stakeholders

Monday

• Start by identifying several (existing) solutions that you think could benefit from Augmented Reality (glasses or phone/tablet based).
• Consider what additional value elements you can add.
• Brainstorm and add other ideas you may have.
• Decide on two ideas to continue working with (existing adding AR or entirely new).
• Update this sheet with your ideas.

Afternoon HandIn 

• Describe the main user journey (in some form, such as bullet points), and
• sketch out at least a few key wireframes of the main interactions (using e.g. figma.com)
• Do this for each idea.
• Hand in those two sets of journeys and corresponding key wireframes to DTU Inside.
• Be ready to present and review your ideas to other groups Tuesday morning.

Tuesday

Tuesday assignment:

Peer Session

• One group explain their ideas, using the user journey and wireframes to show it
• The other group gives feedback and asks (constructive and critical) questions
• Point out at least 3 good elements and identify at least 3 weak areas (SW in SWOT)
• Use 30 min for each group
• Change roles and repeat

After the session

• How well could you explain your idea and what was unclear
• Select the “best” idea and continue working on it
• Create a Lean Canvas (template example) and a User Story Map, and refine your Wireframes
• Hand In your LP-like poster (keynote/powerpoint presentation, max 3 slides) with appendices (LC, USM, WF), which you can use to present your idea
• IMPORTANT: Hand in ONE PDF file and name it GroupNN_title.pdf

Wednesday

• Continue iterating your solution,
• Focus on creating prototypes and validating
• Hand in by 16:30 to peergrade a full pack of 1) Landing Page (or your presentation in PDF format), 2) Lean Canvas, 3) User Story Map and 4) a Storyboard of Wireframes with micro-interactions as well as 5) links to or photos (or link to video) of your (executable) prototypes or experiments you have done.
• Afterwards, review what you are assigned in peergrade.

Thursday

Assignment:

• Continue working on your solution, iterate build-measure-learn cycles, doing prototypes and validation
• Upload by 1700 to CampusNet a 3-minute presentation in PDF format (only!) that you will use for the final presentation.
• This should be based on the latest iteration of your project idea. You may consider including slides with wireframes/screenshots in your 3-minute presentation that show a typical flow through your system -- but please leave out login details etc. You should also explain or show what/how you validated your idea (photos or short video links to YouTube are OK).
• Include (when possible) the full set of artefacts (LP, LC, USM, WF, Validation Documentation) as appendices.
• You may still need to practice pitching your idea and solution based on the presentation you hand in, so that you're ready to pitch it the following morning to all other group.
• Make sure you can do your presentation in 3 minutes (or less) -- this usually takes some practice.
• However, you will be allowed to spend 2 more minutes on showing a typical flow of using your system or a small video snippet, if you include screenshots/wireframes or a working link in your pdf file.

Friday

Assignment

• introduction/motivation (why do this)
• existing work/competitive solutions
• (major) iterations you’ve gone through, showing how you arrived at your product: 
• what was validated (hypothesis)
• how you did (build, measure)
• outcome of validation, leading to next iteration (learn)
• discussion and conclusion                                                                                                                                 
• individual contributions to the project, maybe as a matrix of persons/areas (i.e. did all contribute equally, or was there some division of work/areas of responsibilities) *
• references *
• appendices with your artefacts (LP, LC, USM, WF, Validation, …; for each relevant iteration) *

Examples of previous reports

• Group 1
• Group 13
• Group 14
• Group 4

Literature

Groups