Our Process
Throughout the course of this project, our team followed scrum, meaning we worked in sprints, held a backlog, and worked closely with all involved stakeholders to make consistent progress, feature-by-feature, over time. Additionally, we used a wire-flow diagram to assist in top-down software develoment.
01
Planning & Task Division
Our planning was done in sprints, according to scrum. We started off by implementing a Trello and labeling certain tasks for Sprint 1 and leaving the others on backlog. This allowed us to prioritize the most important features of the site while staying adaptable.
Using Trello also allowed us to differentiate between current tasks and the backlog. As you can see in our images to the left, primary tasks for sprint one were given a purple lavedar label, marking them for the sprint 1 and leaving the others on backlog until sprint 2 or 3.
​ The left are example images from near the end of our project.
02
Workflow
We typically worked in smaller groups to accomplish distinct features for each sprint. Our first sprint worked to set up key functions such as allowing users to log in with Spotify, successfully querying key data from the API, and creating front-end mockups. Our second sprint was more focused on improving these features by creating the actual wrapped slides and beginning frontend coding. Lastly, the third sprint focused on adding our additional user stories like games and additional UI themes to give more varied functionality to the site. This workflow allowed us to stay adaptable, continuously improve, and appropriately prioritize our goals.
.png)
.png)
03
Communications
Per the scrum methodologies, we continuously worked on various aspects of the project, not one at a time. This required not only consistent communication amongst teammates, but timely communication with our client (TA) to make revisions as we worked. To do this, we used Discord to keep daily updates, store useful information, and ask our client questions. We also used github to maintain version control, allowing us to incrementally add new features and work in smaller teams (like front-end and back-end) rather than step-by-step like the waterfall model.
04
Top-down Development
We used a wire-flow diagram to promote top-down software development during this project. This diagram served as a guide for frontend developers by providing a visual representation of the site and the user's navigation through it. This assisted in top-down software development because it allowed us to break up the bigger idea of "a website" that accomplishes various tasks in to multiple subsections based around appropriate pages and distinct functionalities. All together, this diagram made tasks easier to separate throughout our web pages and created a more organized, comprehensible guiding document for the larger project.
