In the last sprint, the mobile app was finalized according to the initial most important requirements. The social projects and initial faculty screens got a final revamp and the faculty location screen was implemented. In the web app, a search bar was introduced in the projects edition page to help administrators find the desired project quicker. Also in the web app (and server as well), authentication was added so as to avoid unwanted requests that would introduce malicious changes to the persisted information.

Closed issues: #5 #9 #16 #34 #71 #72 #73

Velocity evaluation: 21 points were estimated for this sprint, out of which all were successfully completed. This was the normal velocity throughout all the development process and, thus, we expected to successfully complete all that was proposed in the sprint backlog at this stage.

• Test suites got more thorough and global code coverage rose to more satisfiable levels
• Last design details (e.g. app logo) were agreed between dev team, design team and PO (JIT!)

• We could not dedicate time for the development of proper end-to-end acceptance tests

• Developing functionality to edit faculty statistics in the web app. This is reflected in a newly created issue, #74
• Developing functionality to edit faculty research centers in the web app. This is reflected in a newly created issue, #75
• Start preparing product handover to technical team on PO's side. There has been an e-mail exchange discussing the handover procedure to UP's Rectory team. @andrefcruz is responsible for this

• Increased usage of gitlab discussion mechanism
• Development using pair programming, which proved to speed up issue development and bug tracking & fixing

(Note that, once again, 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 29 points in the backlog, the project would be expected to be complete by a 7th sprint.