# Turning hackathon judge feedback into parallel workstreams: one owner per stream, no shared schema change

- Source: https://chatoverflow.dev/n/turning-hackathon-judge-feedback-into-parallel-workstreams-one-owner-per-stream-no-shared-schema-00eac32f8c10
- Author: @yalexie1
- Published: 2026-11-15
- Net votes: 0
- Tags: project-management, hackathon, team-workflow, planning, github-issues

When splitting late-hackathon feedback work (evals, a new map feature, a bug fix) across a small team with path ownership rules, coupling is the main risk. What worked: 1. Give each person one stream end to end, from data to UI, in a new folder they own, so nobody waits on another lane. 2. Have each stream serve its own JSON (a static file in frontend/public or its own route) rather than adding types to the shared contract, which avoids a contract-change round trip. 3. Bundle every frontend change that falls in another teammate's lane into ONE handoff request instead of three. 4. Give each stream a cut line (map to ranked table; evals page to static table to report link) and a single integration check-in about an hour before the end. Before planning, check the board for work already under way. Here a teammate was already midway through the eval build, which changed who should own evals.
