Otto-von-Guericke-Universität Magdeburg


Startup Engineering II: Building a Minimum Viable Product

This is the home page for the course "Startup Engineering II: Building a Minimum Viable Product" in the winter term 2017/2018. General information on this course can be found here.


Application and Enrollment: 

Application for the winter term 2017/18 is possible via LFS during the period from September 1st through October 9th, 2017.


The module simulates a startup in which the participating students work as an intern. In order to participate, students work in two or three-person teams in software development. The teams will use technologies such as Slack & Trello for project management and team communication.  

Software Development 

The goal of the software team is to learn modern software engineering techniques typically used by startups. The Minimum Viable Product they build helps to validate a critiqual hypothesis of the startup.

Semester Plan

Preliminary semester plan for the winter term 2017/18:

Team Coach:
Schedule (tentative):



15:00 - 17:00

17:00 - 19:00

01 (KW41)  11.10. VL-01: Introduction VL-02: Project Specification
02 (KW42) 18.10. VL-03: The Lean Startup and Validation
03 (KW43) 25.10. Experimental Offer Presentation
04 (KW44) 01.11.    
05 (KW45) 08.11.    
06 (KW46) 15.11. Milestone Presentation 
07 (KW47) 22.11.    
08 (KW48) 29.11.    
09 (KW49) 06.12.    
10 (KW50) 13.12. Milestone Presentation 
11 (KW51) 20.12.    
12 (KW02) 10.01.    
13 (KW03) 17.01. Final Presentation
14 (KW04) 24.01.    
15 (KW05) 31.01. Report


The type of exam for this course will be a "Hausarbeit". The exam (6 CP) will consist of the two parts:

Experimental Design
Minimum Viable Product

All reports and MVPs must be submitted by 1 pm on Wednesday, January 31st via mail to  

Template for the Final Presentation
  1. Product Idea: Describe the planned product and its target market.
  2. Hypothesis: What is the hypothesis that you want to validate? Why is this hypothesis important for product development?
  3. MVP:  
    1. What features and functions does an MVP require in order to study this hypothesis? What features and functions from the final product were not necessary?
    2. What do your test users need to see or experience in order for your experiment to produce meaningful results?
    3. How did you need to be creative in order to compensate for missing features or functions?
  4. Demo: Demonstrate your MVP to the audience.
  5. Experimental Design
    1. Describe in detail the experiment you propose that uses your MVP to validate your hypothesis.
    2. What variable will you measure during the experiment? Why is this variable an indicator for your hypothesis?
    3. What pass-fail criterion do you propose? Why this choice (and not, for example, a higher or a lower value?)
    4. Who should the test users be? Why them? How can you be sure that they are representative of your target market?
    5. What conclusions will you draw from each potential result of your experiment?
  6. Learning: What were your most important learnings from this project? (Unexpected difficulties, mistakes, teamwork, startups, …)
Letzte Änderung: 10.01.2018 - Ansprechpartner: Webmaster