Sprint Backlog – School Management System (SMS)

Sprint Number: 3 Sprint Duration: 14 Days (12 Aug 2025 – 25 Aug 2025) Scrum Master: Ramesh Kumar Product Owner: Priya Sharma Development Team Size: 6 Members

---

1. Sprint Goal

Deliver the Student Attendance Module and integrate it with the Teacher Dashboard, ensuring attendance data can be viewed, updated, and reported within the system.

---

2. Sprint Backlog Items

ID	User Story	Priority	Story Points	Tasks	Owner	Status
SB-101	As a teacher, I want to mark daily attendance for my class so that I can track students' presence.	High	8	1. Create DB schema for attendance 2. Develop attendance marking UI 3. API for saving attendance	Dev1, Dev2	In Progress
SB-102	As an admin, I want to generate monthly attendance reports so that I can share them with parents.	Medium	5	1. API for generating reports 2. Export to PDF/Excel	Dev3	To Do
SB-103	As a student, I want to view my attendance history so that I can track my performance.	Medium	3	1. API for fetching history 2. Student portal UI changes	Dev4	To Do
SB-104	Integrate Attendance Module with Teacher Dashboard	High	5	1. Dashboard API changes 2. Frontend integration	Dev5	In Progress
SB-105	Test Attendance Module	High	5	1. Write test cases 2. Perform unit and integration testing	QA1, QA2	To Do

---

3. Definition of Done (DoD)

• Code reviewed and merged into main branch.
• Unit tests passed with ≥ 90% coverage.
• No critical or high-severity defects pending.
• Approved by Product Owner.
• Deployed to staging environment.

---

4. Sprint Risks

Risk	Impact	Mitigation
Delay in report generation API due to data complexity	Medium	Assign an additional backend developer to assist
Integration issues with existing dashboard	High	Schedule early integration testing

---

5. Sprint Burndown Chart

(To be updated daily by Scrum Master using Jira or Excel)

---

6. Notes

• All developers must update Jira tasks daily before stand-up.
• QA testing to start in parallel once first feature is ready.