In this first sprint, the goal was to get all the necessary tools to start working ready and to start working on the mobile app, most specifically on a base structure for all the pages, with information dynamically retrieved from a fake API (as working on the back end was not planned) with proper navigation between them. Despite a more than desired delay on the initial setup, the conceived increment was done: the mobile app has a base structure for all screens and is navigable. In more technical terms, the start of a CI system was achieved, as well as containerization of the development environment.

Closed issues: #2 #4 #6 #7 #26 #39 #40 #41 #42

Velocity evaluation: The initial delay caused two of the sprint goal PBIs ( #1 and #8) to not be completed, although they were being worked on. Since the initial delay, caused by a lack of knowledge about some of the tools used, is not to be expected again, the group considers the estimated velocity to not have been (grossly) off.

• Sprint goal was reasonably achieved
• Some side enhancements were began in a parallel way (e.g. CI, virtualisation w/ Docker)
• Branch naming guideline defined allowed for easily distinguish between different types of work being performed
• 3 people (instead of the "normal" 2) reviewing PRs

• Communication with the PO wasn't always optimal
• Communication inside the team was shaky at first and focused solely on a group chat where quite some relevant information would get temporarily lost often
• Initial project setup took too much time
• Pull requests were initially reviewed too much only for what worked instead of inspecting other aspects more thoroughly

• Insisting more with PO when she doesn't answer by email (i.e. contact by phone number sooner)
• Use another platform (e.g. Slack) to publish important announcements so as to not get easily lost
• Start (gradually) using more automated tools to ensure product quality

• Putting almost all the information in the same group chat, as it gets lost very easily and/or people might miss important aspects
• Having too many people work on the same set of features

• Using the defined branch naming guideline
• Reviewing PRs more thoroughly (not only feature wise, but code wise; although a problem at the start, the team started doing it by the end of the sprint)

Considering the velocity in this sprint (~22 points) and that there are currently 75 points estimated left in the Backlog, the team would say that the project should be complete by the end of Sprint 5