Skip to content

Sprint 1 Retrospective Report

Jump to bottom
mahsa.ama edited this page Dec 10, 2021 · 1 revision

Date: 11/20/2021 --- Time: 16:30 - 17:30

After the sprint review session, we held a retrospective meeting with all team members present where we discussed the things we believe went well during this sprint and also areas where we need to change our approach in the next sprints.

We used the method discussed in this link as we wanted an action focused retrospective. Different parts of the project were mentioned and everyone voted on how they felt about each one.

What we believe went well:

  • Daily Scrums: Daily scrums were very helpful and kept us motivated and working at an even flow throughout the sprint.

  • Overall cooperation: The team members got along very well and the tasks were completed efficiently in a very cooperative manner, whenever a team member faced a problem in doing their task, others were willing to help them out as soon as possible and keep the work flowing.

  • Availability: Everyone was accessible at all times and ready to fix any bugs that were occasionally found and also ready to help out other team members.

  • Final result: We were able to deliver all the promised features of the MVP in the sprint time-frame.

What we need to improve:

  • Unit tests: During this sprint, we did not start writing unit tests until almost all of the work was done. In the next sprints, we will write tests from the beginning so they can be more helpful and we can have test-driven development.

  • Setting up CI/CD: Setting up CI/CD can be added to the backlog for the next sprints as an improvement task. This way merge requests can be automatically tested.

  • Comments in the code: From now on we should remember to explain what each piece of code does after it's written, so we don't have to go back and re-think what it did later on. It will be more efficient and clearer to understand for everyone that way.

  • Commit messages: We should try to write more explanatory commit messages.

  • Reading the sprint instructions: In the next sprints, we should read the instructions more carefully from the beginning to avoid wasting time on misunderstandings or missing out on important details that should be taken into account.

  • Splitting the tasks: During this sprint, some of the team members were mainly focused on writing the code while others were mainly focused on documentation and planning future sprints. In the next sprints, we would like to involve everyone in every part so everyone will be more aware of the whole process.

Clone this wiki locally