Iteration Summaries - SoenCapstone/GameOn GitHub Wiki
a. Iteration 1
The purpose of this iteration was to establish a solid and workable foundation for the project. The team focused on defining the initial project scope for the release and designing the early system architecture. Both the front-end and back-end environments were set up and fully dockerized to ensure consistency across development environments.
In parallel, the UX team created the initial application mockups along with a style guide to ensure visual consistency moving forward. The GitHub environment was also configured, including issue templates, project boards, and CI/CD pipelines. Core authentication features such as login and sign-up screens were implemented, along with logging mechanisms for both the front-end and back-end services.
b. Iteration 2
This iteration marked a major milestone with the complete dockerization of the application, enabling all team members to contribute efficiently in a shared environment. Significant backend progress was made on the Teams entity, as well as improvements to session security.
The UX design was refined and finalized after multiple design drafts and reviews, solidifying the overall user experience direction. A feature-flag system was introduced to control feature access and improve security. On the front end, an early version of the user profile page was implemented.
c. Iteration 3
During this iteration, the authentication flow was completed with finalized sign-up and login pages. Core navigation components, including the application’s navigation bar, were added to improve usability and structure.
Feature flags were integrated into the backend to support controlled feature rollout. Additionally, several design concepts were created for upcoming features, most notably the role manager, laying the groundwork for future iterations.
d. Iteration 4
Iteration 4 focused on finalizing documentation, strengthening security features, and completing the authentication system update. The primary goal was to prepare the application for Release 1, ensuring that both the front-end and back-end were stable, integrated, and well-documented.
Most planned tasks were completed on schedule. Several wiki pages were finalized ahead of time, while minor presentation-related updates were deferred to the next release for further refinement.
e. Iteration 5 Report
During this iteration, the team produced mockups for user-to-user chat functionality, helping define the structure and flow of the messaging experience. The backend CI/CD pipeline was updated to build and test additional backend services automatically.
CRUD operations for the League microservice were implemented, enabling core league management functionality. This sprint recorded the lowest development velocity so far, primarily due to multiple team members managing exams and major coursework in parallel.
f. Iteration 6
Due to finals and the Christmas holiday period, team availability was lower than expected, resulting in reduced sprint output for what was originally planned as a feature-heavy iteration.
Despite this, several important updates were completed. The front end received new components, primarily populated with mock data. The Team microservice underwent a backend rework, and a fully implemented backend Messaging service was completed. Additional front-end components were also added to support upcoming features.
g. Iteration 7 Report
Iteration 7 focused heavily on completing one of the core features outlined in the project proposal: messaging. Several key user stories were completed, including full messaging UI integration and backend support.
Additional work included the Play Maker feature design, team invitation UI, season management functionality, and backend fixes related to database migrations. This iteration significantly improved real-time communication and collaboration features across the platform.
h. Iteration 8 Report
During this sprint, the most significant addition was the implementation of Stripe-based payments for public leagues, developed within the backend Leagues microservice and fully integrated with the front end.
Additional features included league and team integrations such as invitations, as well as visual refinements across the application, including updates to the Play Maker feature and overall UI polish. Usability testing was conducted during this iteration, and the application was successfully deployed, marking a major step toward production readiness.