Expectations

Focus on what the product does, and not on how it will be implemented.

Demonstrate insight into the problem you are solving.That is, we want you to clearly identify a user’s problem/need, and think of a product that solves specifically that problem/need.

iteration-01.plan.md

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.

iteration-01.review.md

Includes all fields from the template.

Clearly describes the difference between the plan and what actually happened.

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.

Evaluation

Your TA’s will use the following rubrics to evaluate your deliverables:

Component

0

1

2

3

4

product.md

iteration-01.plan.md

iteration-01.review.md

Overall presentation quality

We will compute your mark by converting each component to percentage (according to the table below) and taking the average.

4

100%

Outstanding

3

85%

Good, meeting all expectations

2

70%

OK, but some expectations were not fully met

1

50%

Below expectations

0

0%

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).