image flickr com photos rowanhill design project with op
play

Image: www.flickr.com/photos/rowanhill/ Design Project with OP and - PowerPoint PPT Presentation

Image: www.flickr.com/photos/rowanhill/ Design Project with OP and Elisa CS-E5200 Design Project 10 ects Innovating new concepts related to Mobility as a Service (MaaS) special emphasis on an urban environment. Kick-off lectures @ OP 9.1. +


  1. Image: www.flickr.com/photos/rowanhill/

  2. Design Project with OP and Elisa CS-E5200 Design Project 10 ects Innovating new concepts related to Mobility as a Service (MaaS) special emphasis on an urban environment.

  3. Kick-off lectures @ OP 9.1. + Elisa10.1. Monday, January 9 @ OP 09:00 – 09:15 Welcome Håkan Mitts, Mika Nieminen 09:15 – 9:45 Future trends in Mobility Sonja Heikkilä, OP 09:45 – 10:15 Design for Mobility Zhang Aidong, Jonas Kronlund, Elisa 10:15 – 10:30 Break 10:30 – 11:00 Course intro + details Håkan Mitts, Mika Nieminen 11:00 – 12:00 Group formation Homework : Team pitch for Voice of Aalto

  4. Kick-off lectures @ OP 9.1. + Elisa10.1. Tuesday, January 10 @ Elisa 09:00 – 10:00 Voice of Aalto, team/mentor Håkan Mitts, Mika Nieminen pairing 10:00 – 10:30 Team/mentor initial meeting Break 10:30 – 11:00 Enablers of Mobility as a Jouni Lähteenmäki, OP Service 11:00 – 11:30 Capabilities of the Mobility Mika Viljanen, Elisa ecosystem 11:30 – 12:00 Case Whim Lauri Svam

  5. Course ”phases” • Phase 1 (~ period III) – User studies – Gain in-depth insights about your user segment – Discover un-met need, problem or desire • Phase 2 (~ period IV) – Design – Design and evaluate concepts to address issue from user studies • Phase 3 (~ period V) – Prototype & user testing – Build interactive prototype of final concept – Evaluate design using advanced user testing

  6. Combining user research, service design and lean startup Lean startup Service design Service concept Business model Business model feasibility canvas canvas Systematic exploration and iterative op’s Customer Prototyping Prototyping discovery User centric methods Combining the best of both worlds

  7. Simple development model Discover Alternatives Test Implement Take into use Collect Explore multiple Validate Methods specific Operational information solutions alternative to type of service aspects solutions Understand Alt 1 the user Software Identify and Capacity Alt 2 Prototypes frame the problem or Service Help-desk, opportunity User testing process customer Alt 3 service Interviews Collecting Service Safari feedback Alt 4 Spaces Complaints Market management Analyzing studies feedback Course target

  8. Two-week iterations Monday Tuesday Wednesday Thursday Friday Kick-off lecture Design + user/customer interaction planning Mentor meeting User/customer interaction Bi-weekly pitch

  9. Bi-weekly schedule • Week N:Mondays – 9:15 – 12:00 – Topical lectures & exercises • Week N&N+1: Independent work • Week N&N+1: One meeting with mentor • Week N+1: Fridays 12:00/12:30 – 16:00 – Team presentations • 5 minutes pitch – 1-on-1 feedback round with review team – Update of material in mycourses

  10. Summary of key deliverables 1. Bi-weekly MyCourses repository updates – Experiment Board (Javelin board) revision – BMC + VPC revision – User test reports (prototypes + analysis) – Mentor group selfie (preferably in Facebook) – Pitch slides 2. Team online/visual pitch 23.5. – Publicly available “marketing material” about your service 3. Final presentation Wed 25.5.

  11. 6. Pitch 5. Update 1. Derive most BMC + other critical hypothesis material 2. Design 4. Anayze experiments experiment to test results hypothesis 3. Execute experiments with real users

  12. Design is teamwork Software guy Domain expert Designer Project manager

  13. Diversity • Diverse, multi-skilled teams produce much better results that homogenous teams • However, this is true only if – Diversity is not seen as a problem – You work on understanding others – You appreciate the ideas and inputs of others • YOU are responsible for your work attitude!

  14. Experiential learning • Don’t believe what I say, believe what you experience yourselves – Changing your attitudes, values and views • “You cannot experience the experience before you experience it” • Experiential learning requires participation – No way to “compensate”

  15. Experiential learning basics Oppor- Attitude Effort Result tunity Design Your responsibility project

  16. Mentoring • A unique opportunity to learn from the best • Mentors volunteer to help you – NOT to do the work for you • Not paid – doing it for you! • Deserve the utmost respect for their effort – Be very mindful of meeting times etc – The whole team meets with the mentors • Any complaint from the mentors on student (mis)behavior results in failing the course – Includes not attending mentoring meetings

  17. Critical success factors • Team co-operation – Very tight schedule, start NOW – Everyone is needed all the time • Team organization – Define clear roles and responsibilities – Team leader could play a critical role • Meaningful division of labor – Good results are achieved with active co-operation – Every team member must be an active contributor – Maximize parallel processing – Feedbacks, comments, improvement ideas etc fuel a successful team

  18. Some practical stuff • Comms • Facebook group for informal comms • Find group DesignProject2017 and ask join it • facebook.com/groups/DesignProject2017/ – MyCourses forums for team deliverables • Contact info: – hakan.mitts@aalto.fi - 050 408 5622 – mika.nieminen@aalto.fi - 040 731 2625

  19. One final note: No online theft! • http://freemusicarchive.org/ • https://www.flickr.com/search/?text=picture& sort=relevance&license=1%2C2%2C3%2C4%2 C5%2C6%2C9 • http://pixabay.com/ • https://openclipart.org/ • ...and many, many more!

  20. PASSING THE COURSE

  21. Passing the course • Individual requirements – Actively contribute to team/group work • Work is not a valid reason not to participate! • To be on the safe side, agree with H&M about any absences • Complaints of undue absence by rest of team or from mentors will result in failing the course. – Present in 7/9 Friday feedback and pitch sessions • Group requirement – All deliverables done and stored in MyCourses – Deadline 23.5.

  22. Grading and credits • The course can only be done for 10 ECTS – 10 ECTS = 10 x 27h = 270 hours of work/person – 9 sprints => 30 hours/sprint => 15 hours/week => 2 full working days/week – Lectures + mentor meet-up ~10 hours/sprint – 20 hours work/person/sprint – …For a grade of 3! • The course will be graded per team – All team members will get the same grade – Non-participation of a student will not result in a lower grade, the student will simply not pass – You cannot compensate later for a low grade/fail • Grading will be based on – Feedback/review sessions: 50% – Documentation in MyCourses: 50% – Exceptional final presentation can give: +1 grade

  23. Criteria 1 : Process and methods ❺ The team applies appropriate research methods throughout the project. ❸ The team shows evidence of understanding some research methods in the field of his project work. ❶ The team shows very limited evidence of knowing and understanding research methods in the field of his project work.

  24. Criteria 2 : Grounding in data ❺ The work is clearly focused and grounded in the information gathered by the team. Makes proposals on how results could improve things. ❸ The work shows understanding of real-life problems related to the research field and results ❶ The work shows limited understanding of real- life problems related to the research field and results

  25. Criteria 3 : Value and sustainability ❺ The team relates the value proposed in the project to all relevant stakeholders including producers, customers, shareholders, communities, ecological systems and policies as appropriate. ❸ The team shows awareness of the relation of value to producers, customers, shareholders, communities, ecological systems and policies. ❶ The team shows only limited awareness of the relation of value to producers, customers, shareholders, communities, ecological systems, policies.

  26. TEAMS 2017

  27. Team building criteria • Equal distribution of non-Finnish students – In some situations you just have to be able to speak the local language • Equal distribution of students from different disciplines – HCID – Aalto BIZ – Information networks – CS – Other • Please rename your groups by tomorrow!

  28. Team Apple alessandro.capra@aalto.fi niko.hakanen@aalto.fi matias.hamalainen@aalto.fi auli.rantanen@aalto.fi hanyue.zhou@aalto.fi Photo by https://www.flickr.com/photos/lapstrake/

  29. Team Orange elena.kazakova@aalto.fi thomas.langerak@aalto.fi lauri.s.loikkanen@aalto.fi eveliina.vakeva@aalto.fi timo.overmark@aalto.fi Photo by https://www.flickr.com/photos/wgyuri

  30. Team Peach anar.bazarhanova@aalto.fi jenna.leinonen@aalto.fi susanna.nevalainen@aalto.fi leyang.pan@aalto.fi miika.ruissalo@aalto.fi Photo by https://www.flickr.com/photos/bestpicabusen

  31. Team Strawberry jarno.kilander@aalto.fi tomi.m.laakso@aalto.fi anna.lampinen@helsinki.fi loan.le@aalto.fi milda.norkute@aalto.fi Photo by https://www.flickr.com/photos/dmelchordiaz

  32. Team Pineapple susanna.immonen@aalto.fi milla.kruskopf@aalto.fi nico.liljestrand@aalto.fi prashamsa.mishra@aalto.fi abhishek.shetty@aalto.fi Photo by https://www.flickr.com/photos/misakhan

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend