Students will be evaluated based on their commitment to the project (1/2) and the project outcome (1/2). The commitment to the project includes timely weekly project reports, showing effort, and peer evaluations. Project outcome will constitute the quality of your reports, deliverables, and demo. Thus, your grade will reflect the work perceived by the instructor, the TAs, your fellow students (both within and outside your group), and any mentors. You will be constantly given feedback in the class as to your progress, so you will know where you stand. Please notify the instructor of any team issues early!

Deliverables and Tasks

Initial Idea Online Post: Due Wednesday, October 10, Noon PT

With your team, post on Google Groups with the following information:

Initial Idea Pitch: In-Lab Thursday, October 11

Project Webpage for each team:

Each team is required to create a webpage that will include all the material created throughout the quarter. Every deliverable will be linked from your webpage. Teams can use any hosting service they like. The style should be like on Kickstarter, (Example). Keep the website simple so it easy for us to navigate.

Make sure to document everything and put it on the website (notes, pictures, videos, etc), and send us the link that we can add to the course webpage.

Please setup your website by Thursday, Oct 18, 23:59 (11:59pm), and send a link to vr-capstone-staff@cs. Initially, the website can contain a your initial project proposals (+any slides you used, & incorporating feedback/updates) and a short bio/background of the team members. You can update and improve your website as the quarter progresses.

This website will eventually have several components:

Here are some example (final) project websites from previous years:

Weekly Blogs:

Each team is required to maintain a blog on their team webpage. You will be required to update it on a weekly basis (due Friday at 7pm). Blog should at least contain:

  1. Summary: Overview of the last week's activities
  2. Progress: More detail on what has been accomplished in the past week. Include any designs, screenshots, notes for that week, or interesting technical challenges/solutions that you faced.
  3. Plan for next week: Goals and execution plan for the next week, including task breakup amongst team members. Also think/write about the 'demo' that you will show the staff in next week's lab.

These will be graded weekly.

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 your project. It is written to allow stakeholders to understand what a product should do, and also allow serve as a guiding document for the team that is building the product.

PRD should include a one paragraph summary of the project (summarize your project proposal), deliverables (what are you going to deliver 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. You will be asked to do this very early in the class and then update your PRD throughout the quarter. We will use the PRD to see how your end product matches your PRD, so make sure to keep it up to date. Your PRD should be on your website.

PRD template:

Weekly meeting with staff:

You will meet for 15 min weekly with the instructors in SIEG 327. Every Thursday between 1:30 - 4:20. You will describe your progress during the past week, present any demos, and discuss the plan for the upcoming week. The staff can also help answer any questions or resolve blocking issues.

Week 7 Progress report to the class:

Each team will do a 10 min presentation to the class during lecture time. We recommend using slides that motivate your problem, describe your current progress and include any demos/videos/sketches of your system. This is a great opportunity to gather feedback from your peers.

Peer reviews

You will be conducting two teammate group peer reviews during the quarter, around week 7 and week 11 (finals week). This will involve giving demos of your work to other teams and gathering feedback.

Demo Video

Create a video that presents 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 placed on your websites. Examples of last year's videos. The videos can be between 2-5 minutes long. Can include narration if necessary (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 sinage for the team project. You will also need to prepare a demo 'script' and reherse the script in the Lab, a week prior to the final demo day.

Demo Day

The final demo day will take place in the CSE atrium tentatively on Thursday, December 13th. And 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, Facebook, Oculus, Valve, and more!

Staff will evaluate final demos on Novelty, Difficulty, Production Value, 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!