PRESENTATION Team Assignment Due: Monday, May 5 (presentations given 1-4pm in Wean 5310) Prepare a 10 minute (+/- 1 minute) presentation on your project. Provide a brief introduction to your project, then describe your accomplishments. Include a screenshot or demo, if feasible and appropriate. Describe the challenges you faced, what you did to overcome them, and what you would do differently next time (if anything). Provide summary statistics for your work this semester, including: * A graph showing cumulative earned value for each week (i.e. a monotonically increasing graph) * An analysis of whether your effort estimation improved over the course of the semester * Other data you collected that you think will be interesting to the class, if any Finally, describe what you learned in the class. This may include skills and knowledge both from the domain you are working in as well as general software engineering and teamwork. Please expect 2-3 minutes of questions after your 10 minute presentation. ONE PAGE REPORT Team Assignment Due: Monday, May 5 (11:59pm) Prepare a one page report on your project. The audience is your classmates, the instructors, and potentially also an Open Academy panel consisting of: * Scott Chacon, Github * Andrei Alexandrescu, http://en.wikipedia.org/wiki/Andrei_Alexandrescu * David Hornik, August Venture Captial The report can be in any format. Themes suggested by Jay Borenstein and the Open Academy faculty leaders include "what you feel best about with respect to your efforts," "what you feel has been most challenging," and "what you are going to accomplish going forward." Lessons learned (technical, interpersonal, or personal) are likely also an appropriate topic. Charlie and Jonathan can nominate 4 of these reports to be passed on to the Open Academy panel. The Open Academy panel will further select some of the teams nominated by CMU and other universities for special acknowledgment, which will come with an Oculus VR Development Kit 2 (in July). So there are incentives to produce a polished one pager! INDIVIDUAL REFLECTION AND EVALUATION Individual Assignment Due: Monday, May 12 (11:59pm) In a 1-1.5 page document (single-spaced, 12-point font), answer the following question: If you were to do the project over again, how could you do it better, and how does that relate to software engineering principles? Discuss both process and product issues. Product issues include criticisms of and suggestions for improvements to the design, architecture, or implementation of your system; the platform or libraries you chose to build on; etc. Process issues include how you worked with your team, how you interacted with your mentors, any process you followed while developing code, writing tests, making pull requests, or performing reviews. You can of course discuss issues in your project with your teammates, and indeed will need to do so in preparing the final project presentation. However, the write-up should be your original work in your own words, and should describe your personal perspective whether or not that is the consensus of the team (you may criticize team decisions, for example). Grading: Your individual evaluation will be used to assess your level of knowledge of the project, your understanding of software engineering principles, and your ability to apply them to the specific setting of the project and clearly discuss your findings. It will not be used to grade the project itself, and any problems you point out will not decrease your score for this or any other assignment. Therefore, you should not hesitate to discuss flaws in the design of your system or process mistakes you made—indeed, this is your opportunity to demonstrate that you learned from them. 360 DEGREE PEER EVALUATION Individual Assignment Due: Monday, May 12 (11:59pm) If you are on a team with at least 2 members here at CMU, fill out the peer evaluation document. Do so on your own, without discussion with your teammates. If you are currently on a 1-person team, or worked entirely independently from your teammates, you do not need to do this assignment. If in doubt, ask.