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.

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.

The left are example images from the beginning of Sprint 2.

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, showing the map using the API, and creating front-end mockups. Our second sprint was more focused on adding new features, like password reset and the favorites list, and upgrading the UI. This workflow allowed us to stay adaptable, continuously improve, and appropriately prioritize our goals.

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.