PC3 — Sprint Review 1

PC3 is due Monday, 2/17 at noon.

Sprint reviews are important as they serve as a way to review your work, both for yourself and your team.

You will work with your group to create a slide deck that consists of a presentation no longer than ten minutes.

Specification

Your sprint review should serve as a discussion of the work done in the past two weeks, any challenges encountered, and the plan for the next two weeks. Adittionally, there should be a demo of your project in some way or form. You should review your architecture in this presentation if there have been any major changes.

Resources

You can use this template slide deck as a starting point. You don't have to follow it exactly. Feel free to explain your project however you think is best.

Commentary

Based on your sprint review, you will receive feedback from the instructors and IAs. This will include suggestions for the future and ways to handle challenges. This sprint review does not have to be given by all members of your team--one oft-forgotten challenge is time management. With more time than the previous presentations, you should be able to incorporate mroe team members if desired, but having all, or even most, of your team presenting is not required, nor recommended.

Unlike the previous presentations, there will be more time for questions from both peers and the instructional staff. The idea behind opening the floor to questions is to help clear up any confusing parts of the project and make you think of solutions or alternatives to some of your design challenges, not quiz your ability to respond quickly. That said, being able to handle questions on the spot is an important skill that you will have the opportunity to develop.

Remember, the sprint review is designed to be a review of the work you have done in the previous 2 weeks. A substantial part of this hinges on that work actually being done. Instead of having code deliverables every few weeks, this is our way of checking up on your progress and making sure you are moving along at a satisfactorial rate and your grade will reflect this. We will be expecting a demo that showcases much of this work.

Hints

Previous groups have used Google Slides to produce slide decks. You are welcome to do so, so long as you turn in a PDF version of the slides.

Your presentation can be structured in any way as long as we can see the work you have done. Remember, we cannot grade something we don't see, so if you don't include some of the work you have done in the past two weeks, it will not be factored into your grade. If you do not have a full demo, including visuals of a UI or demoing snippets of your project is substantially better than showing us nothing.

Due to the scope of the class, it is impossible for the course staff to have full coverage on all topics that you may working with, such as specific backend servers and APIs. That being said, the course staff is willing to help you find the resources you need to complete the project. This is an ecnouragement to come to office hours early so we have time to find you resources that will help if you do run into problems and need help.

What To Turn In For PC3

You will turn in a single teamX.zip file consisting of a single PDF file:

• teamX.pdf, containing your group's sprint review slides.

Grading Rubric

PC3 Grading (out of 15 points):

• 2 points — Clarity of presentation materials
• 2 points for clear, well-organized, structured, numbered slides; clear and relevant figures
• 1 point for adequate slides
• 0 points for missing slides, poor organization, missing slide numbers
• 5 points — Presentation oration
• 5 points for clear, projected speech that is demonstrably rehearsed and presented in a professional manner.
• 3 points for good speech, not too much stumbling
• 1 point for unclear speech, unrehearsed, questionable organization, lack of professionalism
• 0 points for poor, low speech, no engagement with audience, poor time management
• 3 points — Project management
• 3 points for demonstrating that there has been progress made over the last sprint and a well developed plan has been discussed to correct any issues and ensure that the project be completed on time.
• 2 points for demonstrating progress. The project may be falling behind and the team has thought about potential issues but appropriate plans have not been discussed to ensure project completion.
• 0 points for sprint reviews that demonstrate little or no progress and have no plans to correct issues.
• 3 points — Project design and implementation
• 3 points for projects that demonstrate a sound technical design. These teams will have designed an architecture that covers a front-end, back-end, the Clinc platform, at minimum. If there are any unknowns, there must be plans on how the team plans to fill in these technical gaps using trade studies, testing, or other means. These projects will also have incorporated any project specific requirements given by the course staff into their design.
• 2 points for projects that demonstrate an adequate technical design. These teams will have designed an architecture that covers a front-end, back-end, the Clinc platform, at minimum. There may be unknowns and the team has not developed sufficient plans to fill in these technical gaps. The team has incorporated some of the project specific requirements given by the course staff into their design.
• 1 point for projects that do not demonstrate sufficient technical design. These teams will have a start to a project architecture but it may be incomplete. There are unknowns with insufficient plans to fill in these technical gaps. The project plan may not satisfy all requirements as is.
• 0 points for projects that have little or no technical design. These projects are grossly underdeveloped at this stage.
• 2 points — Demo. The demonstrations can occur entirely within the Clinc platform.
• 2 points for demos that demonstrate progress has been made. Transitions are demonstrated for at least 2 competencies. There may be difficulties but they are not overwhelming
• 1 point for demos that demonstrate some progress has been made. At least one transition to a competency was demonstrated. There may be some difficulties.
• 0 points for no demonstration.