CHIP 10.5: Scoring and Rubrics

Point values and dates are subject to change before each iteration opens. Gradescope is the authority for due dates and for any value that differs from this page.

This page summarizes how the final project is scored and where each deliverable is submitted. The full rubrics live on Overview and Grading in the instructions β€” read that page before each iteration. For the timeline and links, see the project overview; for what AI tools you may use, see AI Tools and Use.

Table of contents

  1. Overview
    1. Inside the big deliverables
  2. Gradescope assignments
  3. Team score scaling
  4. Late work and extensions
  5. P/NP students
  6. Regrades

Overview

CHIP 10.5 is worth 20% of your course grade and is scored out of 150 points: three iterations of 50 points each. In every iteration, 35 points are a team score (deliverables A, B, and C β€” everyone on the team earns the same score) and 15 points are individual (deliverable D, earned solely by your own submission).

Deliverable Who Iteration 1 Iteration 2 Iteration 3
A. Planning meeting Team 4 4 4
B. Code submission Team 1 1 1
C. Video + Links Submission Team 30 30 30
D. Retrospective Individual 15 15 15
Team total Β  35 35 35
Individual total Β  15 15 15
Total Β  50 50 50

Inside the big deliverables

Deliverable C carries the bulk of the team grade. Its weight shifts from set tasks in Iterations 1 and 2 to your own features in Iteration 3:

Part of C Iteration 1 Iteration 2 Iteration 3
Video (2–4 min, then 2–5 min; deployed app, URL visible) 2 2 2
Feature work (Iteration 3: two features of your choosing + a technical checklist) 12 12 8 + 6
Team work (reviewed PRs, issues planned vs. delivered, passing CI) 6 6 3
Testing (coverage and plan, accessibility scenarios, test cases) 8 8 3
Generative AI (how the team used it, chats linked) 2 2 8
Bonus (Rails feature not covered in class; an additional service) β€” β€” up to 8 extra

Deliverable D is the same every iteration: retro board 3, Teammates surveys 2 (peer review 1, self-assessment 1, checked against Teammates), your GitHub contributions 8 (pull requests you authored 3, code reviews you gave 3, issues 2), and your AI chats 2.

Coverage targets (line coverage of app/, reported by SimpleCov): full credit at 50% after Iteration 1 and 75% after Iterations 2 and 3, with extra credit from 80% in Iterations 2 and 3. The starter app begins at about 19%.

Gradescope assignments

Each deliverable is its own Gradescope assignment. Team assignments are submitted once per team (add every teammate to the submission); the retrospective is submitted by each person. All deadlines are 11:59 PM PT. Every iteration totals 50 points.

Iteration Deliverable Points Who Due Late until Gradescope
1 A. Planning Meeting 4 Team Wed Nov 4 Sat Nov 7 8462256
1 B. Code Submission 1 Team Fri Nov 13 Mon Nov 16 8462257
1 C. Video + Links Submission 30 Team Fri Nov 13 Mon Nov 16 8462252
1 D. Retrospective 15 Individual Fri Nov 13 Mon Nov 16 8462260
2 A. Planning Meeting 4 Team Fri Nov 13 Mon Nov 16 8462258
2 B. Code Submission 1 Team Fri Nov 20 Mon Nov 23 8462254
2 C. Video + Links Submission 30 Team Fri Nov 20 Mon Nov 23 8462255
2 D. Retrospective 15 Individual Fri Nov 20 Mon Nov 23 8462259
3 A. Planning Meeting 4 Team Tue Nov 24 Sun Nov 29 8964867
3 B. Code Submission 1 Team Fri Dec 4 Sun Dec 6 8964868
3 C. Video + Links Submission 30 Team Fri Dec 4 Sun Dec 6 8964869
3 D. Retrospective 15 Individual Fri Dec 4 Sun Dec 6 8964871

The Teammates peer review and self-assessment surveys are at teammatesv4.appspot.com and open near the end of each iteration; completing them is part of deliverable D.

Team score scaling

Beyond the rubrics, staff adjust the team portion of your grade, up or down, based on the peer evaluations, the quality of your stories, and how the team worked together in pull requests and issues, when a team member’s contribution is clearly above or below an equal share. It is therefore possible to earn more than 100% on an iteration (do not expect more than about 115%), and possible to earn substantially less than your teammates if they report that you were absent or not contributing. The goal is a healthy development process, not just a finished app.

Late work and extensions

  • Every assignment accepts late submissions until the hard deadline shown on Gradescope β€” the β€œlate until” date above, two or three days after the due date β€” with no penalty.
  • There are no further extensions and slip days do not apply to the project. Iterations are scheduled team events, like real sprint boundaries.
  • If a teammate has an emergency, the rest of the team should still submit on time; tell us on Ed (privately) and we will handle the individual case.

P/NP students

You need 50% or more on the project category, including your peer evaluation scores, to pass. This is straightforward as long as your teammates do not report that you were absent and not contributing.

Regrades

Regrade requests for team deliverables should come from one team member on behalf of the team, through Gradescope, within one week of scores being released. Please point at the specific commit, pull request, or timestamp in the video that you believe was missed.


Back to Top

Accessibility Nondiscrimination

Copyright Β©2026, Regents of the University of California and respective authors.

This site is built following the Berkeley Class Site template, which is generously based on the Just the Class, and Just the Docs templates.

View all course offerings