IITM Online BS · Software Engineering Project · May 2026 Term
Revision note: Chinmoy Das (22f2000481) is on sick leave for this sprint.
All of his Product Manager and Tester responsibilities have been reassigned to
Muktavali Rao. Chinmoy has no assigned tasks this sprint.
To balance Muktavali's load, his primary Code Reviewer role moves to
Abhijay Sharma. Review sign-offs are crossed so nobody reviews a module
they tested: Muktavali signs off MRs for Aditya's modules (which Abhijay tests);
Abhijay signs off MRs for Ramakrishnan's modules (which Muktavali tests).
Sprint 1 Deliverables (full official list) — due 2nd August 2026
Documentation of APIs in a Swagger-compatible YAML file — the YAML must include error handling, user-story mapping, and a description of every API (use an x-user-stories block: story ID → actor → mapped endpoints).
Backend code of the implemented APIs — well commented, with proper error handling, validation, and responses.
Lists of APIs created (by the team) and APIs integrated (third-party / GenAI / libraries) — state explicitly if none were integrated this sprint.
Test cases for each API in the full official format: [API being tested, Inputs, Expected output, Actual output, Result: Success/Fail] — including the actual request payloads.
Showcase at least one API where actual ≠ expected, with a before/after account of the fix — demonstrating how testing improves the API.
pytest code for these APIs, plus screenshots/terminal grabs of pytest output for 4–5 key APIs with failures clearly highlighted.
User feedback and a plan to implement it in the next sprint.
Consolidated Milestone 3 PDF report containing all of the above, opening with an executive-summary metrics table (endpoints built, test cases run, bugs found/fixed).
PM dutiesScrum MasterCode Reviewer (secondary)↳ takes over all of Chinmoy's tasks
Sprint coordination (from Chinmoy)
Coordinate the sprint end-to-end; finalize which API modules are in scope for Sprint 1 (see module split below).
Maintain the sprint board / GitHub Issues; run standups with Aditya.
User feedback deliverable (from Chinmoy)
Collect feedback (team demo + a few outside users), write a per-user feedback summary, and draft per-user planned improvements for the next sprint.
Test case tables (from Chinmoy, co-owned with Abhijay)
Document every test case in the full official format: [API being tested, Inputs, Expected output, Actual output, Result: Success/Fail] — with the actual request payloads included.
Include at least one case where actual ≠ expected, written up before/after-fix style as “how testing improved the API”.
Compile the consolidated submission PDF: executive-summary metrics table (endpoints built, test cases run, bugs found/fixed), lists of APIs created vs integrated (state explicitly if none integrated), test case tables, pytest output screenshots, user feedback and next-sprint plan. Assemble the final submission package: PDF + openapi.yaml + backend code / tests zips.
Retained duties
Secondary code reviewer: verify test coverage on each MR; give the review sign-off on MRs for Aditya's modules (which Abhijay tests).
Keep scrum minutes with Aditya for the milestone document.
Aditya Kumar · 23f3004176
Backend Developer
Implement core API endpoints for his modules: Auth/Users (register, login, roles) + Complaint Management (CRUD, status transitions).
Write the Swagger-compatible YAML (openapi.yaml) for every endpoint he builds: request/response schemas, status codes, auth.
Design each endpoint Swagger-first; the YAML must carry error responses, a description for every endpoint, and user-story mapping (x-user-stories block: story ID → actor → endpoints).
Code must be well commented with proper error handling, validation, and responses (graded criteria for the backend code deliverable).
Write basic pytest unit tests immediately after coding each endpoint (official guide rule); Abhijay builds the full suite on top.
One feature branch + MR per user story, linked to its GitHub Issue, Code Reviewer tagged (existing team process rule).
S Ramakrishnan · 22f3000400
Frontend DeveloperBackend Developer
Implement remaining backend modules: Security/Visitor Management (pre-approve, OTP verify, entry log) + Announcements, plus their sections of the Swagger YAML.
Same YAML and code standards as Aditya: Swagger-first design, error responses + descriptions + user-story mapping in the YAML, well commented code with error handling and validation, and basic pytest unit tests written immediately after coding each endpoint.
Own API integration: wire the Vue frontend views (login, complaints, visitors, announcements) to the real endpoints, replacing mock data.
Abhijay Sharma · 23f3002675
Code Reviewer (primary)Tester↳ takes over Muktavali's primary reviewer role
Primary code reviewer on all MRs: API design consistency (naming, status codes, response envelope, error format consistent across Aditya's and Ram's endpoints), code quality, and integration completeness (every documented endpoint is consumed or tested).
Give the review sign-off on MRs for Ramakrishnan's modules (which Muktavali tests); Muktavali signs off Aditya's module MRs.
Own the pytest suite: unit tests for every endpoint (happy path + validation/error cases), runnable with a single command.
Maintain a test case matrix with Case IDs (Case ID / Endpoint / Scenario / Inputs / Expected / Actual / Result), covering positive, negative, and integration cases per endpoint.
Capture pytest output screenshots / terminal grabs for 4–5 key APIs with failures clearly highlighted (graded rubric item).
Record every discovered bug as a GitHub Issue (evidence to be showcased in the final milestone).
Back up Muktavali on the test case tables.
Chinmoy Das · 22f2000481
On sick leave
No tasks assigned this sprint. Get well soon!
API Module Split (Sprint 1 scope, from the 6 epics)
Owner
Modules
Aditya
Auth/Users + Complaint Management
Ramakrishnan
Security/Visitor Management + Announcements (then integrates all four modules into the frontend)
Deferred to Sprint 2: Finance and AI features — the natural “implement based on feedback” content for the next-sprint plan.
Kanban / Jira Task Cards (copy-paste ready)
One line = one card. In Jira: Backlog → + Create issue (or Bulk create), paste a block below, then set the Assignee once for the whole block. All cards start in To Do.
Muktavali Rao — assignee: Muktavali · 8 cards
Finalise Sprint 1 API scope and create GitHub Issues for all user stories
Run daily standups and keep the sprint board updated
Write test case tables for Visitors/Security + Announcements APIs (full format: API, Inputs, Expected, Actual, Result)
Collect user feedback: demo to team + outside users, write per-user summaries
Draft per-user planned improvements for Sprint 2
Review sign-off on Aditya's module MRs + verify test coverage on all MRs
Keep scrum minutes with Aditya for the milestone document
Compile Milestone 3 submission: PDF report + openapi.yaml + code/tests zips (exec-summary metrics, APIs created vs integrated, test tables, pytest screenshots, feedback + plan)
Aditya Kumar — assignee: Aditya · 6 cards
Swagger-first YAML: Auth/Users endpoints (schemas, status codes, error responses, x-user-stories mapping)
Implement Auth/Users API (register, login, roles) with validation + error handling
Basic pytest unit tests: Auth/Users endpoints
Swagger-first YAML: Complaints endpoints (schemas, status codes, error responses, x-user-stories mapping)
Implement Complaints API (CRUD + status transitions) with validation + error handling
Basic pytest unit tests: Complaints endpoints
S Ramakrishnan — assignee: Ramakrishnan · 7 cards
Swagger-first YAML: Visitors/Security endpoints (schemas, status codes, error responses, x-user-stories mapping)
Implement Visitors/Security API (pre-approve, OTP verify, entry log) with validation + error handling
Swagger-first YAML + implement Announcements API with validation + error handling
Basic pytest unit tests: Visitors/Security + Announcements endpoints
Frontend integration: login/auth flow wired to real API
Frontend integration: complaints views wired to real API
Frontend integration: visitors + announcements views wired to real API
Abhijay Sharma — assignee: Abhijay · 8 cards
pytest suite scaffolding (conftest, fixtures, single-command run)
Full pytest coverage: Auth/Users + Complaints (happy path + validation/error cases)
Full pytest coverage: Visitors/Security + Announcements (happy path + validation/error cases)
Build test case matrix with Case IDs (all endpoints: positive, negative, integration cases)
Write test case tables for Auth/Users + Complaints APIs (full format: API, Inputs, Expected, Actual, Result)
Capture pytest output screenshots for 4-5 key APIs with failures highlighted
Log every discovered bug as a GitHub Issue + write the expected-vs-actual showcase
Primary code review on all MRs (API design consistency, code quality, integration completeness)
Deadline & Scope Note
Milestone 3 is due 2nd August 2026. If time runs short, prioritise finishing
Auth/Users + Complaints completely (implemented, documented in the YAML, tested in the full
format, pytest evidence captured) over having four half-done modules — completeness grades
better than breadth.