CS 2340 Group 12 Website
Group 12 Team Website
The Team
Who We Are
Emily Rosenfeld
Scrum Master & Back-end Developer
Shanaya Bharucha
Back-end Developer
As a back end developer, Shanaya created the Spotify Developers account and, along with Emily, worked with the spotify API to get the data to generate the spotify summary. She worked closely with Emily to create the models to save the spotify summaries as well as developing the code coverage tests and our CD/CI pipline. She also added the documentation for the Python and Javascript code and did the backend for contact developers.
Anne Youn
Product Owner and Full-Stack
Anne did the entire front and back end of the landing page (such as the navbar/buttons), logout, account settings, summary slides 6 and 7, delete account, and delete song history. She also created the style guide, outlined each page in a wireframe, and listed each page's components for the Figma. She focused on creating and ensuring that the modal feature was working and aesthetically pleasing. Her main full-stack user stories were dark-mode and song snippets, which she did the entire front and back end of using bootstrap. As product owner, she managed communication (creating and organizing the Discord) between the team and our client, helping team members meet their deadlines, helping address and fix their errors, and remember to do scrum. She also created the team website.
Joanne Gosal
Full-stack
As a front end developer, Joanne created the front-end for the user dashboard, contact developers, spotify wrapped history, spotify wrapped summary, and loading pages. She also designed all icons used throughout the website and helped establish the theme and typography on Figma. Joanne worked to improve the UI and aesthetic of the website, including colors, size adjustability, animations, and hover effects.
Jessica Osborne
Full-stack
As a full stack developer, Jessica created the majority of our page designs in Figma. She also worked on the front end for the main and saved Spotify Summary and connected the backend data to correctly display on those pages. Additionally, Jessica did both the front and back end of the quiz functionalities, and implemented the transitions and hover effects on the summary slides.
Our Process
For project management, we improved on our old Notion board. As before, we used Notion to record the different tasks, update with new tasks, and mark tasks as completed. However, we also used the calendar section of Notion to plan out our different tasks over a month in advance, which was important for a project of this scale. We also recorded our daily standup notes, so everyone knew what everyone was working on. It was a useful tool for all of us, but especially for our scrum master, so she could keep everyone organized.
Discord was also an important place for us to keep communicating and asking for help. During the last project, we all started defaulting to using the general channel, which made it harder to go back and find old discussions about specific front-end or back-end issues. This time, we made sure to put our conversations in the appropriate channels, which made our Discord much more streamlined.
​
We followed the Scrum sprint method by prioritizing our user stories on hard deadlines and dependencies. This meant that for our first sprint, we made sure our front-end had the figma diagram all connected with the general UI decided and our back-end had the CD pipeline set up on GitHub and could access the Spotify API. Then in our second sprint, we wanted to get the base functionality of the necessary user stories working, so that in our third sprint, everyone could finish their individual extra user stories so that we had a total of 21 story points.
In the first image below, you can see how we used System Diagrams to map out the different user stories and how they depend on each other. In this example, since it was clear that the main complexity in the base user story of displaying Spotify data was getting that data from the Spotify API, we prioritized that over designing the actual display. These diagrams made it easy for us to keep track of the important pieces and patterns of code as the project expanded in complexity.
Our GitHub usage was much more streamlined during this project than the last. The use of the CD pipeline along with running over 80% code coverage tests and forcing a peer review of all pull requests ensured that main was always protected from pushes that would break something. We had many more small commits and branches created and destroyed, in keeping with the fast and incremental improvements that are the backbone of agile project management.
