Tablet PC Capstone, Winter 2006

Grading Guidelines

The premise of the course is that a new software company has been formed to create consumer and educational software for the Tablet PC platform. The company aims to develop a series of prototypes to evaluate the feasibility of a number of project ideas. These prototypes are to be presented at a company meeting in mid-March 2006. The project ideas have been set by management, and developers will be assigned to project teams based on individual preferences and relevant constraints. (Some background notes on the general context are available here.)

In addition to deciding which software projects to pursue further, management will also need to conduct performance reviews of all project participants. These will be individual reviews (but influenced strongly by team performance), done on a 0-4 scale.

The goal of each project is to produce a compelling Tablet PC application. Hence, the quality of the application and the degree to which it demonstrates the novelty and advantages of the Tablet PC platform will be very important in the project evaluation. Beyond that, there are many other aspects of projects that could be considered in the evaluation.

To allow teams to concentrate on those aspects of development that are important to the team members (e.g., to match their own professional development goals), management has decided to give each team the flexibility to specify (with some constraints) the criteria that they would like to be evaluated on.

By 5pm on Friday, January 13 (the end of week 2), each team must submit - by email to the course staff - a breakdown of the weights they would like to place on each of the criteria listed in the table below. The weights assigned to all items must add up to exactly 100%. Items A, B, and C have initial weights (which cannot be reduced) totaling 60%, so there are 40% remaining to be assigned. The constraint is that at most 3 items from categories D-N may be assigned non-zero weights. Note: It is not necessary to assign all remaining percentage points to items in the D-N range; additional weight may be placed on one or more of the items A, B, or C.

 WeightEvaluation Criteria
B10%Use of Agile Process and VSTS tools
C10%Meeting deadlines and presentations at checkpoints
D Code Quality
E Design Methodology
F Project Architecture
G Testing Methodology and Test Execution
H Engineering Quality
I User Interface
J Release Quality
K Development Process
L User and Technical Documentation
M Technological Innovation
N Business Case for the Application

Weights can differ between teams, but within each team the same weights will be applied to the evaluation of all team members. Hence, teams must agree internally on their preferred set of weights. If for some reason a team cannot agree and announce their decision by the stated deadline, the default weights to be applied will be A: 80%, B: 10%, and C: 10%.