Team Project - Deliverable 2
Due: November 16, 10 pm
The goals of this assignment are as follows:
- Get you to build the first presentable version of your prototype
(i.e. Demonstrate working software)
- Require you to prioritize tasks and make product decisions
(the deadline is fixed, you get to choose what to build by the deadline)
- Encourage you to reflect on your team (and individual) work habits
The following files should be submitted to your team repo, in a folder called deliverables (you will need to create this folder):
Summarize your second planning meeting.
Summarize your second review meeting.
These files should follow a similar style to what you had for iteration 1 (but feel free to make improvements, if you want).
- Please keep these documents informative, but concise
(max 3 minutes read, per document)
- Focus on the highlights
- Link to existing artifacts (e.g. issues and pull-requests)
- Edit and clean-up the documents while you’re working on your project
In addition to the files above, each team is required to submit a video with a demo of their prototype.
Guidelines for the demo video
Maximum 3 minutes!
Roughly follows this format:
- Introduction (30-45 seconds)
- Give the audience some context
- Tell the audience what they are about to watch
- Demonstrate your product
- Present it from the user’s perspective, and guide the audience through the most common user flow.
- Final discussion (30-45 seconds)
- Summarize what we saw
- Briefly discuss what you’re planning to do next
In terms of the technicalities:
- Feel free to use whichever screen capture tool you want.
For example: ScreenCast-o-Matic, LICEcap, Reflector2 or even by taking a video of the screen with your phone’s camera.
- We will be evaluating you on the content of the video, not on production quality.
Just make sure we can see the demo and understand what you are saying.
- Feel free to share the video with the TA in whichever format works best for all of you.
For example: Private video on YouTube or some other video hosting service, via DropBox or some other file-sharing service, as a file in your repo (if it’s not too big), etc.
- Make a test video early on, and make sure you get all technical difficulties out of the way
- When giving a demo, speak slower than usual - The audience needs to process what you are saying, as well as everything that is happening on the screen.
- Before you record the video:
- Write a script
- Work out the timing (i.e. read the script at a slow pace, and make sure it is not too long or too short)
Here is what we expect from each of your deliverables:
- Clearly demonstrates the existing software
- Someone who knows nothing about your project should understand the basic user-experience, based on your video.
- Provides a good idea of what the product is (even if it isn’t fully implemented)
- Provides a good idea of the value to the user
- Includes all fields from the template.
- Process is described in detail, according to the instructions in the template.
- Product goals, tasks and artifacts are described clearly and concretely.
That is, at the end of the iteration, it should be easy to determine whether a goal was met / a task was completed / an artifact was delivered.
- Includes all fields from the template.
- Clearly describes the difference between the plan and what actually happened.
- When reviewing your work, refer and provide links to artifacts.
- Insightful reflection - Identify good/bad decisions and offer concrete improvements.
In addition to that, we expect all deliverables to have a high-quality presentation.
- Clear writing.
- No typos and/or grammar mistakes.
- No placeholders and/or instructions from the template.
- Make good use of images, videos, links and/or any other aid that makes your deliverable easier to read and understand.
Your TA’s will use the following rubrics to evaluate your deliverables:
We will compute your mark by converting each component to percentage (according to the table below) and taking the weighted average.
Good, meeting all expectations
OK, but some expectations were not fully met
Missing (or extremely low quality) work
IMPORTANT: We expect all team members to contribute to the project.
Students who do not participate are risking not earning a mark for this deliverable (keep in mind that, throughout the project, we will look at the graphs of your repo to determine individual participation).