Wiki
Archive: 02809 E17

Lecture 13 - Final Presentation
Page last edited by Per Bækgaard (pgba) 03/12-2017

Monday December 4th

08:00-10:00 Group Presentations with Live Feedback
10:00-11:30 Group work

Assignment week 13

Continue iterating your designs, incorporating feedback you have received and finalise your report. Please use the 2-column ACM_SigConf template (part of ACM Master Article Template) 
to generate and hand in one single pdf file. The template exists in both Word and LaTex formats, but only the resulting pdf file should be uploaded. 

Hand-in your report as ONE PDF FILE which contains as appendixes 1) a landing page with marked value element, 2) a lean business canvas for your system, 3) sketching goals, activities and tasks in a user story map  that can be validated with 4) annotated (microinteractions, backend integration) wireframes showing both app/tablet/computer/... screens and 5) when applicable, a link to your Marvell prototype, by Friday this week at 23:00 to the DTU Inside (CampusNet) project area.

NOTE: DO NOT HAND IN TO PEERGRADE! USE THE CAMPUSNET ASSIGNMENTS AREA!

Details on the report (summary)

  • half a page pr person (i.e. 2 or 2.5 pages for actual report without couting the items marked with a *) plus appendixes 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 8th 
  • 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). 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).
  • 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 *)

Please refer to relevant (use of) tools, methods, terminology and theories in your main text.

Slides

Video lectures

Required Reading

Additional Links

Support: +45 45 25 74 43