DEV Community

Aisalkyn Aidarova
Aisalkyn Aidarova

Posted on

full agile by claude

Here's the full Agile roadmap. Navigate using the tabs at the top — each view is designed for a different stakeholder:

The five tabs give you:

  • Overview — epic cards at a glance, each clickable to generate deeper breakdowns
  • Epics & features — all 7 epics expandable, 28 features with priority ratings and descriptions
  • User stories — filterable by epic, each with full acceptance criteria in testable format
  • Sprints — all 9 sprints expandable with tasks, story points per task, tags, dependencies, and a checkable testing checklist
  • Timeline — visual Gantt-style bar chart showing cadence and point distribution across 18 weeks

A few architectural decisions baked into the prioritization worth calling out:

Sprint 1 is deliberately a zero-feature sprint. Nothing ships to users — only foundation work. RLS policies, CI/CD, schema migrations, and fixing the broken UI states must land before any feature development begins, or you'll be retrofitting security onto live user data.

Payments are Sprint 7 (not Sprint 1) by design. You need working auth, lecture delivery, and an admin panel before charging students. Trying to wire Stripe before those are stable creates refund complexity and support burden.

The testing checklist for each sprint is written as executable statements, not vague phrases — each item should map to an actual test case or manual QA step in your project management tool.

When you're ready to move forward, say the word and I can generate the actual code for any specific sprint, starting with Sprint 1's Supabase schema and RLS policies.

Top comments (0)