IT issues Solvin-Hackathon Presentation

IT issues Solvin-Hackathon Presentation

ITECH1101 IT issues  Solving CRICOS Provider No. 00103D ITECH1101 Hackathon Assignment Specification 1817 Page 6 of 10 Part 3: Hackathon Presentation At the conclusion of the hackathon, each person must provide a short individual presentation about their hackathon experiences in their scheduled laboratory. This presentation will: • introduce the main problem that the team attempted to solve for the hackathon. • identify a personally-significant moment experienced during the hackathon and discuss what made this significant. A significant moment may include events that were challenging, particularly emotive (satisfying, frustrating, etc) or that had a large impact on the work performed during the hackathon. • identify ONE problem personally encountered during the hackathon, and discuss the problem solving techniques or strategies used personally to address this problem and how (and why) these were used. Note: team members must not choose the same problem to discuss. You will need to coordinate with your team to ensure different problems are selected. • reflect on personal learning and responses to challenges encountered during the hackathon, including understanding of course concepts, personal skills in problem solving and the role of mindset. Each presentation should not exceed 5 minutes. Any presentation aids readily available to students may be used, but students are responsible for ensuring these will work in the labs and having a backup available in the event of an issue. You are also required to complete a peer review of two presentations conducted by other students in your laboratory class. You will be allocated two student presentations to review at the start of the laboratory class. Peer review forms will be provided in the class. Submission Your initial design documentation must be submitted in the Workshop and Assignment link provided in Moodle, as a .pdf file. Your peer reviews will also occur directly in this Workshop link. Your work journal must be created in the Mahara ePortfolio and submitted in Moodle at the assignment dropbox provided. This must be separate from your ePortfolio journal entries. Your documentation, including all code, models, test cases and test results, must be zipped into a single file and submitted in the assignment dropbox provided. This includes the final version of the design documentation, incorporating any changes to the documents that occurred during the hackathon, and the final version of any supporting documentation referenced in your work journal. You will also submit a copy of the feedback you provide to your peers on their presentations in the week 11 lab in this link.

Order from us and get better grades. We are the service you have been looking for.