VeloxIQ One · Enterprise Stores
Daily Schedule — separate page, shared data
Checking shared database…
10–30 November 2026 · Hansika + Akash + Navakesh

Daily Schedule

Daily time slots and task statuses for Hansika, Akash and Navakesh. Changes synchronize with the Sprint & Scrum board across devices.

Progress by owner

Task statuses, blockers and sprint records save to shared Cloudflare D1 when connected. Browser changes are kept safely until they sync.

Checking shared database…

21-Day Calendar

10–30 November 2026 at a glance. Click a working day to open its hour-by-hour plan below. Sundays are off; 10–11 Nov have no recorded progress.

Sprint colours: 01 blue · 02 gold · 03 green · Release red

Day & Time Schedule

Every working day hour by hour: Mon–Fri 10:00–19:00, Sat 11:00–19:00, lunch 13:00–14:00, Sundays off. Statuses here and on the board are the same.

3 work blocks + self-test hour per developer per day

Weekly Scrum Task Board

Filter by assignee and move cards through the workflow. Each card has a date, time slot, requirement reference and a clear acceptance condition.

To Do → In Progress → In Review → Blocked → Done

Workflow Coverage

Every workflow in requirement §9 and the tasks that deliver it. WF-27 is built as a disabled action until the owner signs off.

27 of 27 workflows planned
IDWorkflowOwnersDatesTasksProgress

Daily Scrum (stand-up)

Record what was completed, what is planned today, and blockers. A 10–15 minute check-in at the start of the first block.

One update per developer per day

Scrum routine for this sprint

Saved stand-ups in this sprint

No saved stand-ups yet.

Weekly Sprint Ceremonies

Planning, review/demo and retrospective notes for the selected sprint.

Rules & Weekly Sprint Alignment

Definition of Done

  • Acceptance condition on the card met, with evidence recorded against the workflow ID in the Git issue tracker.
  • Code reviewed in a PR by a teammate and merged to develop; staging deploy checked.
  • The developer has self-tested it (no testers): authorised completion, returned correction, denied scope, missing settings, stale version, duplicate retry, failed handoff.
  • Incomplete work stays open and carries over; never mark Done from the plan alone.

Working hours and capacity

  • Mon–Fri 10:00–19:00, Sat 11:00–19:00 (end time is an assumption to confirm), lunch 13:00–14:00, Sundays off.
  • Each day: three work blocks plus 18:00–19:00 self-test, commit and PR. Stand-up in the first 15 minutes.
  • Limit 141 h per developer for 10–30 Nov; 16 h of it was 10–11 Nov. From 12 Nov each developer has 109 h of tasks + 16 h self-test.
  • All 27 workflows fit only because each task is tightly estimated — the 14 Nov review (GR1) checks the pace; if behind, the team lead decides what moves.

Architecture, hosting and Git

  • Shared PostgreSQL database for Core, Inventory, PMS, HRMS and P&M with module-owned schemas; Stores writes only its own tables and reads Core through controlled services; no Core configuration editing in Stores.
  • React + Vite frontend (Cloudflare Pages), Node.js + Express API on the Hostinger VPS behind Cloudflare; nightly encrypted backups to Cloudflare R2.
  • Git: main/develop protected, feature branches, PR + one review, tagged releases, API contracts in Git; secrets never in Git.
  • PMS, HRMS and P&M stay on clearly labelled mocks for 30 Nov; a mock is never shown as verified money or identity.

Gates

  • G0 · 14 Nov — foundation ready (VPS, DB, backups with tested restore, CI/CD, sign-in).
  • GR1 · 14 Nov — re-estimate after Sprint 01 (Mr. Akash + team lead).
  • G1 · 19 Nov — Core-routed approvals, MR and PR working end to end.
  • G2 · 21 Nov — PR → RFQ → PO → GRN chain working.
  • G3 · 28 Nov — all workflows tested, every screen on the API, freeze.
  • G4 · 30 Nov — production release v1.0.0.

Open decisions (from the requirement)

  • Quarantine release authority (§4.7) — not granted to Inventory Head until assigned.
  • Damaged-stock reuse release permission (§4.9).
  • PO reopening authority (§5 4.7, WF-27) — action stays disabled.
  • Final accounting valuation method for lending (§6 5.5).
  • Saturday end time; Core contact for database grants and approval configurations.

How this relates to the existing schedule

  • Days, hours, team, hosting, Git, testing rules and the 30 Nov release are taken from the existing schedule (v3).
  • Scope now follows the v4 requirement: four privileges, sections 4–8 and workflows WF-01–WF-27.
  • Progress, blocked reasons and stand-ups are stored in this browser. Export progress file gives a copy that can be imported on another computer.
  • IDs like STR-W2-BE1-03 are planning IDs for this Stores schedule.
Status saved in this browser