Scrum Sprint Planner using Django

Student teams run their final-year projects on chat messages and hope — then discover in the last month that half the work was never started. Professional teams avoid this with Scrum: fixed-length sprints, a visible board, and a burndown chart that makes slippage impossible to ignore. This project is a full Scrum sprint planner built with Django: story and bug tracking on a kanban board with WIP limits, sprint planning with story-point commitment, burndown charts plotted against the ideal line, velocity history across sprints, in-app planning poker, and auto-generated standup summaries. The demo walks through a realistic sprint — Sprint 7 of a campus portal build — with the board, the burndown (21 of 34 points done, ahead of the ideal line) and the sprint/team management views exactly as the Django app renders them.

1. The Product Owner creates epics and stories with acceptance criteria; the team estimates them in-app with planning poker.
2. At sprint planning, the team pulls stories into the sprint up to the velocity-guided commitment; the burndown's ideal line is drawn from committed points over sprint days.
3. Developers move cards across the board; WIP limits on In Progress are enforced (the demo caps 8 cards for 4 developers).
4. A nightly job snapshots remaining points, so the burndown reflects daily progress; scope changes are logged in the sprint-change audit.
5. Velocity is recomputed from completed sprints and shown as the commitment guide for the next planning session.
6. Each morning the standup summary aggregates yesterday's card movements, open blockers and today's focus into one digest.

Tech stack:

• Python 3.10, Django 4.2, Django REST Framework (board APIs)
• PostgreSQL (projects, sprints, stories, estimates); Redis (real-time board updates via channels)
• HTML/CSS/JS frontend (kanban board, SVG burndown and velocity charts)
• Single-file HTML/CSS/JS demo walkthrough mirroring the Django screens
• pytest suite for sprint math (burndown, velocity, WIP enforcement)

• [Kanban sprint board] Five columns (Backlog, To-Do, In Progress, In Review, Done) with drag-and-drop cards, story points, assignees and WIP limits.
• [Burndown charts] Remaining work plotted daily against the ideal line, with scope-change annotations when stories are added mid-sprint.
• [Velocity tracking] Completed points per sprint charted across the last six sprints, with the running average used for commitment guidance.
• [Sprint planning] Sprint creation with date ranges, story-point commitment, goal statements and retro-action carryover.
• [Planning poker] In-app Fibonacci estimation with simultaneous reveal; averaged estimates write back to the story.
• [Standup summaries] Auto-generated daily digest: what moved, current blockers, today's focus per developer.
• [Team & capacity view] Per-developer workload against declared capacity (the demo models a teammate at 60% during exams).
• [Role-based access] Scrum Master, Product Owner and Developer roles with appropriate permissions on sprints and stories.

• Complete Django source code (models, views, DRF APIs, board frontend, chart rendering)
• pytest test suite for sprint calculations and permissions
• Project report PDF (agile background, data model, sprint algorithms, UI design, test results)
• PPT presentation for final review
• Viva Q&A preparation document (Scrum framework, Django MVT, DRF, WebSockets, estimation theory)
• Setup guide (environment, migrations, seed data, running the demo)

• Single-project demo seed data; multi-project portfolio rollups are out of scope.
• Real-time board updates need Redis — without it the board falls back to polling refresh.
• Burndown math assumes story points are the unit of work; hour-based tracking is not supported.
• The standup summary is a rules-based aggregation, not an LLM — it reports card movements, it does not infer blockers from chat.
• No mobile app; the board is responsive in a mobile browser but touch drag-and-drop is basic.