|
Page last edited by Per Bækgaard (pgba) 30/11-2020
Monday November 30th
NOTE: The sessions are online-online. You can of course still use the group area if you would like to sit together as a group.
We will divide into two parallel sessions, with a built-in break. We expect ALL students to attend the entire session from 08.00 to 12.00 approximately (either session A or session B), even if that means you will be presented to something "new" -- that will solicit a different type of feedback which will be important to the groups presenting.
There will be two TAs/lecturers in each session, and in some cases also the stakeholders present.
Session A
| Time and topics |
Groups |
Zoom-link to use |
| 08:00-09:15 Micro-interventions |
6, 8, 20, 24, 32, 35, 37 and 38 |
ZOOM |
| 09:45-11:45 OptoCeutics |
3, 4, 7, 12, 14, 16, 17, 22, 23, 30, 33, 36 |
ZOOM |
Session B
| Time and topics |
Groups |
Zoom-link to use |
| 08:00-09:30 Computerome and Other |
10, 11, 13, 19 and 28
9, 26, 39, 40
|
|
| 10:00-11:30 Tripdoodler |
1, 2, 5, 15, 18, 21, 25, 27, 29, 31, 34 |
|
Presentation format
- Each group will present, based on the pdf file handed in at the end of week 12. You will share the presentation from your own computer; make sure you have tested this before on zoom. It means you can run it off Google Slides, Keynote, Powerpoint, WordPerfect or Emacs, as long as you know it works. Don't rely on anything that emits sound; it usually doesn't work to have sound in the presentation when sharing on Zoom.
- There is 3 min to give the presentation, but you may chose to use 2 additional minutes to show a typical use of your system (based on e.g. wireframes), if you have prepared and included that in your pdf file. So MAX 5 min for the presentation if you have at least two minutes of wireframes and the overall flow of screens.
- The presentation will be followed by questions and comments for up to 3-5 minutes.
- Other groups and in many cases the stakeholders will give comments, verbally and using the tool below.
8 min is set aside in total for each group.
ALL students individually need to use this link for giving feedback to other groups (results will be available here).
When you give feedback:
- Make sure you find the correct group number in the form
- Also it's a good idea to start your feedback with the product name/title of the presentation, as in "BetterTravel: Nice presentation, I could use this myself. But I didn't understand your target segment -- and I don't understand why all screens use the yellow-brown background..." or some such :-) Try to be constructive in a good tone.
This weeks assignment
Continue working on your project, using the methods you have learned throughout the course, taking into account the feedback you receive from this weeks presentations.
Iterate your project idea, each time validating with other groups or - better - with prospective users. Make sure you capture and document all artefacts and summarise findings and what you did, for each iteration (these may need to go into your report as appendices or summarised in the main text).
For each iteration, you need to create/revise your a 1) landing pages, 2) lean canvas, 3) user story map and 4) annotated wireframes (with micro- and backend interactions) as well as 5) your executable prototype.
In addition, 6) document what you have validated and how you did that.
Make sure you validate all elements of your idea, and not only your wireframes, through the iterations, so that your final iteration at the end of week 13 can be considered a MVP candidate.
Complete your final report and hand it in to CampusNet by Tuesday December 8th 23:59.
Details on the report
- For the joint part of the report, hand in half a page pr person (i.e. 2/2.5/3 pages for actual report without counting the items marked with a *) plus appendices and the individual reflections using the 2-column ACM_SigConf template (part of ACM Master Article Template) in one single pdf file upload to campusnet / inside by Monday Dec 8th mark clearly who wrote and can be held responsible for each part by e.g. initials in the header/section title (but see also below)
- be sure to include final versions of landing page, lean canvas, user story map and annotated wireframes w/microinteractions and a link to your Marvell prototype (or similar) in the appendices. Make sure the actual landing page, user story map etc is included in the pdf 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).
- include an appendix that contains 0.5 page of individual reflection reports for each person
- outline
- introduction/motivation (why do this)
- existing work/competitive solutions
- (major) iterations you’ve gone through, to show how you arrived at your product:
- what was validated
- how you did
- outcome of validation, leading to next iteration
- discussion and conclusion (including possibly ethics considerations if not covered previously)
- individual contributions to the project (did all contribute equally, or was there some division of work/areas of responsibilities) *)
- references *)
- appendices with your artefacts (LP, LC, USM, WF, Validation, ...) *)
- individual reflections as one appendix; max 0.5 page pr person *)
For the individual reflections, each person may chose one topic from the list below. Two persons in the same group are not allowed to pick the same topic. For the chosen topic, please 1) in our own words, briefly define the concept, referring also to the course material, 2) explain how it relates to the learning outcomes of the course, and 3) reflect on how it has provided value to the present assignment and what went well and that could have been improved with respect to the topic.
The topics for the individual reflections are:
- Minimum Viable Product
- User Story Map
- Usability
- Microinteractions
- Elements of Value
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):
This page will be permanently deleted and cannot be recovered. Are you sure?
|
