Grading
Students will be evaluated in the following ways that aim at simulating industry work.
| Item | Description | Type | Weight |
|---|---|---|---|
| Individual Assignments |
Unity Tutorial Demo Application Individual Project Brainstorm |
Individual | 5% |
| Group Planning Documents |
Team Brainstrom Project Pitch Project Requirements Document |
Group | 5% |
| Midterm + MVP Deliverables |
Midterm Presentation Minimum Viable Product (MVP) (MVP) Quality |
Group | 10% |
| 6 weekly updates (individual) |
Each update is graded compared to what was planned in PRD Code reviews Individual contribution to the team |
Individual | 60% (10% each) |
| Final Demo | Final application quality based on level of complexity, refinement, and holistic user experience | Group | 20% |
Deliverables and Tasks
Product Requirements Document (PRD):
After firming up the project idea, each team will be required to create a Product Requirements Document (PRD) that details all the various aspects of the project. It is written to allow stakeholders to understand what a product should do, and also serves as a guiding document for the team that is building the product.
The PRD should include a one paragraph summary of the project (summarize project proposal), deliverables (what will be delivered at the end), the features (ranked by priority), any performance metrics, milestones, responsibilities of each team member, materials and outside help needed, budget, risks, and how risks will be addressed. Teams will create the PRD early in the quarter and they will be used to compare progress over the span of the course.
PRD template: https://docs.google.com/document/d/1XZZ1UXkJmTesv3N0jhjIo9FAxPlNyNH5UVVq8RzEq6w/edit?usp=sharing
Weekly Snippets
Each team will be required to post weekly project snippets to the top of their PRD document detailing their progress. The teaching staff will use these snippets to perform code reviews and provide feedback. The snippet should consist of a bulleted lists of tasks for the week which contain:
- The current status (complete, in-progress, blocked)
- The team members who are assigned to the task
- Comments explaining why the task is in-progress or blocked
- Screenshots or recordings showing the task working if complete
- Links to specific files, commits, or pull requests in the project repo related to the task
The snippet should also include a list of tasks for the coming week and which project members are assigned to each.
Peer reviews
Teams will be conducting two group peer reviews during mid-quarter and end-quarter. This will involve giving demos of work to other teams and gathering feedback.
Demo Video
Create a video that presents what your app should accomplish (or what challenge it is trying to solve), the capabilities of your app and an example of how it is played or used (like the one you're going to demo during the final session). The videos are going to be played during the demo session and uploaded to the UW Reality Lab YouTube account. Examples of past videos. The videos can be approximately 1 minute long. Can include narration (kickstarter style) or just demonstrate technical features of your project.
Demo Plan and Rehersal
You will be required to come up with a demo plan, that includes the floor-plan layout for your space, any furniture/props and some signage for the team project. You will also need to prepare a demo 'script' and rehearse the script in the Lab, a week prior to the final demo day.
Demo Day
The final demo day will take place on campus tentatively on Tuesday, June 4. There will be a rehearsal, one week prior. Mark your calendars now! More details will be sent later in the quarter as they are confirmed.
It will be very exciting, fun, and a fitting end to the capstone! It will be open to friends, family and general public. We will also invite a number of guests from companies like Microsoft, Magic Leap, Google, Meta, Valve, and more!
Staff will evaluate final demos on complexity, refinement, wholistic user experience, and final demo presentation.
After the Capstone Ends
Your course related obligations end after demo day. However, some teams may choose to continue working on their capstone project in order to release it on the App Store, Open Source, etc. This is a great way to get your creations out into the world and gain recognition for your work! If your team would like to continue working on the project, please contact the course staff and we will be happy to help you!