Workshop Activities
Nine activities from the practice library are run as workshops in class: four in fall, three in winter, and two in spring. Each session spends its first half on the activity and its second half redoing it with an AI agent; both halves go in the same submission. They are graded, but only on whether you did them: there is no quality bar, no bands, and no rubric. Submit the output and you get the points.
Each one makes several later rubric criteria easier; each activity’s Feeds line names which. The more than a hundred other activities in the library are optional.
Fall (4 items, 2%)
Section titled “Fall (4 items, 2%)”| Activity | Week | What it makes easier |
|---|---|---|
| Team Formation Strategies Assessment | 1 | The Team Charter conflict and inclusion section, written the week you meet; the defense role question |
| User Story Mapping | 2 | docs/requirements.md at every repo checkpoint; the winter Definition of Shipped |
| Describe your Architecture | 3 | docs/design.md, your RFC, and the defense technical-depth question |
| Audit Your Safety Net | 3 | Four criteria across the checkpoints, the RFC, and the defense |
Week 3 is one session with two outputs: the architecture and the safety net that guards it. Both land before the RFC draft at the end of week 4. Map Your One-Way Doors is not a workshop but picks your RFC topic; do it in week 3 on your own, it takes an hour.
Winter (3 items, 1%)
Section titled “Winter (3 items, 1%)”| Activity | Week | What it makes easier |
|---|---|---|
| Dependency Mapping or Critical Path Analysis | 1 | The Definition of Shipped, due two weeks later: the external clocks named and started |
| Team Dysfunctions Assessment | 2 | The midterm peer evaluation in week 5: naming a problem before the survey does; the defense role question later |
| Test Plan | 3 | The week-5 repo checkpoint: the tests in CI that must exist before real users arrive at the release candidate |
Spring (2 items, 1%)
Section titled “Spring (2 items, 1%)”| Activity | Week | What it makes easier |
|---|---|---|
| Team Health Assessment | 2 | The spring charter refresh and the midterm peer evaluation; the Project Retrospective team-dynamics criterion later |
| Identify Success Metrics | 3 | Release and Metrics and the Landing Page: the number that proves it worked, chosen while there is time to instrument it |
The spring assessment closes with the charter refresh: update docs/charter.md with what it surfaced (roles for the final term, the decision process, anything the winter postmortem changed) and commit it. Spring has no repo checkpoint to carry the refresh, so this workshop is where it lives.
The teamwork slot rotates through three different instruments so it tells you something new each term rather than asking you to retake the same survey.
Grading
Section titled “Grading”One Canvas column per term, scored as complete/incomplete per item: 4 checkboxes in fall, 3 in winter, 2 in spring. The spring week-6 Resume Building session is a workshop too, but its output is graded inside the Career and Individual Retrospective, not here. Submit the activity’s output, whatever the activity says a good output is. A grader spends seconds per item confirming something real was submitted.
There is no partial credit within an item and no quality judgment. An output that is obviously not the activity (a blank file, an unrelated document) does not count, but a genuine attempt always does.
Late work: these are workshop activities tied to a week, so the standard late policy applies with one relaxation: a workshop item submitted any time before the end of the term still earns its points. Doing it late costs you the benefit, not the mark.
Missed the workshop session? The activity pages are public and self-contained. Read the page, do the activity, submit it.