Repository navigation
Sprint 1
September 30 through October 13, 2026. The dates cover the two weeks following week 5 planning. Canvas names the October 13 week 7 status update "End-of-Sprint-1," so this plan uses Sprint 1. Matthew Feroz is the assigned owner because the public repository currently lists no other collaborators. Adjust dates/ownership if the course team specifies otherwise.
Make the public evaluation workflow understandable and verify its existing behavior from first setup through a saved, deliberately published report. Resolve targeted defects found during validation; retain reproducibility and recovery evidence.
The week 5 prototypes and architecture explanation are planning inputs. This sprint does not promise to implement onboarding or live monitoring from scratch, since both already exist in the public source.
| Issue | Work | Owner | Estimate |
|---|---|---|---|
| #9 | Validate the first evaluation workflow and resolve onboarding blockers | @MatthewFeroz | 8 h |
| #10 | Verify reconnect and cancellation behavior without duplicate evaluation runs | @MatthewFeroz | 8 h |
| #11 | Validate private reports, published revisions, and revoked-link access | @MatthewFeroz | 6 h |
| #12 | Document reproducible evaluation evidence and a public release checklist | @MatthewFeroz | 6 h |
Each issue includes expected work, observable completion criteria, evidence requirements, and scope exclusions. All four are open and begin in Todo. The planned work has not been claimed complete.
Milestone · Sprint 1 board · Project
The commitment is 28 estimated hours. Reserve another 4 hours for defects and review, for a planning capacity of 32 hours across two weeks. Estimates are planning judgments, not measured execution times. Keep one issue actively in progress at a time.
- Week 1: complete the first-run walkthrough and reconnect/cancellation validation. Record findings as they occur.
- Week 2: complete report access/publication validation, consolidate reproducibility/release evidence, and review any targeted fixes.
- Issue #12 consumes evidence from #9 through #11. Do not let documentation work block their independent validation.
Use Oracle and synthetic reports for automation. A real model run needs a separately approved spending budget. Automatic cloud provisioning, a new scheduler, full raw-log streaming, large paid studies, a package release, and application deployment are outside this sprint. If work exceeds capacity, reduce the commitment explicitly rather than treating incomplete criteria as done.
A separate public Heval project was created. The unrelated private Kanban Idea Board and its views were left untouched. The default Heval table remains available; Sprint 1 is its own saved board view.
The Sprint 1 view filter is:
repo:MatthewFeroz/heval milestone:"Sprint 1: evaluation workflow validation"
All four milestone issues were imported and their Status is Todo. Move an issue to In Progress when work begins and Done only when its completion criteria and evidence pass. Future sprints should receive their own milestone and saved view; do not overwrite this one.
Enabled and verified on September 30, 2026. The native Auto-add to project workflow targets MatthewFeroz/heval with filter is:issue is:open. It is independent of the sprint milestone, so future sprint issues can enter the project while each saved board limits its own sprint.
Verification removed issue #12's project item, then updated the issue. GitHub automatically re-imported it with a new project item ID and Todo status, without a manual item-add operation. All four sprint issues remain in the project and milestone.