Global Team-Based Product Innovation & Engineering II, ME 310 (Sommersemester 2015)
Dozent: Dr. Matthias Uflacker
Website zum Kurs:
- Semesterwochenstunden: 4
- ECTS: 6
- Einschreibefrist: 24.04.2015
- Lehrform: Seminar
- Belegungsart: Wahlpflichtmodul
- Maximale Teilnehmerzahl: 8
Studiengänge & Module
- IT-Systems Engineering A
- IT-Systems Engineering B
- IT-Systems Engineering C
- IT-Systems Engineering D
- IT-Systems Engineering Analyse
ME310 is a course where master students from the Hasso Plattner Institute (HPI) and leading global universities tackle Design Innovation Challenges posed by global corporations.
Who could explain this course better than Larry Leifer? Right, nobody. Here you go: Tele Task Video. But if you just want the brief, continue reading, below.
Students from Potsdam and leading global partner universities tackle design innovation challenges posed by global corporations. The course lead by Stanford University is focused on teaching students the innovation methods and processes required for designers, engineers, and project managers of the future. Through the projects, students go through an intense and iterative process of need finding, ideation, and rapid prototyping to create and evaluate new concepts. Company involvement provides the reality check necessary for teams to improve their innovation abilities. A professional coach, corporate liaisons and faculty advisors support the teams. Projects typically involve systems integration and include a mix of mechanical, electronic and software design. The results of all projects are real prototypes that have a user centric design, are economically viable and technically feasible. For more information, visit the Stanford course web site for Mechanical Engineering 310.
We expect from attending students their full commitment to the team and allow two days a week for this course. Candidates should present with in-depth technical knowledge, be passionate about the task at hand and prepared to dedicate their creative energy to the team's success.
The participants will be evaluated based on their participation in the weekly meetings of the course. These meetings are mandatory and structured as follows:
- A 3-min pitch about the activities of the previous week and plans for the following week
- 17min discussion with the teaching team about the project topic
- 20min internal discussion (with optional Teaching Team participation) about organisational topics
The 3-min pitch is given by one team member per week. Which team member is giving the talk is determined by a round-robin scheduling. The pitch can be supported by using pictures from a mandatory photo diary that the students need to keep during the project but no bullet point powerpoint slides are allowed. Each presentation is rated by the teaching team based both regarding the content (What has the team done in the last week?) and the quality of the presentation (information density, clarity of the presentation, expressiveness of the accompanying pictures).
In addition to the weekly pitch-presentations, the teams will be required to present their prototypes according to the deadlines stated in the course calendar. These presentation represent group efforts and require active participation by all team members. Powerpoint slides can be used, but only to support the presentation of a physical prototype, not to replace it. Prototype presentations without the presence of a physical prototype (running software does count as a physical prototype) will be postponed to the following week. Presentation duration is limited to 8 minutes.
In addition to the presentations, the students are required to provide documentation for their work at the beginning of December, end of March, and mid-June (exact deadlines are tbd).
Room E-U 1.1/1.2