Skip to content

Sprint 3

Mikael Kalajdzic edited this page Mar 31, 2023 · 8 revisions

Mikael as the Scrum Master

David

During this sprint, I focused on a major refactor for the project. Although the refactor was successfully completed by the end of Sprint 3, I realized that some of my teammates were waiting for me to finish before they could proceed with their tasks. In hindsight, I should have finished the refactor earlier in the sprint to minimize any delays for the rest of the team. On a positive note, while reviewing a teammate's pull request, I discovered that the refactor was not present anymore in his branch. This timely review allowed us to resolve the issues now, ensuring that no refactor-related work would be carried over to Sprint 4. In addition to the refactor, I efficiently completed my other assigned tasks by reusing and adapting existing modularized code in our codebase. This allowed me to finish my tasks quickly and contributed to the overall success of the sprint.

Mikael (Scrum master)

My tasks were both on implementing the events filtering, but in the first week of the sprint I was more waiting for #42 (principal events view by Eric) and on PR56 (list mode by David who was firstly more focused on the big refactoring). This made me nervous when the refactoring was taking more time than expected because my tasks were really dependant on these and I couldn't work much on UI + testing UI. For the next sprints I will take care to not find myself in such situation again. Apart from that, when I could have started to work on my tasks all went pretty good.

As the scrum master for this sprint I was happy how my teammates were easily joinable and available for organising the scrum meetings and all about communication in general. I had no particular issue with my role, it was a nice experience to feel more personally involved in the project apart from only developing.

Aymeric

This sprint I implemented the chat into our wonderful application. There were two tasks: UI and firebase. Once again I finished both during the first weekend which works amazingly for me. Honestly, I really had a blast with these tasks and am really starting to appreciate the intricateness of android apps. This week no one depended on my tasks, because I wanted to learn from the issues encountered during the previous one. The team is working together in a very productive manner. There is always someone available to help with issues that we are facing. We are learning a lot about scrum and android programming in a great work environment with just enough constructive criticism.

Luc

The sprint went without any particular problem for me. The time allocated to each of my tasks was quite accurate. I'm happy to have learned new things with it. For the following weeks, maybe I should take a little more care with the Pull Request. But I spend to much time overall to remerge again and again, with the CI each time,from the main waiting that somebody valideted the requested changes

Thösam

During this sprint, I focused on implementing the QR code feature. It took me some time to find an efficient way to generate a we code and think about the logic behind. Gratefully my part was totally independent from the others, however merging resulted in taking longer time to solve bugs. Also reviewing Mikael’s pull request was relatively easy because what he coded was very clean.

Eric

This sprint went well at first. Sadly, I had to realise two pull requests as features I was implementing were too different. Despite finishing early the features I was assigned to, I had to wait before merging since my task depended multiple other ones. I will try for next sprint to reduce dependencies with other tasks. On the positive side, I got a deeper understanding of how to create XML files and overall learn more about the Filtering queries in a Firebase.

Overall team

As a team we all managed to successfully complete our respective tasks with the estimated time. There was still some dependency between some tasks and some people needed to wait for other before they could continue to work, but this is normal when the task in question is a big refactor. Still, the tasks about the chat and the QR code were completely independent so this could progress greatly. There was two PR which came a bit late (Thursday) and also needed to be reviewed and merged. Hopefully this situation would not reproduce, but in the meantime we managed to finish all tasks, all with a smile at the end :)

Clone this wiki locally