• 2015-01-26 — 2015-05-13
  • Mon & Wed 5:00PM - 6:15PM
  • 4085.582.01
  • Orange Hall (ORN)-1375
  • remydcsi@rit.edu

FINAL

TBA

Team Evaluations 15%

  • 200-1000 words per teammate.
  • Indicate what they did to contribute to the project.
  • What skills did they pick up this semester?
  • What skills should they develop further?
  • Give a numeric score (1-10) for them and justify it.
  • These must be emailed to the professor They will remain private.

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?)

Finished Project 20%

  • Your grade here will be derived from the following factors (adjusted for progress over the quarter):
    • Is the code clearly licensed under an OSI-compatible license?
    • Does your source repository contain clear written instructions for future developers? (i.e. How to setup their environment to work on your project)
    • What TODO items are left to do?
    • Does it work on python on a normal machine?
    • Does it work on the OLPC?
    • Code quality and git commit history.
    • Quality of the wiki entry at sugarlabs.org