Process Description
Walk through our process!
01
Our development approach embraced the agile Scrum framework, with several developers branching out to work on different features independently. This allowed us to leverage parallel development, speeding up the creation process while maintaining code quality and coherence. We outlined our tasks and progress using Trello and communicated daily via our Microsoft Teams chat. We also had weekly check-ins with our "client" (mentor TA) to provide progress updates and receive feedback, ensuring strong deliverables.
Each branch focused on incremental advances, whether it was enhancing the user interface, implementing backend logic, or integrating with Spotify's API.
02
As features matured and proved their stability, we merged these branches into a staging area. This approach facilitated thorough testing, ensuring that any integration issues were caught early. The successful features were then merged into the master branch in preparation for deployment.
03
A key design pattern emerged during the development of the application's slideshow feature. Many of the slideshow pages shared common behaviors and visual elements, leading us to abstract these similarities into a single class. This consolidation significantly reduced redundancy, streamlined our codebase, and made future adjustments much more manageable. By using diagrams and design documentation, we could illustrate how this pattern was applied consistently across the application, ensuring a uniform user experience while maintaining the flexibility to add unique elements to individual slides.
Example use case:
This is our SD for a scenario where a user wants to go through the app and reach the game at the end of the slideshow. Here, they will be able to view their most listened too songs, view their playlists, and play a game from their selected playlist.