The goal of this assignment is to have each team provide an update to the work breakdown schedule developed previously. For the work breakdown document, each team was required to write a detailed list of the activities that need to be performed to complete their video game project, estimate the time required for each, and assign people to each of these tasks. Now that each team has some experience from working on the project, it is possible to identify those tasks that have already been completed, as well as provide an updated estimate of how long the remaining tasks will take.
A common pitfall in any computer related project is that the work takes far longer to complete than one initially estimates. Once work begins, a more realistic picture emerges of the challenges, and time required to complete the project.
It is also frequently the case that, once this more realistic picture of time requirements emerges, teams decide to reduce the scope of their project so they can complete it on time. This is fine, and an expected outcome of a time estimation activity. If you decide to reduce the scope of your project, please describe the reduction in scope on your progress report. In general, a smaller game that is perfectly executed will get a better grade than a more ambitious project that fails to complete on time. Note that there are limits to this. Reducing scope to the point that you have a trivial game will not result in a high score.
For details on the content of the computer game progress report, see the template page, and for details on grading of the progress report see the evaluation page.