Skip to content

Sprint 4

AlSchlo edited this page Mar 25, 2022 · 10 revisions

Summary for sprint 4

Adrien

This week was a lot different than the others. It was a new experiance to work on the same task with another scrum member. It was pretty interesting to echange and sometime confront our idea for the implementation of the task.

I didn't do lot of coding this we week but I had a lot of reflection to have an overview of our database to implement the interface the best way possible. And then I had to learn a lot on firebase feature. Despite this reflection time everthing went well and we archieved to finish our task in the time we hestimated and even manage to add some demo for the sprint review. .

Alexandre

This was quite an interesting week, I learned a lot and my time estimates were nearly on point. I'm glad I allocated more time to search for an emergency numbers database since this was harder to find than I would have thought (I had to combine several databases to have one as complete as possible). For the rest, the implementation went quite smoothly.

What I could improve on would be to do more research beforehand if my task relies on some external factor (here: the existence of such a database) to avoid any surprises during the sprint.

Alexis

Very interesting week. Perhaps the best one till now. I learned how to work efficiently with another member of the team (Adrien). Our task was mainly conceptual, thus a lot more fun. Also, our estimates this week were spot on! Finally, the database being conceptualized, this paves the way for a lot of exciting new tasks.

One minor setback we had this week was ONCE AGAIN related to Cirrus CI. For some reason, Firebase tests won't run on Cirrus (generate a timeout) even though the database is publicly accessible without any key. This was frustrating, as our coverage took a hit again for no reasons at all. Anyways, mocking the database is planned in future sprints.

Emilien

This week was nice. Considering I underestimated the time taken by my tasks those last few weeks I took a light task to be safe and it went well. I implemented a more intuitive UI for the map and changed the way we handled permissions. I also made a custom map but it does not seem to work for now which I cannot explain, I might have to translate it to a local JSON if we want to use it in the future. We seem to work well as a team and I am looking forward to next week.

Hind (Scrum Master)

This was a nice sprint, I managed to finish my task in a reasonable time. Implementing the first aid tutorials was really fun especially since it enriched my general culture about emergency procedures. Now that I am a bit more familiar with Android Studio, I am able to spend more time working on the actual task itself rather than discovering how it works.

Also as a scrum master, I managed to keep the standup meetings short and efficient.

Wiam

This week I implemented the search bar feature. Users can now look up features and start their activity directly from the search bar. I also implemented well-modularized tests that achieved 100% of coverage. I added a small tutorial for the rest of the team on how to add new features to the list view so that it can be populated by more elements during the upcoming weeks.

My time estimates this week were on point. I think the issue before was only considering the time it will take for me to implement a feature and neglecting the significant time it takes to actually implement tests.

Overall team

In this sprint we did significant progress in implementing our app features. We addressed several user stories that imply important parts such as the map and the database.

The main problem we faced is the difficulty or incapability of testing every single part of the code. This is mainly due to the fact that we use external libraries that require dependency injections which take some time to implement. Also, tests usually fail randomly on the CI which makes the merging take way longer than it should.

Standup meetings were great and efficient, the time slots we plan are such that everyone can have time to add new features between the two meetings.

Overall, we are again very proud of what we've achieved so far!

Clone this wiki locally