|
|||||||
|
|
20.10 Project Idea Presentations
Page last edited by Per Bækgaard (pgba) 09/11-2020
Monday November 9th
Learning objectives week 10Project idea presentationWe will use 4 different zoom channels for the presentations. Each group shall present their idea, using the slides that has been handed in, using at most 3 minutes (we will use a timer). Focus on making sure everyone else understands what problem is being solved, who are the users, how does the proposed solution look and how will it solve the problem. Be prepared to share your slides yourself via zoom, and remember to unmute yourself when you start presenting :-) Others that are not presenting should be muted. The channels may agree to run the slides from the TA/lecturer computer instead. Then we'll spend 2 minutes where everyone else gives comments in the chat. Comment on e.g. how you see this could work (or not), and give suggestions for things that could be improved. The TA/lecturer running the session will also give brief verbal comments. Each group should copy the comments from the chat or save it towards the end of the session so that they don't get lost. We will thus spend approximately 5 minutes for each group, and then we continue with the next group in turn until all groups have had their turn. When you're not presenting, make sure you listen and give feedback in the chat to the group that presented. DO THIS INDIVIDUALLY (not as a group). Here is an overview of the zoom channels to use; make sure you join the correct channel: Optoceutics: https://dtudk.zoom.us/j/63577078772 TripDoodler: https://dtudk.zoom.us/j/61165105537 Microinteractions: https://dtudk.zoom.us/j/67454545541?pwd=encwdi80bGZBd3lYbUdwRnhlWjdSZz09 Computerome and Others: https://dtudk.zoom.us/j/62423305524?pwd=WlYxNzVQc3UvNmNlQXNzTHZBUG5RQT09 Assignment week 10Continue working on your project based on feedback you have received in the project idea presentation session, and using the methods you have learned throughout the course: Iterate your project idea, each time validating with other groups or - strongly preferred and much 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. NOTE: Pick your tools wisely; spend most effort where it makes sense, in order to work efficiently towards a validated minimum viable prototype. 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. Upload the latest iteration of your project idea by Sunday 16:00 to the campusnet assignment folder. Next week, we will do peer-reviews 2-3 groups together, spending 30 min on reviewing and asking critical questions to one another. |
||||||
