1
Sprint Review and Retrospective for the SNHU Travel Application Development
Project
Southern New Hampshire University
CS 250: Software Development Lifecycle
Joseph Martinez
December 13, 2025
, 2
This paper contains the formal Sprint Review and Retrospective for the SNHU Travel
application development project done by ChadaTech. The project was a pilot project aimed at
testing the possibility of the organization shifting from its conventional traditional Waterfall
approach to the Scrum-Agile model. Besides providing a working travel application to the
SNHU Travel client, the project was intended to evaluate efficiency of the Agile practices,
application of Software Development Life Cycle (SDLC) in the Scrum, and the general value of
the iterative application development. This retrospective presents evidence-based suggestions
that can be used to inform future development strategy at ChadaTech through reflective analysis
of team roles, completion of user stories, change management, communication practices, and
organizational tools.
The well-defined and collaborative roles set in the Scrum framework were major
contributors to the success of the SNHU Travel project. The Product Owner was responsible for
maximizing business value by continuously refining and prioritizing the Product Backlog. The
Product Owner prioritized making sure that the development process aimed at creating value to
the user immediately by ensuring the prioritization of high-impact features, like personalized
destination suggestions were focused on. This prioritization plan enabled the early release of
Minimum Viable Product that gave the stakeholders the opportunity to test the basic
functionality with further development happening during further sprints. The Product Owner
kept the customer expectations and development outputs aligned by involving the stakeholders
on a regular basis.
The Scrum Master also proved helpful in project success as he acted as a servant-leader
and facilitator to the team. The Scrum Master fostered efficiency and responsibility within the
project by training team members on the Scrum principles and making sure that they comply
Sprint Review and Retrospective for the SNHU Travel Application Development
Project
Southern New Hampshire University
CS 250: Software Development Lifecycle
Joseph Martinez
December 13, 2025
, 2
This paper contains the formal Sprint Review and Retrospective for the SNHU Travel
application development project done by ChadaTech. The project was a pilot project aimed at
testing the possibility of the organization shifting from its conventional traditional Waterfall
approach to the Scrum-Agile model. Besides providing a working travel application to the
SNHU Travel client, the project was intended to evaluate efficiency of the Agile practices,
application of Software Development Life Cycle (SDLC) in the Scrum, and the general value of
the iterative application development. This retrospective presents evidence-based suggestions
that can be used to inform future development strategy at ChadaTech through reflective analysis
of team roles, completion of user stories, change management, communication practices, and
organizational tools.
The well-defined and collaborative roles set in the Scrum framework were major
contributors to the success of the SNHU Travel project. The Product Owner was responsible for
maximizing business value by continuously refining and prioritizing the Product Backlog. The
Product Owner prioritized making sure that the development process aimed at creating value to
the user immediately by ensuring the prioritization of high-impact features, like personalized
destination suggestions were focused on. This prioritization plan enabled the early release of
Minimum Viable Product that gave the stakeholders the opportunity to test the basic
functionality with further development happening during further sprints. The Product Owner
kept the customer expectations and development outputs aligned by involving the stakeholders
on a regular basis.
The Scrum Master also proved helpful in project success as he acted as a servant-leader
and facilitator to the team. The Scrum Master fostered efficiency and responsibility within the
project by training team members on the Scrum principles and making sure that they comply
