One clear view of what’s next.
Discovery is taking shape. The website foundation is being specified. Follow the current work, what we’ve captured, and what still needs a decision.
Two workstreams, moving together.
The foundations for delivery tracking are in place.
- Five discovery sources reconciled, including Jasmine’s UX meeting and the planned US shipping list.
- Seventeen Confluence records refreshed; requirements expanded to 44 entries and current checkpoint coverage recalculated.
- Affected Jira stories and sprint goal updated; dashboard stays Done, nine discovery stories In Progress, ten software stories To Do.
- Project progress dashboard completed and confirmed by Johnathan; live at lumistproject.info.
The project progress dashboard is complete. The remaining discovery and foundation deliverables continue through their Jira workflows.
No entire milestone is recorded as accepted. Future milestone progress is unmeasured.
What will move the project forward.
Assets and website decisions
Get actual logo/photo/fact files through Jasmine, Gigi and David. Resolve Contact/menu and copy-tone revisions, archive/languages and required verification/consent fields; return draft review.
Brand discovery · SCRUM-11 ↗Real product and policy inputs
Supply the four reported 2024 item records and full-case prices, stock units/source and VIC admin rules. Confirm the paid House reservation policy and implementation scope.
Product discovery · SCRUM-12 ↗Compliance and provider decisions
Map the ten planned states to verified permissions and restrictions. Obtain counsel/finance/logistics contacts, licensing quote, age/tax/fulfillment rules and merchant/provider decisions.
Compliance inputs · SCRUM-17 ↗The work behind each milestone.
How the percentages are calculated
Delivery completion = Jira Done deliverables ÷ tracked deliverables × 100. Each deliverable counts once. SCRUM-8 contributes one complete deliverable: 1/10 for 1A (10%) and 1/20 across the current 1A + 1C scope (5%). This is a count of finished deliverables, not an estimate of hours or the whole future project.
Documentation coverage = captured checkpoints ÷ applicable checkpoints × 100. Partial checkpoints remain visible but receive no invented fractional credit. Missing checkpoints receive no credit. Learning-phase checkpoints are excluded from the denominator. Counts are equal checkpoint counts, not equal-effort estimates.
A checkpoint shows 100% when its documentation is Captured, 0% when Missing, and “Partial” when no reliable fraction is supplied. Milestone bars roll up their checkpoints, not averages of rounded item percentages. Jira Done counts and formal acceptance remain separate. A documented requirement does not mean implemented software.
The full project roadmap.
Future milestone deliverables are known scope; progress percentages remain unmeasured until Jira work and evidence checkpoints are defined. No calendar delivery date, payment or formal acceptance is inferred from the proposal. Sprint end: October 16, 2026; this is a planning date, not an acceptance deadline.
Requirements, kept traceable.
Sources, freshness and evidence limits
Jira supplies workflow status, owners and story requirements. Confluence supplies documented input checkpoints and remaining asks. The local master memory supplies the 16-milestone proposal map. This page is a published snapshot, refreshed as project work is recorded; it does not continuously poll Jira.
1A progress notes · 1C progress notes · Source register · Decisions & open questions
All 22 milestone epic/story records were retrieved; the 20 child stories are the dashboard’s delivery scope. Two Jira sample tasks are excluded. Status, summary, description, parent, assignee, labels, priority and update date were checked. Input-review contacts are documented separately from actual Jira assignees, which remain unassigned. No assignee capacity, software deployment, executed test, reviewed milestone criteria, contract, payment or acceptance record is inferred.
Search indexing is discouraged through noindex / nofollow directives. Linked Jira and Confluence records retain their own access requirements.