In this Sprint Retrospective, I will review the achievements and challenges of the recent sprint with Chada Tech. In traditional waterfall workflows, development progresses sequentially through rigid stages with minimal stakeholder feedback, often leading to isolated silos, outdated features, and an inability to adapt to changing customer needs. In contrast, the Agile framework enables continuous team collaboration and immediate responses to design changes during the active sprint cycle (Beck et al., 2001). The following sections summarize the team's work during the SNHU Travel Boutique pilot.

At the project's start, we developed user stories to prioritize our work and manage the backlog. One initial story stated that as an end user, I want to view a list of the top travel destinations so that I can quickly browse popular vacation choices to decide where to go (Gilbraith, 2026). Looking closely at project roles, the Product Owner (PO), recognized that users were overwhelmed by text-heavy lists. The PO prioritized this feature in the backlog and defined the slideshow's behavior. This clarity allowed the developer to focus entirely on technical layout restrictions, text wrapping, and UI features without guessing requirements. Simultaneously, the tester focused on building exact validation steps, such as verifying the greater than or equal to 90% algorithmic matching engine threshold and measuring 10px borders, ensuring the code met all user acceptance criteria.

User stories also facilitated realistic sprint scheduling through estimation based on effort and time. Sizing each story ensured a balanced workload that team members could realistically accomplish within the sprint window. For example, the user story regarding customer travel recommendations based on historical data was sized as large due to complex backend logic, while the story for viewing an amenities list was labeled small (Gilbraith, 2026). This intentional balance prevented scheduling multiple large tasks in a single sprint, protecting team capacity.

Mid-sprint feedback forced a shift in our priorities, requiring the layout to transition from a static list format to an interactive slideshow. In a typical waterfall cycle, this change would remain hidden until the formal testing phase, forcing expensive re-scoping or an entirely new project cycle since waterfall workflows cannot move backward. Under the Agile model, the team seamlessly accommodated this pivot. The information was brought to the entire cross-functional team during a daily stand-up meeting, allowing members to immediately adjust layout panels and rewrite testing verification scripts.

Accomplishing our goals within this strict deadline required transparent, continuous communication across all partners. To ensure alignment during the layout transition, written communication was heavily utilized to clarify acceptance criteria before updating the user interface:

Dear Product Owner, I am developing the initial and revised test cases to establish success criteria for system validation. While the user stories explain what features are wanted at a high level, they do not provide the exact user interface details required to create concrete pass/fail measures. Specifically, for the user stories involving search filters, the criteria leave out where these elements should live structurally on the screen. Could you clarify if the team prefers these filters displayed as a sidebar, a modal overlay, or placed in the header or footer? Because UI elements are not described within the user stories, we need to finalize these locations to build a user-friendly layout. To gather this information during development, I suggest we schedule user testing, such as focus groups or A/B testing, to help determine the most effective visual locations and UI elements to meet the goals of the user stories. Please let me know your thoughts so we can align our test cases accordingly. (Gilbraith, 2026)

This communication was highly effective because it proactively addressed UI constraints before final testing began. By bringing cross-functional roles together to solve a technical dependency, the team prevented duplicate work and established clear visual parameters.

To ensure transparency, our team relied on the product backlog and the sprint backlog. The product backlog acted as our single source of truth, capturing every user requirement and layout modification. Because the Product Owner kept this backlog updated and prioritized by business needs, the team easily pulled high-priority items into the active sprint without debate. During execution, the sprint backlog was paired with daily stand-up meetings where team members answered three questions regarding past progress, daily focus, and current impediments to ensure continuous alignment (Schwaber & Sutherland, 2020). This tight loop maintained transparency and reduced time wasted on miscommunications. At the end of the development cycle, the completed backlog items allowed us to demonstrate working software increments to Chada Tech stakeholders, providing clear proof of our velocity.

Transitioning the SNHU Travel pilot to a Agile framework brought clear advantages, primarily the ability to adapt to changing user requirements rapidly and catch inconsistencies early through parallel development and testing. However, it also introduced operational challenges. The framework required a high level of continuous collaboration that initially strained a team accustomed to siloed waterfall workflows. Additionally, breaking down a complex travel application into bite-sized user stories required significant initial effort during backlog refinement to ensure accurate story sizing.

Ultimately, the Agile framework was the best choice for the SNHU Travel Boutique project. This application operates in a dynamic market where user interface standards and customer expectations change daily. By utilizing Agile, the team managed interruptions effectively, maintained a predictable delivery cadence, and delivered a functional, user-centric application on time. Based on the success of this pilot, expanding the Agile framework to the broader organization is highly recommended to improve product quality and foster a collaborative corporate culture across Chada Tech.

References

Gilbraith, K. (2026). SNHU Travel user stories, product backlog, and Journal Entry (Unpublished manuscripts). Department of Computer Science, Southern New Hampshire University.

Beck, K., Beedle, M., van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M., Grenning, J., Highsmith, J., Hunt, A., Jeffries, R., Marick, B., Martin, R. C., Mellor, S., Schwaber, K., Sutherland, J., & Thomas, D. (2001). Manifesto for Agile Software Development. Agile Alliance. https://agilemanifesto.org/

Schwaber, K., & Sutherland, J. (2020). The Scrum Guide: The definitive guide to Scrum: The rules of the game. Scrum.org. https://scrumguides.org/scrum-guide.html

AI Usage Disclosure: In accordance with Southern New Hampshire University academic integrity guidelines, I acknowledge utilizing generative AI (Gemini) to assist in refining the phrasing of this assignment to meet specific length constraints, ensuring proper integration of technical course terminology, and formatting references according to APA 7th edition guidelines. All primary conceptual arguments and project reflections represent my own authentic work.