Sprints
Research is rarely a straight line from hypothesis to discovery. It is a cycle of trial, error, debugging, and refinement. To mirror the workflow of professional research software engineers and agile labs, this course replaces the traditional “Midterm Exam” with Sprint Cycles. A sprint is a focused period during which your team aims to achieve a specific set of technical and scientific goals. At the end of each sprint, you do not just turn in homework; you deliver a working product increment (i.e., artifact) and a Sprint Report.
Schedule
We will follow the tentative sprint schedule shown below.
| Sprint | Week(s) | Theme | Goal |
|---|---|---|---|
| 1 | 5 | Charter | Form teams. Set up the GitHub repo structure. |
| 2 | 6 – 8 | Prototype | Build the pipeline and run it on a toy dataset. |
| Spring Break | |||
| 3 | 9 – 11 | Production | Run the full pipeline on the real dataset. Handle errors and scaling issues. |
| 4 | 12 – 14 | Deliverable | Analyze the results and visualize findings. |
Last updated on