|
||||
|
|
Wk01: Augmented Reality
Page last edited by Per Bækgaard (pgba) 09/01-2020
Augmented Reality (which is a part of the wider concept Extended Reality) systems like the Microsoft HoloLens are examples of Mixed Reality: blending the virtual and real worlds. This offers new and exiting opportunities for systems design, but also poses a whole new set of challenges when designing solid User Experiences. This weeks project will focus on creating systems that work in an extended/augmented reality setting. Note This page will be continuously updated through the week; the schedules below are therefore only tentative. Learning objectives
Monday 08:00: Introductory lecture on User Experience and Extended/Augmented Reality and course practicalities (B341#A021)
09:30: Group work (B358#H067, #H068, H072)
12:00: Lunch break
13:00: Q&A Sessions (B358#H067, #H068, H072)
13:30: Group work (B358#H067, #H068, H072)
17:00: Hand-In to DTU Inside your two idea (user journey and wireframes as ONE pdf file, named GroupNN_xxx.pdf) Slides: Morning Lecture (will be updated) Monday assignment (see slides for more details): Noon HandIn
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).
Afternoon HandIn
1) Describe the main user journey (in some form, such as bullet points), and 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 08:00: Peer Review Sessions (B358#H067, #H068, #H07)
09:00: Group work (B358#H067, #H068, #H072)
12:00: Lunch break
13:00: Lecture on Design Thinking in UX (B341#A021) followed by short presentation of Augit
14:00: Group work (B358#H067, #H068, #H072)
17:00: Hand-In (LC,USM, WF and LP-like poster). Also PRINT OUT YOUR POSTER (A3)!
Slides: Afternoon Lecture Tuesday assignment: Peer Session
One group explain their idea, using the user journey and wireframes to show it
The other group gives feedback and asks questions
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 and a User Story Map, and refine your Wireframes
Hand In (Tuesday afternoon) the above, including the LP-like poster you can use to present your idea
Print out the poster and bring it for Wednesday morning’s poster session
Wednesday 08:00: Poster Sessions (B358#H067, #H068, #H072). BRING YOUR PRINTED POSTER (A3).
09:30: Group work (B358#H067, #H068, #H072)
12:00: Lunch break
13:00: Lecture on Testing and Validation (B341#A021)
14:00: Group work(B358#H067, #H068, #H072)
16:30: Hand-In (LC, LP, USM, WF) to peergrade.io (join at www.peergrade.io/join and type in the class code ___)
16:30 Peergrading
17:00 EOD
Slides: Afternoon Lecture Assignment 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 poster), 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 08:00: Lecture/Feedback (B341#A021)
09:00: Group work (B358#H067, #H068, #H072)
12:00: Lunch break
13:00: Group work (B358#H067, #H068, #H072)
17:00: Hand-In (Presentations for Friday morning in pdf format!) Slides: Morning Lectures Assignment: Continue working on your solution, iterate build-measure-learn cycles, doing prototypes and validation Upload by 1700 to DTU Inside 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 stillneed 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 08:00: Group Presentations (B341#A021)
11:00: Group work (B358#H067, #H068, #H072)
17:00: Hand-In of Report (0.5 page/group member) with Lean Canvas, Landing Page, User Story Map and Annotated (Micro-interactions/Back-end) Wireframes and Validation documentation as appendices in one pdf file to CampusNet. Name your file "GroupNN_title.pdf" (where title is a description of your work). Include also links to your "executable prototypes" and any video lins, but make sure you have all details of the wireframes readable in the PDF file you hand in. For the group presentations, please give feedback using this google form. Results will be visible here. Assignment For the main report, hand in half a page pr person (i.e. 2/2.5/3 actual report pages including illustrations, without counting the items marked with a *; plus appendices use the 2-column ACM_SigConf template (part of ACM Master Article Template, or use the 02266 Overleaf template) and hand in one single pdf file to DTU Inside by Friday 17:00 mark clearly who wrote and can be held responsible for each part by e.g. initials in the header/section title (see also further below) be sure to include final versions of 1) landing page, 2) lean canvas, 3) user story map and 4) annotated wireframes w/microinteractions 5) a link to your executable prototype (or similar) and/or video in the appendices and 6) additional documentation of how you validation. Make sure the actual landing page, user story map etc is included in the pdf as vector graphics and not just a link to an external resource where it is available (although you may of course also provide a link to e.g. an executable version of the landing page). - 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 The following are examples of reports you may be inspired by. NOTE: None of them are perfect (and a few follow a slightly different template than above):
Background from 02809 (some parts may be refreshed in lectures too) Michael Kai Petersen: Modeling Needs and Solutions (Lean Canvas, Elements of Value) Prototyping with user Story Maps Micro- (and other) Interactions Eye-Mind and Gestalt Principles Literature Abras et al: User-Centered Design (Strongly recommended read) d.school at stanford: Design Thinking Bootleg with main page here (Very handy overview to dig into) Milgram, P. and Kishino, F., 1994. A taxonomy of mixed reality visual displays. IEICE TRANSACTIONS on Information and Systems, 77(12), pp.1321-1329. Alanya Treene (2017): The rise of augmented reality. Andy Robertson (2017): New Lego Augmented Reality App is the best Open-World LEGO Video Game. David Heanay (2020): Facebook’s Chief Researcher: ‘When The Next Generation of VR Shows Up, It Will Be Because We Did It’ MarvellApp (2018): Designing for VR: A Beginners Guide. Almquist 2016: The Elements of Value (webinar) The UX Review (2013): User Journeys -- the Beginner's Guide NN Group (2018): Journey Mapping 101 IT-Universitetet (2018): Derfor fejlede tre store offentlige it-projekter UX Design Collective, 2017: Design with Gestalt theory Becca Kennedy, 2017: Four psychology principles every UX designer should know Groups Please update this sheet to include your group. |
|||
