1 / 20

SISYA200 Innovation Project 2013-14 Periods III-IV

SISYA200 Innovation Project 2013-14 Periods III-IV. Course homepage: http://www.uta.fi/sis/yhteiset/innovaatioprojekti/index.html Timo Poranen (UTA/SIS, responsible teacher) + other project supervisors from UTA/SIS + Demola staff Email: timo.t.poranen@uta.fi

rusty
Download Presentation

SISYA200 Innovation Project 2013-14 Periods III-IV

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SISYA200Innovation Project 2013-14Periods III-IV Course homepage: http://www.uta.fi/sis/yhteiset/innovaatioprojekti/index.html Timo Poranen (UTA/SIS, responsible teacher) + other project supervisors from UTA/SIS + Demola staff Email: timo.t.poranen@uta.fi www-page: http://www.sis.uta.fi/~tp54752 Office: B1023

  2. Initial lecture 17.1.2014 • What is Demola? http://www.youtube.com/watch?v=vDo7u6Fwfaw • Experimental Mobile Haptic Game: Commander • Nokia Kinetic Prototype of bendable smartphone • Course information: • Curriculum • Example project: LiveManual (project phases) • Credits and grading, schedule • Demola profile, project applications • Moodle (course registration, discussion forum), Project blog • Teacher’s role, problems, recommendations • One more sample project: YLE's Virtual Studio + NABC pitch • Questions and answers

  3. Demola – www.demola.fi Video: What is Demola? http://www.youtube.com/watch?v=vDo7u6Fwfaw

  4. Curriculum • Course for all SIS students. • Intermediate studies in Computer Science, Information Studies and Interactive Media, and Interactive Technology. • Students work in a project team to produce a demo or an interactive demonstration. • Teams have students from TAMK, UTA and TUT. • A Demola facilitator and university supervisors support the team. • The course is organised with Demola and teams work daily in the Demola premises. • Project topics are related to new technology and services (new mobile phones, innovative www/mobile applications, cyber glasses, augmented reality, games, new service concepts, etc.). • Learning goals: http://www.uta.fi/sis/yhteiset/innovaatioprojekti/curricula.html

  5. Course’s suitability • I have studied course TIEA4 (Project Work). Can I still take Innovation project? • Yes. Your credits can be used in other studies -category. • I'm majoring in Interactive technology. Can I study Innovation Project (SISYA200) instead of Project Work (TIEA4)? • Yes. • I’m majoring in Software Development / Information systems. Can I study Innovation Project (SISYA200) instead of Project Work (TIEA4)? • No, SPM (TIETS19) still require TIEA4. • I'm majoring in Information studies and interactive media. Can I study Innovation Project (SISYA200) instead of Interactive Media Project (ITIMA25)? • Yes.

  6. Project lifecycle • Reviews: Project plan review, 2 mid-project reviews, final project report review. • Deliverables: Project plan, final report, NABC (Need, Approach, Benefits, Competition) pitches (“presentations”), project blog and Demo. There might be other deliverables too! • Workshops. • Kick-off and graduation events.

  7. A sample project - LiveManual Source of the picture: http://www.tampereenkauppakamarilehti.fi/2012/pirkanmaan_taloudessa_tapahtuu/tal_tap_3_12_4.php

  8. LiveManual – project phases • Project Requirements Gathering - regular meetings with Metso to understand their needs. • Requirements Analysis - brain storming, listed all ideas which we thought of and realized them one by one based on the priority and implementation difficulty. • Concept Design – define what the new demo should be like, what kind of features should be there, for example how to show the navigation column etc. Draw different versions of the interface. Proceed based on these. Searched needed resources from the internet, self learning and transfer all those new ideas and knowledge into our product.

  9. LiveManual • Development – added needed features one by one. Meanwhile, continued to improve the interface design and made it look better. • Integration – put different parts together and integrate with the database. • Testing – we devised questionnaires and tested the manual. The test requirements and description were prepared in advance. The first test was done with some volunteers, the test subjects were students and those students had some IT related knowledge. The second test was done in Metso, with staff from different backgrounds. The test results were collected and discussed based on feedback and comments. Some issues that came up in the tests were fixed. • Demonstration & Possible Deployment – show the demo in the final customer meeting, if the customer wants, they can license the demo.

  10. Credits and grading • Credits are based on amount of (productive) work in your project. 1 ECTS corresponds to 20 hours of work in your project (5 ECTS equals to 100-119 working hours, 10 ECTS equals to >200 hours). • All students should work at least 100 hours (= 5 ECTS) for their project. • Working hours are reported weekly in the project blog. • Grading is based on the process, outcome and personal activity in the project.

  11. Schedule – main deadlines • http://www.uta.fi/sis/yhteiset/innovaatioprojekti/schedule.html • http://tampere.demola.fi/news/demola-spring-schedule-published • Join Moodle forum of the course no later than 26.1.2014. • Create Demola profile and apply for projects 26.1.2014. • Project plan deadline in February, a review after that. • Reviews / milestone meetings: March / April. • A review? What the team has done since last meeting, a demo, and what the team is going to do next. Feedback. • Final project report deadline in May, a review after that. • Graduation event 22.5.2014. • Credits and grading: May/June. • Training sessions, workshops, group work, and other project activities. Pitching (three times).

  12. Demola profile, project applications • Create a Demola profile and apply for interesting projects no later than 26.1.2014. • Pay attention on writing a good application. Skills and motivation are important. • You may (and should!) apply to different projects but you’ll be selected to one project. • In your profile/application tell your experiences, skills, hobbies, wishes, etc. • Course and Demola staff will inform you on your project before 4.2.2014 (Kick-off meeting). • It is possible that there is no suitable project for you.

  13. Moodle • All UTA/SIS students must join course’s Moodle forum. • Address: https://learning2.uta.fi/course/view.php?id=3444 • Forum name: SISYA200 Innovationproject – Spring 2014 • All important course messages (to UTA/SIS students) will be sent to the “News” forum. Demola has an own information channel (www.campwire.com) for their messages / news / guidelines to project teams (on workshops etc.). • Moodle’s discussion forum can be used for asking/commenting project/course related questions.

  14. Project blog • Project blog is a public web-based diary, where project team publishes the current status of the project. The project blog shows how the project is progressing in general. • Blog uses Demola’s project platform. • Regularity: Weekly /every second week. • It is important to bring out some key issues and challenges concerning the current stage of the project. • Team should divide the blogging so that each team member writes the project blog at some point. • Teams should report their working hours (John Doe, 15 hours this week, 60 hours so far. All project hours: 290.) and main activities done during the week (John: meeting with the client, review meeting with supervisor, usability testing, coding,…). • Check: Project blog cartoon (from “guidelines”).

  15. Teacher's role Each student has a responsible teacher assigned to him/her from the course. A team might have up to three supervisors from different universities! Teachers are there to support your learning and to help you Checking how you are doing To give help and support when you need it To watch the amount and quality of your work to verify that you can pass the course Teachers participate in main reviews (project plan etc.) and meetings and give feedback based on those. (They don't have time to participate in all of meetings.) Make sure that the teacher knows about all reviews and can participate.

  16. Guidelines • http://www.uta.fi/sis/yhteiset/innovaatioprojekti/guidelines.html • Important - All students must read these: • Demola-academy-students.pdf: Slide set for students (PDF) • Co-creation_meetings_checklist.pdf: Co-creation meetings checklist (PDF) • Student_checklist.pdf: Checklist for a student in a team (PDF, Important!) • Central_principles_of_project_work_checklist.pdf: Central principles of project work (PDF, Important!) • Project blog guidelines (PDF, important) • Optional • Checklist for project partner (PDF)

  17. Problems in your project? • It is normal that when a group of people is working together in a technical project, there might be problems with • Team members • Client • Technical devices • Design and implementation • Etc. • All teams should be able to solve “small problems” together, but in case of serious problems, contact project supervisor and Demola staff. • Tell about your project obstacles in review meetings and in the project blog.

  18. Findings from earlier projects • Meet your team at least weekly! Your project needs roughly 10-15 hours work / week. • More group work instead of working alone, participate in workshops. • Do not forget to inform your university supervisor on your project reviews. Preferably, days and times should be agreed in advance in the project plan review. • Use good project working practices: send a meeting agenda beforehand and write down meeting minutes (and send to all stakeholders). • Put your project’s name in email’s subject field. • Select and use suitable tools, enough management, … • Communicate (facebook, face-to-face, email,…). • Update project plan regularly and/or maintain tasks / work packages using some tool (excel, project management sotware,…).

  19. YLE's Virtual Studio project • Website: http://tampere.demola.fi/node/5016 • Tohloppi’s VIRTU is the only virtual studio in Finland that functions in daily production use. How could we utilize motion capture in our productions? • NABC from “mid project” pitching: http://www.youtube.com/watch?v=PGtQG5pfR0o • Efficient communication: blog posts, facebook-group.

  20. Questions and answers?

More Related