Sprint Goals and Backlog 2
This is the wiki page for Sprint 2, you can find the GitHub Project for Sprint 2 here
During this sprint, our main goal was to implement all the components that are necessary for a MVP discussed in sprint 1. A few examples such as making an easy and clean interface that can interactively show information about places around campus. A framework for pane switching within the app in order to pave the way for future additions of capability. We also want to have a designated Sign In Page, even if account login is not supported (yet). Finally, we want to have a populated database that works locally with the app storing building information.
Unlike last sprint, we did not find the need to add tasks halfway through the sprint, finding the tasks we set to be helpful and effective at making progress in small chunks. We were satisfied with our actual MVP by around two days before the sprint was over, and everything after that was extra stuff that we are glad we finished but was not strictly necessary.
Below is our burn-down chart for this sprint, as with last time, we were not able to get all of our tasks done. Populating the database is going to take more time than we thought as while we have gathered a large amount of building data, we aren't sure exactly what we want. Also, Map Navigation is a task for later because there aren't inherently right choices for what API we should use, and it might not take the same form that we initially expected
This sprint it was pretty clear we were getting into the swing of the Agile work environment, as well as our group dynamics and goals as a whole.
Some of the things that we think went particularly well for us:
- Working on particular tasks and making progress when needed
- Collaborating on things when required, combining understanding and learning TypeScript together
- Meeting and finding time to communicate when necessary, we have genuinely been very efficient and prompt with problems/new issues that come up
Some of the things that we can improve on in the coming sprints:
- Getting everyone on the same page with things they are not explicitly working on
- Setting more reasonable expectations (better to under-estimate and deliver more than over-estimate and miss some tasks)