|
Week 13 - Final Presentation and Hand-In
Page last edited by Per Bækgaard (pgba) 02/12-2018
Monday December 3rd
| 08:00-11:00 |
Project Presentations (3(+2) min presentation and 5 min discussion pr group).
Groups 2-14, 21, 22 and 34 are in 324#060.
Groups 15-20 and 23-32 are in 324#040.
|
| 11:15-12:00 |
Final Lecture and Wrap-Up/QnA (306#035) |
Presentation format:
- Each group will present, based on the pdf file handed in at the end of week 12. This means that all presentations have to run off one computer in order save time and thus allow for more discussion.
- 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.
- The presentation will be followed by questions and comments for 5-7 minutes.
10 min is set aside for each group.
Please us this link for giving feedback to other groups (results here).
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 (e.g. Marvel) 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 Monday December 10th 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 Friday Dec 7th
- mark clearly who wrote and can be held responsible for each part (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
- individual contributions to the project (did all contribute equally, or was there some division of work/areas of responsibilities) *)
- references *)
- appendices *)
- 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, 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 what could have been improved with respect to the topic.
The topics for the individual reflections are:
- Minimum Viable Product
- User Story Map
- Design Thinking
- Microinteractions
- Gestalt Principles
- Lean Canvas
Examples of previous reports
The following are examples of reports you may be inspired by. 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?
|
