In order to develop Spotify Wrapper, we followed a Scrum workflow. We divided all the user requirements into two distinct sprints, each with specific user requirements to be accomplished by the end of each respective sprint.
Below is some more detail on how we decided to divvy up our user requirements between our sprints to finish the application.
Sprint 1 Details
Sprint 2 Details
We chose these specific user requirements to be a part of our first sprint because we felt they were the paramount components to complete as soon as possible. User authentication was a priority since it is an integral feature for users to be able to log into an account in order to link account information to users. Aesthetic UI was very important to us for this project as it laid the framework for how every page would fit a single theme that would look nice to users. Lastly, Spotify account linking was very important to get done early for this project as every feature of app relied on Spotify API calls to gather user data for the wraps. This can only be done if users can successfully link their Spotify account to their Spotify Wrapper profile.
We chose these specific user requirements to be a part of our second sprint because these features took lower precedent compared to the components of sprint one. Sprint two contains requirements such as the account page. This page did not have a specific need for prioritization since other app features did not rely on it being built. Another such page is the developer contact page. Here, you can learn more about the developers who build the Spotify Wrapper app and also submit a developer contact form. Lastly but the most important requirement for sprint two, we created the base information that would be the foundation for the actual Spotify wraps. Completing this requirement was crucial for sprint two as it allowed us to continue working on the main feature of the Spotify Wrapper app, the generated slideshow based on user listening data. This requirement consisted of calling the Spotify API to request data such as a user's top 50 artists and tracks.
Sprint 3 Details
We chose these specific user requirements to be a part of our third sprint because these features were the last components that needed to be completed for the application. The most important requirement for sprint three was the Spotify Wrapper slideshow. This was the major feature of the Spotify Wrapper app which displays user listening data in a fun and interactive way. The wrapper includes information such as top artists, tracks, and genres, as well as, fun games about users listening history. Additionally, sprint three saw the creation of the saved page which hence the name, saves all of a user's created wraps for later access. Lastly, we created the ability to share a user's created wraps with others via social media websites such as X and Reddit.