Schedule

Overall Philosophy

Our schedule foused on an agile based methodology that centered around each individual developer tackling a different feature. This was a strategy to mitigate merge conflicts in order to save the team time on our limited schedule. The first semester focused on planning such as writing documents, deciding on a tech stack, testing our tools, etc. The second semester was where developement kicked off, starting with the bones of the project such as setting up the AWS server and our server-side routing.