Simulated project by Vimlesh Sonawane, Project Manager. Not a production system, no real customer data. Timeline in the project: 6 weeks, 3 two-week sprints. Target in the simulation: onboarding from 21 days to 10 days — a target, not a real company result. Story points here are for demo illustration, not a real team's velocity.
1. Sprint board — try it
Pick a sprint, read its goal, click Move forward on a story to move it To Do → In Progress → In Review → Done. Points and remaining work change only when a story reaches Done. Use Reset sprint to run it again.
Remaining work
Points left as stories move to Done. Start = sprint total. Each Done story drops the line.
Product Backlog
From docs/backlog.md, plus any stories you add below. Future backlog, not in Sprint 1–3: additional import formats, automated reminders, deeper reporting.
Add your own story
Try backlog refinement: add a story for a stakeholder, reporting, or process need. It is added to the backlog in this browser session only, it is not saved to the repo.
2. Risks, blockers, and roadmap
Risks and blockers — from docs/raid-log.md
Click a risk to see its mitigation. These are the trade-offs a hiring manager can ask about in an interview.
Sprint 1 — Weeks 1–2 Discovery and setup Milestone: Charter and backlog reviewed; pilot profiles selected.
Sprint 2 — Weeks 3–4 Core build Milestone: Core flow walkthrough; two usability issues logged for Sprint 3.
Sprint 3 — Weeks 5–6 Pilot, training, go-live Milestone: Go-live readiness review against charter success criteria.
What this shows: backlog refinement, sprint planning with a goal and a point total, a Jira-style board, tracking by remaining work, risk and dependency management, and the trade-off when a story is not finished — it stays out of Done and out of the sprint's completed points. Sprint review and retrospective notes are in docs/sprint-plans.md and docs/retrospective.md.