Results from the Mockup Review
To view a section's presentation and provide feedback, click on the links provided below. Each idea has been reviewed by at least 3 different course staff members.
Please do not make your final product selection before your lab next week. Use the time to consider the more details feedback you will receive over the next few days, to conduct additional tests or experiments with your mockups, and to make sure that you will have enough information to make an informed final concept selection. The goal is not to prepare for a contest, but to be in a position to make a wise product decision. Be open to new insights and changing your mind. If your lab is towards the end of the week and you feel you cannot wait, please make arrangements so that your instructors can be observers/facilitators for the decision process.
A scoring out of 10, based on the average of 24 instructors and staff that attended the review, is provided below. 10 was defined as outstanding, 8 commendable, 6 good, and 5 marginal. This score is not your grade and should not be used to determine your project selection. Also, remember that the main goal of the mockup stage is to learn the things needed to have a successful project at the end of the term, and to have an authentic product development learning experience.
The scores require interpretation... At MIT we are biased to appreciate hardware, even when that may not be the most critical risk that should be addressed. Not demonstrating hardware can lead to a low score. Opinions about key risks can vary considerably, but when the product specifications become more precise, both feedback and appreciation of achievement becomes more targeted. Good work may not have been clearly communicated, or taking on too many tasks may have resulted in not having the time to prepare and demonstrate what was accomplished. The notes from class attempt to offer additional insights.
(mockup execution, analyisis/risks) 24 reviewers
Analysis: risks and contract