In the third sprint, the goal was to start converging to the expected final solution, while finishing up the setup for good development practices (development guideline enforcement). For this, much of the mobile app screens were redesigned to meet the final mockups' look. There was also the need to create new screens due to late, high priority information requirements. Web app wise, editing a social project functionality was introduced. In more technical terms, linters were enforced in the web app and server, a unit test structure was developed for the remaining modules (i.e. server and web app), inclusive some tests added to them, and CD implemented for the server.

Closed issues: #8 #12 #47 #49 #54 #59 #62 #64 #65

Velocity evaluation: The sprint backlog contained 23 points, out of which all of them were completed. However, the mobile app unit test structure proved to be a more difficult task than antecipated (4 points instead of 2), so in practice ~25 points was the actual sprint velocity, which was a little higher than normal. This does not mean the next sprint backlog will have more effort points, as we consider ~20/21 our ideal velocity and, considering the next sprint will be during a busier period, do not want to get ahead of ourselves.

• More usage of Gitlab discussions, pointing out what was not so good and where in a more practical and direct way;
• Beginning of convergence to a final solution
• Thorough definition of development guidelines and their full automatic enforcement.

• Communication with the PO wasn't always optimal, as she was not easily reachable;
• Continuous deployment is still not fully setup (lacking web app CD);

• Integrate unit test development alongside the respective feature development by taking both into account when estimating PBI effort points
• More frequent and clearer communication with the design team by providing feedback (from PO's perspective) and challenges we have implementing certain aspects of the mockups periodically (e.g. twice a week)

• Making autonomous design changes (without consulting design team first - as requested by PO)

• Increased usage of gitlab discussion mechanism
• Good communication as a result from a sub-division of the group on smaller groups;
• Good division of tasks among team members;

Considering the average sprint velocity (~21 points) and that there are still 53 points in the backlog, the project would be expected to be complete by a 6th sprint.