1. Amanda Shen | Christine Marie Acuario | Mike Kung | Robert Schwenz | Christopher Hoover

2. What Happened: Team size relatively small (5 person group) Little experience with web programming Ambitious Initial Goals How We Dealt With It: Had to cut features Looking Back: Early risk assessment was crucial Reflection: Feature Cut Feature Cut | Roles | Learning Curve | Paper Prototype | Architecture | Integration | Usability

3. Reflection: Feature Cut Initial Feature Set Question/Answer Management Spam Prevention Video Tutorial Saved Sessions Auto-Complete Box Stretch Features Grouping and/or Prioritizing Instructor Questions/Polls Instructor History Quick Questions Statistics Live Feed/Recording Interactive Tutorial Final Feature Set Basic Framework Q&A Management Auto-Complete Box Instructor Questions/Polls Timeline Graph Bug Report Help Page Grouping and/or Prioritizing Potential Features Spam Prevention Quick Questions Saved Sessions Statistics TA Account Live Feed/Recording Interactive /Video Tutorial Feature Cut | Roles | Learning Curve | Paper Prototype | Architecture | Integration | Usability

4. What Happened: Initially set roles to match individual interests How We Dealt With It: Members had to take on multiple roles Back end/Front end swapping Feature Cut | Roles | Learning Curve | Paper Prototype | Architecture | Integration | Usability Reflection: Roles Back end Back end leadFront endPM Front end lead

5. Looking Back: Early risk assessment was a good decision  Members prepared technologies for both front & back end Feature Cut | Roles | Learning Curve | Paper Prototype | Architecture | Integration | Usability Reflection: Roles Back end Front end Test Back end lead Test Front end Back end PM QA Front end lead UI Design Test

6. What Happened: Nobody was experienced in PHP, JavaScript, jQuery, Ajax, YUI Unfamiliar with Hudson, PHPUnit and JSUnit How We Dealt With It: Allocated time to ramp up on technologies Assess technologies to fit our needs Looking Back: Wasted some time researching independently rather than asking faculty Feature Cut | Roles | Learning Curve | Paper Prototype | Architecture | Integration | Usability Reflection: Learning Curve

7. Feature Cut | Roles | Learning Curve | Paper Prototype | Architecture | Integration | Usability What Happened: People raised concerns about distractions & usability Suggested new features How We Dealt With It: Interviewed participants outside of in-class activity Figured out which concerns were the most applicable to our customers Looking Back: Helped us make more informed decisions moving forward Reflection: Paper Prototype In-class exercise: testing Student Home

8. Feature Cut | Roles | Learning Curve | Paper Prototype | Architecture | Integration | Usability What Happened: Initially attempted to mimic the slides instead of concentrating on what would be helpful to us Members confused about what to do How We Dealt With It: Reached out to faculty for help revising our architecture Looking Back: Good decision to reach out to faculty early  helped clarify responsibilities and tasks Learned the hard way about architecture diagram Reflection: Architecture

9. Feature Cut | Roles | Learning Curve | Paper Prototype | Architecture | Integration | Usability Reflection: Architecture Initial Architecture – Front End

10. Feature Cut | Roles | Learning Curve | Paper Prototype | Architecture | Integration | Usability Reflection: Architecture Initial Architecture – Back End

11. Feature Cut | Roles | Learning Curve | Paper Prototype | Architecture | Integration | Usability Reflection: Architecture Revised Architecture – Front End, Back End

12. Feature Cut | Roles | Learning Curve | Paper Prototype | Architecture | Integration | Usability Reflection: Architecture Initial Architecture – Front End, Back End

13. Feature Cut | Roles | Learning Curve | Paper Prototype | Architecture | Integration | Usability Reflection: Integration What Happened: Spent more time integrating than actually implementing new features Even with our architecture, there was still confusion between FE and BE How We Dealt With It: Paired front end and back end developers Looking Back: Cleared up confusion and prevented merging issues Made integration seamless

14. Feature Cut | Roles | Learning Curve | Paper Prototype | Architecture | Integration | Usability Reflection: Usability What Happened: We were able to test with students & instructor Were not able to test in an in-class environment How We Dealt With It: During our testing, we tried to simulate “classroom” setting Looking Back: We are still not able to gauge how distracting Incognito is.

15. Thank you! Questions?