Grades are assessed independently each term, according to the work done that term. Since all team members are responsible for the progress of the project, the grade reflects both individual contributions and overall team results. The individual grade is determined from a combination of technical and non-technical factors, equally weighted. The team grade is determined from an evaluation of the team's overall progress towards established goals, as well as the success at meeting the project partner's needs.

Technical contributions are apparent in the various artifacts produced by the team, from requirements documents to code to test cases. Different students contribute to different artifacts; for example, at one point one student might be focusing primarily on requirements analysis, while another is prototyping key components. The team maintains an equitable distribution of tasks to ensure sufficient opportunities for technical contributions. Since the artifacts are produced collaboratively, each student documents his/her particular contributions in weekly reports, individual design notebooks, and annotations in revision control logs. In addition, each student critiques both his/her own participation and that of all team members (peer evaluations). Grades are determined for the artifacts, with credit given to the responsible students according to level of contribution.

Non-technical contributions include written reports (design documents, user manuals), oral presentations (design reviews, deployment summaries), project partner interactions (requirements elicitation, support), and effective teamwork (meeting participation, fulfilling team roles). Each team member is expected to contribute in each of these four categories.