Final Project Presentation • Monday, May 6th • Begins sharply at 8:00 AM in ERB 103 • Each team has 35 minutes for: • Presentation (30 min) • Q & A (5 min) • Store presentations on your computer or a USB drive. Email a copy to the instructor and the GTA before 8:00 AM on presentation day. • Demos will be set up in ERB 208 (lab) before 7:30 AM and done after the last presentation • Poster board is set up with demo
Final Project Presentation • Order/timing of presentations is: • 8:00 – 8:35 AM Team Checkmate • 8:40 – 9:15 AM Team Too • 9:20 - 9:55 AM Team PNI • 10:00 – 10:35 AM Team Roboball • 10:40 – 11:15 AM Team Mirrors, Inc. • 11:20 AM - 12:30 PM Demos & lunch Note: plan to begin your demo set-up early, and to be finished and in your seats in ERB 103 no later than 7:55 AM. Demos should be planned (and rehearsed) to last no longer than 10 minutes per team.
Final Project Presentation Content • Roles and Responsibilities of team members (1) • Project Overview & Product Concept(2) • Requirements Overview– Per baseline SRS (2) • Requirements Completion Summary/Analysis (green, yellow, red button next to requirements) • Design Overview (4) • Summarize ADS and DDS, design trade-offs • Test Plan Overview& Results report (2) • Project Effort Assessment: (1) • Lines of code, hardware, earned value, time spent … • TEAM Lessons Learned (1)
Final Project Presentation Hints for Success: • Dress professionallyand present at your best • SPEAK UP - Project your voice to the back the room • Hands out of pockets • Eye contact with entire audience • Rehearseas a team – coach each other • Stay on topic – be crisp, concise, don’t ramble • Use graphics, pictures wherever possible to liven up the presentation • Practice your demo so you can show what you’ve done in no more than 10 minutes.
Final Project Presentation Other Info: • Friends, family, significant others are invited/encouraged to attend • Please attend a short celebration in the lab area after demos (approx. 12:30 PM). • Each demo setup must include a 3-part posterboard project summary • Picture of team, title of project, key roles & responsibilities • Product concept/description • Architectural design diagram • Key requirements, with completion indicator • Lessons Learned • Photos, etc. as required
Final Presentation Scoring • Final Presentation Score by peer, GTA and instructor evaluation rubric (on website) • Final Product Scoring by instructor per following scale.
Final Product Scoring Guideline • 100: fully operational prototype, fully functional per plan, professionally packaged (extremely rare) • 95-99: operational prototype, with minor functional deficiencies, cleanly and neatly packaged (rare) • 90-94: operational prototype, some major functional deficiencies, packaged well as a prototype (common) • 85-89: operational prototype, numerous functional deficiencies, not well packaged (most common) • 80-84: functioning prototype, with minimal features operational, not well packaged or not packaged at all (frequent) • 70-79: non-functioning prototype, unable to demonstrate key/critical features, prototype is not worthy of display (occasional) • <70: non operational bread-boarded design only, numerous functional deficiencies, unable to demonstrate critical features (rare)