Sprint 01
Table of Contents
This page documents a sprint (Sprint 01) of ORE Studio v0. It captures the sprint's mission, current status, and the stories that compose it. For the surrounding context — version goals, sprint order, and product identity — see Version 0.
Mission
Bootstrap project infrastructure and bring currencies end-to-end through the stack.
Status
| Field | Value |
|---|---|
| State | DONE |
| Parent version | Version 0 |
| Previous | — |
| Start | 2024-06-15 |
| End (expected) | 2025-02-02 |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Sprint 02 |
| Release Notes | Release notes |
| Last touched | 2024-07-28 |
Achievements
- Project bootstrapped: build, packaging, and CI in place.
- Qt UI scaffold established as the desktop surface.
- Currencies working end-to-end as the first live domain feature.
- Documentation infrastructure laid down.
Stories
For the definitions of the themes see Themes.
Infrastructure
| Story | State | Start | End | Description |
|---|---|---|---|---|
| Project bootstrap | DONE | 2024-07-01 | diffuse story covering repo, build, CI, and packaging. The plumbing every later story stands on. | |
| Build quality | DONE | 2024-07-28 | nightly memcheck, Valgrind stabilisation, C++ standard bump, vcpkg warning hygiene. |
Product
| Story | State | Start | End | Description |
|---|---|---|---|---|
| Qt UI scaffold | DONE | 2024-07-28 | initial Qt application: hello world, splash, refactor toward a usable layout, icon set. | |
| Currencies end-to-end | DONE | 2024-07-28 | tight story: bring currency data through XML, JSON, the database, and the Qt UI as the pathfinder data type. |
Documentation
| Story | State | Start | End | Description |
|---|---|---|---|---|
| Documentation infrastructure | DONE | 2024-07-28 | project site, Doxygen, README, seed domain notes. |
Agile
| Story | State | Start | End | Description |
|---|---|---|---|---|
| Sprint 01 housekeeping | DONE | 2024-07-28 | sprint-level work that doesn't fit a product story: sprint instrumentation, dev setup, community channels. |
Charts
Charts generated via sprint_charts cmake target.
PRs & Commits per Day
Dual-axis bar chart. PRs (left axis) and commits (right axis) per day. A high commits-to-PR ratio may indicate scope creep.
Daily Line Churn
Lines added (green) and deleted (red) per day. Building work produces mostly additions; refactoring produces a mix. Days with no churn may indicate blockers.
Cumulative Stories Done
Line chart tracking stories marked DONE during the sprint. Steady upward slope is healthy; plateauing signals a stall.
Retrospective
Filled in retrospect, from the v0 record:
- What worked
- tight time-boxing (~80 hours total), small per-entry work units (median ~30 minutes), explicit acceptance via "Result:" sections.
- What did not
- the v0 model conflated "story" with "task"; the actual user-visible outcomes (e.g. "currencies end-to-end") were never surfaced as units, so the sprint mission had to do double duty as both intent and acceptance.
- Carry forward to v2
- the discipline of one PR per task and the habit of recording outcomes inline are preserved; the missing story layer is what the v2 information architecture restores.