ryantpham.com
Agile Software Development · Simulated Team Project

Student Information SystemAn Agile Project Case Study

A simulated Agile team project — building a Student Information System across 3 two-week Scrum sprints with full sprint planning, backlog, and release delivery.

Domain: Higher-Ed Web Platform Method: Scrum · PERN Stack Team: 4 Members

1. Overview

The Student Information System (SIS) is a simulated Agile project run over a full academic semester: a 4-person Scrum team designed and built a web-based class registration platform for Administrators, Professors, and Students — user management, course catalog management, class roll and grading, and course enrollment — delivered across three two-week sprints on the PERN stack (Postgres, Express, React, Node).

Team: Thanh Nguyen (Product Manager), Eric Martinez (Scrum Master), Loc Nguyen (Developer), and Ryan Pham (Tester).

My role was Tester: developing test strategies, test plans, and test cases; running system tests each sprint; reporting bugs; and verifying delivered features against acceptance criteria. I also contributed directly to frontend implementation — login, student portal, and transcript view functionality.

2. Agile Process

The team ran full Scrum ceremonies across Sprint 0 (technical spike) and three delivery sprints, with a defined role for every team member and a release plan that adjusted as scope was learned.

Sprint Planning

Each sprint opened with backlog review, story-point estimation, DONE-criteria definition, and a top-5 risk identification — committing the team to a realistic, sized scope before work began.

Standups & Backlog Refinement

Three standups a week tracked progress and surfaced blockers in real time; dedicated refinement sessions kept the backlog prioritized as the Product Manager added and reprioritized user stories.

Sprint Review & Retrospective

Each sprint closed with a live product demo against sprint goals, stakeholder feedback captured directly into the backlog, and a start/stop/keep retrospective to improve the next sprint.

Release Planning

The release plan was revised twice mid-project as scope and velocity became clearer — a realistic look at how Agile plans adapt under real schedule and workload pressure, tracked with burndown charts in Jira.

3. Document Preview

The full 40-page Project Summary Report, rendered as a scrolling two-page spread — scroll within the frame to read the whole document, or jump to the full PDF downloads below.

Student Information System — Project Summary Report
40 pages
Loading document…

4. Full Documents

Two artifacts from the project: the initial Project Plan (team roles, scope, and schedule) and the complete Project Summary Report (all sprint activity, standups, retrospectives, and burndown charts).