Innovating new concepts for transportation in urban ...€¦ · Final presentation Wed 25.5. 1....
Transcript of Innovating new concepts for transportation in urban ...€¦ · Final presentation Wed 25.5. 1....
Innovating new concepts fortransportation in urban environments.
http://livinglabbus.fi/
Friday, Jan 5
Time Topic Speaker
09:15 – 09:30 Welcome Mika P. Nieminen
09:30 – 10:00 Theme overview: Smart Public Transport
Jani-Pekka Jokinen
10:00 – 10:40 LLB overviewLLB platform technology
Juho Kostiainen, VTTOlli Pihlajamaa, VTT
10:40 – 11:05 E-Fleet management Tom Granvik, Linkker
11:05 – 12:00 Intro part 2, Group formation Mika P. Nieminen
Monday, Jan 8
Time Topic Speaker
09:15 – 10:00 Voice of Design, team/mentor pairing Mika P. Nieminen, mentor companies
10:00 – 10:30 Team/mentor initial meeting Students + mentor company representatives
10:30 – 11:00 Public transport now and in the future Tuukka Hastrup, HSL
11:00 – 11:30 Future of ticketing as a service Tuomo Parjanen, PayiQMarko Nieminen presenting
11:30 – 12:00 Sprint 1 assignment Mika P. Nieminen
Course ”phases”
• Phase 1 (~ period III) – User studies & Problem Space– Gain in-depth insights about your user segment– Discover un-met need, problem or desire
• Phase 2 (~ period IV) – Concept 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 & UCD, service design and lean startup
Lean startup Service designService 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 modelDiscover 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:15/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 (in Facebook)– Pitch slides
2. Team online/visual pitch 25.5.– Publicly available “marketing material” about your
service3. 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
Domain expert
Software guy
Designer
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• Mentors are 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 DesignProject2018 and ask to join it• https://www.facebook.com/groups/DesignProject2018/
– MyCourses forums for team deliverables• Contact info:
– [email protected] 040 731 2625– [email protected] 050 5981 434– [email protected] 050 3684 763
One final note: No online theft!
• http://freemusicarchive.org/• https://www.flickr.com/search/?text=picture&
sort=relevance&license=2%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 M&J-P about any absences• Complaints of undue absence by rest of team or from
mentors will result in failing the course.– Present at 7/9 Friday feedback and pitching sessions
• Group requirement– All deliverables done and stored in MyCourses
• No links to cloud files, submit static documents– Final Deadline 25.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 3 (Good)!
• 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– Grading snapshots given after sprints 3 and 6
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 2018
Team building criteria
• Equal distribution of non-Finnish speaking students– In some situations you just have to be able to speak the
local language• Equal distribution of students from different disciplines
– HCID– CS– Information networks– Aalto BIZ, IDBM, USchool– Others
• Please rename your groups by monday!
Team Apple
[email protected]@aalto.fi
[email protected]@[email protected]
Photo by https://www.flickr.com/photos/lapstrake/
Team Orange
[email protected]@aalto.fi
[email protected]@[email protected]
Photo by https://www.flickr.com/photos/wgyuri
Team Peach
[email protected]@aalto.fi
[email protected]@[email protected]
Photo by https://www.flickr.com/photos/bestpicabusen
Team Strawberry
[email protected]@[email protected]
[email protected]@[email protected]
Photo by https://www.flickr.com/photos/dmelchordiaz
Team Pineapple
[email protected]@aalto.fi
[email protected]@[email protected]
Photo by https://www.flickr.com/photos/misakhan
Team Kiwi
[email protected]@aalto.fi
[email protected] *[email protected]
[email protected]@aalto.fi
https://www.flickr.com/photos/pmillera4/
Team Saskatoon
[email protected]@[email protected]
[email protected]@aalto.fi
Photo by https://www.flickr.com/photos/dbarronoss
Team [email protected] *
[email protected]@aalto.fi
[email protected]@aalto.fi
Photo by https://www.flickr.com/photos/blumenbiene
FIRST HOMEWORK
Monday pitches
• Team introductions to the mentors• In 2 minutes or less tell:
– What do you want to achieve?– What do you want to learn?– What are you good at?– Who do you want to play with and why?
• After/during your pitches the mentors choose their teams on first-come-first-served basis
Hints
• Might be a good idea to find out who the mentoring companies are before monday…
• Pitching hint of the day: Google for “Simon Sinek Start with why”
Mentors
• Solita• Eficode• Nitor• Digitalist• Vincit• Tulos• Siili