1. SISYA200 Innovation Project 2016-2017 Periods I-II
Course homepage:
Timo Poranen (UTA/SIS, responsible teacher)
+ other project supervisors from UTA/SIS + Demola staff
www-page:
Office: B1023

2. Initial lecture 7.9.2016 Curriculum
Project management (TIETS19-Practice) at Demola?
What is Demola?
Some project videos
Needed skills – Padlet
Schedule, credits and grading, working hours, no project
Example project: LiveManual (project phases)
Moodle (discussion forum), Project blog
Teacher’s role, problems, recommendations, tools
One more sample project: YLE's Virtual Studio + NABC pitch, MATOC2C
Questions and answers

3. 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.
Project partner (usually from a company or an association).
Demola facilitators 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, drones, robots, etc.).
Learning goals:

4. 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.
Can I study Innovation Project (SISYA200) instead of Project Work (TIEA4)?
Yes. But you can always take them both.
I’m studying in Master’s Degree Programme in Software Development. Can I study Innovation Project (SISYA200) instead of Project Work (TIEA4)?
Yes, SPM (TIETS19) does not anymore require TIEA4.
But you can still take TIEA4, because these projects are more software development oriented.
I'm majoring in Information studies and interactive media. Can I study Innovation Project (SISYA200) instead of Interactive Media Project (ITIMA25)?
Yes.

5. Project management (TIETS19-Practice) at Demola?
I would like to get credits from TIETS19-Practise from a Demola project. Is that possible? Yes.
You must have studied earlier Project Work (TIEA4) and/or Innovation Project (SISYA200) and (TIETS19/Theory, Software Project Management - Theory).
Then you normally apply for a Demola project. In the application, mention that you are interested in doing project management tasks in your project (among other things!).
Then you participate normally in your Demola-project, but you must be active in project management related tasks (initiating, planning and design, executing, monitoring and controlling, communication, reporting, presentations, etc.).
Your name should be mentioned in the Playbook when management-related tasks are listed.
Supervising teacher gives more information on required activities in the project meetings.

6. Demola - http://tampere.demola.net/
Video: What is Demola?

7. Project skills
What is your personal super power that helps your team to be successful?
Password: demola
Think about it a couple of minutes, write down to the Padlet-wall your skill and how it helps your team.

8. Project lifecycle
Meetings: Playbook meeting, some mid-project milestone meetings, final meeting (final version of the Playbook).
Iterative project cycle: 1) brainstorm, analyse and design, 2) build a demo, 3) evaluate your demo.
Deliverables: Playbook (Project plan), final report (updated Playbook), three NABC (Need, Approach, Benefits, Competition) pitches (“presentations”), project blog and Demo. There might be other deliverables too!
Workshops. Kick-off and graduation events.

9. Project lifecycle Schedule
4.9. Registration. After that, team forming.
14. – Initial Meetings – First meeting with the team
26.9. – Playbook Meetings – Delivering initial playbook
Mid-pitching Event – 3-minute Pitch
12.1. Final Pitching Event& Graduation
9. – Final Meetings – Delivering the Result Package
Credits and grading: January / February 2017.

10. A sample project - LiveManual
Source of the picture:

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

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

13. 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 team members log their personal working hours.
Grading is based on the process, outcome and personal activity in the project.
If a student quits the course before the Playbook-meeting + 1 week, then there are no consequences. If a student quits the course after that, "fail" will be marked to the academic transcript.

14. Working hours
Each team member maintains a list of his / her working hours.
All students should work at least 100 hours (= 5 ECTS) for their project.
Working hours are reported in the end of the project in the Playbook.
An easy way to maintain working hours:
Shared Google drive sheet (name, day, hours, activity)
Timo, , 2 hours, UI design
Be ready to show your team’s hours in your meetings.

15. No project It is possible that there is no suitable project for you .
You can apply for a Demola project again in January 2017.
You can ask for a possibility to join TIEA4 project from the lecturer.
Study other courses.

16. Moodle All UTA/SIS students must join course’s Moodle forum.
Forum name: SISYA200 Innovation project – Fall
All important course messages (to UTA/SIS students) will be sent to the “News” forum. Demola has own information channels 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.
A short questionnaire after the project. To get credits you must answer the questions.

17. 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. Other platforms are also ok.
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.
Check: Project blog cartoon (from “guidelines”).

18. Development tools http://www.uta.fi/sis/tie/pw/tools.html
Subversion - version control for code
Balsamiq - UI design tool
Redmine - project management
Trello for project management (Kanban board), Slack or Flowdock for communication, GitHub or BitBucket source code.
Invisionapp for UI design.
Prezi for presentation.

19. Teacher's role
Each student has a responsible teacher assigned to him/her from the course. A team might have up to four 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 project meetings (Playbook etc.) and give feedback based on those. Teachers don't have time to participate in all meetings.
Make sure that the teacher knows when you have milestone meetings.

20. Guidelines
Important - All students should read these:
Central_principles_of_project_work_checklist.pdf: Central principles of project work (PDF, Important!)
Co-creation_meetings_checklist.pdf: Co-creation meetings checklist (PDF)
Student_checklist.pdf: Checklist for a student in a team (PDF, Important!)
Project blog guidelines (PDF, important)
Optional
Checklist for project partner (PDF)
Demola-academy-students.pdf: Slide set for students (PDF)

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

22. 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 Playbook 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, …
Communicate (facebook, face-to-face, ,…).
Update Playbook regularly and/or maintain tasks / work packages using some tool (excel, project management sotware,…).

23. YLE’s Virtual Studio Project
Website:
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:
Efficient communication: blog posts, facebook-group.

24. Questions and answers?