Second, the class will make a final, one-two hour, oral presentation of its solution in early December. This presentation will be open to the entire MIT community. In addition, a panel of experts will be invited to attend the presentation and to critique them in an open forum. Because it would be logistically difficult for everyone to speak during the presentation, the staff recommends that each team elect one member to join a presentation committee that will choreograph the final presentation. The committee member should not bear sole responsibility for the work involved in developing the presentation!

This second journal article should be a brief (1,500 words or less) compendium of the technical results that YOU specifically have contributed to your group’s work. It’s OK if you worked in pairs with someone, though please try to distinguish what you did if possible

Each week, your team should update your team’s wiki page. If you do a great job documenting everything, it will make your final report much, MUCH easier to write.

The wiki should include key documents (project specs, etc.), an ever-changing schedule, photos from experiments, scans of best brainstormed ideas, etc. It should also contain a weekly report on your communications with your community partner (you should do everything in your power — regular emails and/or phone calls to stay in touch) so that they are up to date on your progress and can offer feedback.

Problem set for the course D-Lab: Energy.

When designing a product that is to be produced beyond just the prototype stage, attention must be given to the resources that are available and to the sustainability of the manufacturing processes. 

As a team, determine the appropriate scale of manufacturing for your project: will they be made in the tens, hundreds, or millions? What design changes will need to be made as you shift from manufacture of a single prototype to the production of multiple units?