Report Sprint 1

Sprint 1- Summary of Progress

The following report highlights some key elements of our implementation of Sprint/Deliverable 1.

Management

Meetings

We held four official meetings overall with a few informal meetings in between where we implemented or further discussed some features together. While we felt that the informal meetings were productive in terms of work, schedule conflicts did not always allow for the whole team to meet at once all the time. We were always able to inform absent teammates of what was discussed during the meeting afterward but we agreed that for the following sprints that we should better schedule meetings so that we could all be present.

Issues, documentation and wiki

All team members were able to adjust to the use of Github issues and Github wiki early on. We tried to break down certain tasks into subtasks (namely the creation of new versions of the domain model) but felt that the breakdown of tasks for the creation of the database and test writing could have been clearer.

Tasks completed

Overview

We were able to complete all tasks in the project description. We were able to create our functionality list, use case diagram, and a first draft of our domain model relatively quickly. After we were able to set up Gradle, Travis CI, Heroku and SpringBoot, we began implementing the persistence layer and writing tests. This last task took the most time to complete.

Requirements

Of particular note for our requirements list, while functional requirements reflected the client's desireds in the assignment description, the non-functional requirements were selected as we felt that they would be good quality of life improvements for the app user.

Class diagram

We created a few iterations of our class diagram during the sprint. These were mainly created to address redundancies and small oversights.

Persistence and tests for persistence

This aspect of the sprint took the longest to implement. We encountered trouble in creating the database, as we had initially forgotten to add unique ids to our classes before then encountering. We then had to experiment with JUnit testing in order to resolve bugs and ensure our tests were written thoroughly.

While most tests were written and returned successful, a handful of tests returned as errors or failures. These errors were not able to be resolved in time for the deliverable deadline as we were unable to determine their cause. For these cases we plan on consulting the TA for guidance early into Sprint 2.