danShumway
commented
10 years ago Quick sketch of what a presentation to work
Demonstration of the product - Pharas How does the code work? - mtubinus/danShumway What are some of the best/worst pieces of the code and why? - mtubinus/danShumway What documentation exists/setting up the wiki - djm6833
What stumbling blocks? -
- compiling for the XO - mtubinus
- design-centric Open Source - danShumway
What would you do differently? - All of us What would you have done if you had more time? - All of us Final evaluations - All of us
- playtesting (danShumway/Pharas)
Final Presentation 20% Your presentations should last 10 minutes with another 5 minutes for discussion. Your team will need to present from the front of the room. You can either: 1) Make your slides web-accessible, or 2) Email slides as a .pdf to your instructor. Every member of your team needs to speak for a roughly equal amount of the presentation. Be prepared. Give a demonstration of your project. How does the code work? What are some of the best pieces of software you wrote? Why? What are some of the worst pieces? Why? What stumbling blocks were there? What successes? What would you have done differently? What would you have worked on if you'd had more time?
Your Presentation will be graded on aspects such as: Presentation Skills (Projection, Posture, Body Language) Grammar/Spelling Design (colorschemes, graphics, look/feel) Timing (significantly over/under time limit) Content (quality/quantity of information) Adherence to Guidelines (Did you hit all the bullet points in this list?)