SISYA200 Innovation Project Periods I-II Timo Poranen (UTA/SIS, responsible teacher) + other project supervisors from UTA/SIS and Jarmo Tuominiemi (Demola) + other facilitators from Demola

Initial lecture Video: Experimental Mobile Haptic Game: Commander Course information: – Curriculum, a sample project: LiveManual – Credits and grading, schedule – Demola profile, project applications – Moodle (course registration, discussion forum), Project blog – Teacher’s role, problems, recommendations Demola (Jarmo Tuominiemi) – Sample projects, Demola info Questions and answers 11.9 Demola Roadshow at UTA, demos ( ) and Demola presentations ( , B1096), location: entrance hall of Pinni B and lecture room B1096.

Curriculum New 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, games, etc.). Learning goals:

Course’s suitability I have studied course TKOPA12 (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 (TKOPA12)? – Yes. I’m majoring in Software Development / Information systems. Can I study Innovation Project (SISYA200) instead of Project Work (TKOPA12)? – No (SPM and ToSPM still require TKOPA12). I'm majoring in Information studies and interactive media. Can I study Innovation Project (SISYA200) instead of Interactive Media Project (ITIMA25) as my compulsory course? – Yes.

A sample project - LiveManual Students after real life solutions The first Demola Academy winner project was Live-Manual, a project ordered by Metso to develop a more user-friendly manual. Members of the Live-Manual team, Jussi Ahola, Eero Ojanperä and Tomi Turtiainen, say they could have achieved their credits with a lot less work… – … but that would not have been as rewarding. It would not have motivated us. And the opportunity of doing something in a new way offered by Demola was more important than the credits: a possibility of learning, using new tools and nimble techniques, getting experience in project work. – We learned by doing. Hitting on a solution that worked had a great energising effect on us.

LiveManual – project phases 1.Project Requirements Gathering - regular meetings with Metso to understand their needs. 2.Requirements Analysis - brain storming, listed all ideas which we thought of and realized them one by one based on the priority and implementation difficulty. 3.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.

LiveManual 4.Development – added needed features one by one. Meanwhile, continued to improve the interface design and made it look better. 5.Integration – put different parts together and integrate with the database. 6.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. 7.Demonstration & Possible Deployment – show the demo in the final customer meeting, if the customer wants, they can license the demo.

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 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.

Schedule – main deadlines Join Moodle forum of the course no later than Create Demola profile and apply for projects Project plan deadline in Oct, a review after that. Reviews: November and December. – A review? What the team has done since last meeting, a demo, and what the team is going to do next. Final project report deadline in January, a review after that. Graduation event Credits and grading: February. Training sessions, workshops, group work, and other project activities.

Demola profile, project applications Create a Demola profile and apply for interesting projects no later than 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, wishes, language restrictions (if you can’t participate in an English language project), etc. Course and Demola staff will inform you on your project in the end of week 38 (or in week 39). It is possible that there is no suitable project for you .

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

Moodle All UTA/SIS students must join course’s Moodle forum. Forum name: SISYA200 Innovationproject Key: SIS_inno2012F All important course messages (to UTA/SIS students) will be sent to the “News” forum. Demola has an own information channel for their messages/news to project teams (on workshops etc.). Discussion forum can be used for asking/commenting project/course related questions.

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. 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,…).

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.

Guidelines 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!) – Checklist for project partner (PDF) – Project blog guidelines (PDF, important)

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.

Findings from earlier projects Meet your team at least weekly! Your project needs roughly 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 ’s subject field. Select and use suitable tools, enough management, … Update project plan regularly and/or maintain tasks / work packages using some tool (excel, project management sotware, Demola’s project tool,…).

Demola –

Questions and answers?