---
# System prepended metadata

title: Untitled

---

## Sprint 4 retrospective

This sprint, as it is our last one, we decided to have a little fun and do our sprint retrospective Mario Kart style. 🚗

### Which bananas did we slip on? 🍌 

 - Not paying attention when other elements had already been responsible for a review.
 - We weren't able to completely fulfill the goal of considering the end of the sprint as Tuesday, however, everything was successfully implemented and was just waiting for code reviews.
 - Some members not communicating with the team.
 - Not paying enough attention to merge conflicts that should be resolved before opening a PR.
 

### What boost gave us an edge? ⭐️
 
 - Mid sprint organization meeting.
 - Workload was nicely divided among team members.
 - Constant notice of the other members about the development status of our tasks and availability.
 - Developed our tasks earlier.


### What’s an upcoming shortcut we could take advantage of? 🚪

 Escrevam aqui coisas que melhorariam no futuro
 
 - Make better use of the knowledge of each element in the areas that feel most comfortable and share it with the other elements.
 - Better distribute code reviewing workload among the team members.
 - Better comunicate with other members of the team that were working in the same files, in order to make the merge easier and not lose any work done.

