In the second to last sprint, the goal was to start finalizing the mobile app's design and provide functionalities (edition wise) in the web app. For the first, an in person meeting with the designated designers was done in order to (finally) finalize the mockups for the remaining pages (menu, introduction, future prospects). For the latter, social project edition suffered a small enhanhcement, a menu to select which faculty's information one wants to edit, i.e. future prospects, social projects, videos, alongside the ability to actually edit the latter two. In more technical terms, Continuous Deployment (staging and production) setup was enhanced for all of the project's components.

Closed issues: #3 #13 #35 #37 #38 #46 #50 #68 #69

Velocity evaluation: 20 points were estimated for this sprint, out of which all were successfully completed. The web app enhancement (#69) needed a little extra work, so we recognise it should probably have been estimated with a weight of 4, making the total sprint velocity around 22 points.

• More usage of Gitlab discussions, pointing out what was not so good and where in a more practical and direct way
• Communication with designers more clear than ever
• Full implementation and automation of CD

• Some components do not have a satisfiable test battery (i.e. server)

• Developing more thorough tests for server side, while capturing code coverage. This is reflected in a newly created issue, #72
• Preparing handover manual by detailing general development guidelines/technologies/architectures used, as well as some usage instructions. @cyrilico will be responsible for the guarantee that it is done.

• Increased usage of gitlab discussion mechanism
• Clearer communication with designers through continuous feedback

(Note that despite the chart saying there was one issue left, all were successfully completed and closed) Considering the average sprint velocity (~21 points) and that there are still 42 points in the backlog, the project would be expected to be complete by a 6th sprint.