In the second sprint, the goal was to have a functional back end server so as to be able to ditch the fake API, develop some editing functionalities in the web app and start to refine the mobile app's design (converging to a final solution, despite some constant mockup refinement). However, this was all preceded by an overall information restructure (mainly on the mobile app) to facilitate development (e.g. Redux integration) and impose some development guidelines. This caused some delay in the actual redesign of the mobile app screens. In more technical terms, the sever was successfully containerized, a unit test structure for the mobile app was created and a linter has been attached.

Closed issues: #1 #14 #21 #43 #44 #45 #48

Velocity evaluation: The necessary information restructure on the mobile app delayed the redesign of the screens, which caused some issues to not be completed, namely #47 (mid way completed), #8 and #50 (not started). For this reason, the group will lower the estimated velocity for the next sprint to around 21 points (+- 1/2 points).

• Good discussion on all merge requests;
• Sprint goal was reasonably achieved;
• Some side enhancements were began in a parallel way (e.g. CI, CD);
• Thorough definition of development guidelines and their automatic enforcement.

• Issue estimation was slightly off the mark;
• Communication with the PO wasn't always optimal, as she was not easily reachable;
• We still lack a good code coverage of automated tests.

• Start explaining how to test MRs more thoroughly (if applicable);
• Start managing PO expectations regarding future changes to the already planned project (new features should me minimised);
• Start developing unit tests for all implemented features.

• Stop taking too long to review merge requests;
• Stop delaying closure of issues until the end of the sprint.

• Good communication as a result from a sub-division of the group on smaller groups;
• Good communication of the development process and challenges with the PO;
• Good division of tasks among team members;
• Usage of more automated tools to ensure product quality (linter was a first step introduced later in the sprint).

Considering the velocity in this sprint (~21 points) and that there are currently 68 points estimated left in the Backlog, the team would say that the project would be complete by the end of a 6th sprint