cs-e5200 design project 10 ects - mycourses.aalto.fi · cs-e5200 design project 10 ects. ......

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

Innovating new concepts

related to Mobility as a Service (MaaS)

special emphasis on an urban environment.

Design Project with OP and ElisaCS-E5200 Design Project 10 ects

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

Kick-off lectures @ OP 9.1. + Elisa10.1.

Tuesday, January 10 @ Elisa

09:00 – 10:00 Voice of Aalto, team/mentor pairing

Håkan Mitts, Mika Nieminen

10:00 – 10:30 Team/mentor initial meeting

Break

10:30 – 11:00 Enablers of Mobility as a Service

Jouni Lähteenmäki, OP

11:00 – 11:30 Capabilities of the Mobility ecosystem

Mika Viljanen, Elisa

11:30 – 12:00 Case Whim Lauri Svam

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

Combining user research, service design and lean startup

Lean startup Service design

Service concept feasibility

Business model canvasSystematic exploration and iterative op’s

Business model canvas

Customer discovery

Prototyping PrototypingUser centric methods

Combining the best of both worlds

Simple development model

Discover Alternatives Test Implement Take into use

Understandthe user

Interviews

Service Safari

Collectinformation

Explore multiplesolutions

Validatealternativesolutions

Marketstudies

Alt 1

Alt 2

Alt 3

Alt 4

Prototypes

Methods specificto type of service

Software

Serviceprocess

Spaces

Operationalaspects

Capacity

Help-desk,customer

service

Identify andframe the

problem oropportunity User testing

Collectingfeedback

Analyzingfeedback

Complaintsmanagement

Course target

Two-week iterations

Monday Tuesday Wednesday Thursday Friday

Kick-offlecture

Bi-weeklypitch

Mentormeeting

Design + user/customer interaction planning

User/customer interaction

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

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.

1. Derive mostcritical hypothesis

2. Designexperiments

to testhypothesis

3. Execute experimentswith real users

4. Anayzeexperiment

results

5. UpdateBMC + other

material

6. Pitch

Design is teamwork

Designer

Software guy Domain expert

Project manager

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!

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”

Experiential learning basics

Oppor-tunity

Attitude Effort Result

Your responsibilityDesignproject

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

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

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

One final note: No online theft!

• http://freemusicarchive.org/

• https://www.flickr.com/search/?text=picture&sort=relevance&license=1%2C2%2C3%2C4%2C5%2C6%2C9

• http://pixabay.com/

• https://openclipart.org/

• ...and many, many more!

PASSING THE COURSE

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.

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

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.

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

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.

TEAMS 2017

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!

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/

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

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

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

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

Team Kiwi

nagadivya.balasubramaniam@aalto.fi

kaisa.halmetoja@aalto.fi

kenneth.lindroos@aalto.fi

niklas.nisen@aalto.fi

laura.walden@aalto.fi

jiayao.yu@aalto.fi

https://www.flickr.com/photos/pmillera4/

Team Saskatoon

dicle.ayzit@aalto.fi

atte.hanski@aalto.fi

minni.kuusisto@aalto.fi

anna.nermes@aalto.fi

lichang.zhang@aalto.fi

Photo by https://www.flickr.com/photos/dbarronoss

Team Pitaya

abc@aalto.fi

abc@aalto.fi

abc@aalto.fi

abc@aalto.fi

abc@aalto.fi

Photo by https://www.flickr.com/photos/blumenbiene

FIRST HOMEWORK

Tuesday pitches

• Team introductions to the mentors

• In 2 minutes or less tell:– What do you want to achieve?

– What you want to learn?

– What you are good at?

– Who you want to play with and why?

• After your pitches the mentors choose their team on first-come-first-served basis

Hints

• Might be a good idea to find out who the mentoring companies are before tomorrow…

• Pitching hint of the day: Google for “Simon Sinek Start with why”