The Final Report and Presentation should review your project and project plan, describe the execution and achievements of your project, and demonstrate functionality achieved. The specific components are outlined below. Grading will be based on successful coverage of everything below. A significant portion of the grading will be used to assess the completeness of the project as compared to the original project plan. Individual emails evaluating the team are also required and are described further below.
The Final Presentation is a professional quality multimedia slide-based (preferably Microsoft PowerPoint) presentation of your project along with a complete demonstration. See the Final Report section below for details on the content of your presentation. All team members are expected to participate in the presentation and have a professional appearance (e.g., no jeans, no tennis shoes, no T-shirts). Each team will be given 50 minutes for their presentation (45 minutes) and questions and feedback from the audience (5 minutes). The presentations schedule is as follows:
|Monday, July 30||1-2pm||SHINE|
|Monday, July 30||2-3pm||WHMS|
|Wednesday, August 1||1-2pm||CART|
|Wednesday, August 1||2-3pm||Tracker|
|Friday, August 3||1-2pm||RATS|
|Friday, August 3||2-3pm||TOMS|
Please let me know if you will need to present in the lab instead of the classroom.
The Final Report is a professional quality document detailing the information below. Your Final Report should be emailed to me (firstname.lastname@example.org) and published on your team's web site by the above deadline.
The Introduction should include your team/project name and your team members' names, titles, and contacts (email). The Introduction should also give a brief overview of the project, including the problem statement, solution, and benefits to the customer. Also, review the graphical diagram of your project.
Summarize the main components of your Project Plan, including milestones, deliverables, resource needs, schedule, quality control, project control, and documentation. Also, review the individual task plans for each team member, including a task description, relationship to other tasks, and any deviations from the original task plans.
Describe testing and documentation performed throughout your project. During the presentation, you should give a brief tour of your web site.
Describe the functionality achieved by your final project. Describe how this functionality is demonstrated during the final presentation. During the presentation, you will demonstrate this functionality using a working prototype.
Describe the general lessons you learned during the execution of the project, especially in the areas of project control and project team dynamics. Describe what future work you would recommend be performed to improve your project.
Include in your final report, or as a separate document, a User's Guide for your project. The User's Guide should be at a level of detail sufficient for someone like me to reproduce your demonstration using your final prototype. Required software should be emailed to me or available on your website. Required hardware beyond what will be left behind in the lab should also be described.
This section will not be part of the report, but requires an email sent to me from each team member evaluating all the team members (including yourself). The evaluation should be a number (1-5), where 5 is excellent and 1 is poor, and an explanation of why the team member deserves this numeric evaluation. Possible aspects to consider in your evaluation and explanation include distribution of workload, cooperation, initiative, and satisfactory performance of assigned tasks. For the team leader, also consider their leadership qualities. All evaluations will remain confidential. These emails are also due by the above deadline.