Code Reviews

Code reviews were conducted through collaborative discussions and GitHub-based workflows. Team members reviewed each other’s changes by examining commits, pull requests, and shared code in Team meetings before integration into the main branch.

Although formal review tools and approval systems, in general, were not consistently enforced, there was active participation among team members in verifying functionality, identifying issues, and suggesting improvements. This was particularly important when working on shared components such as controllers and utility functions. The main code review that occurred on GitHub was for Sprint3, after all the code was finalized.

The team demonstrated continuous feedback and iterative improvement, especially when resolving integration issues and refining features such as authentication and data handling. Moving forward, adopting a more structured pull request review process would further strengthen code quality and accountability.