This week, it was time for another retrospective, evaluating our sprints for this semester. You can also read our last retrospective here.
This time, we did our retrospective together with TaskHub. You can read their blog post about the retrospective here.
We began by noting the things we found positive, negative, confusing and not-so-good. After looking what all the other groups noted for them, we went over to drawing the consequences. That is, we discussed what we want to talk about in detail, what our thoughts about the topics are and what we want to do in the future to improve our work.
Our main takeaways were these:
- Distribute the work / tickets better: in some sprints, we had an unequal distribution across our team. This is something we should try to change in the future, although it doesn’t make sense to try to prevent this completely as we also have more or less to do for lectures etc., so it’s normal to have some change in the utilization.
- Everyone should know the basics of every part of the project, so when someone is sick or otherwise occupied, the project doesn’t come to a stop just because the other team members don’t know anything about this part.
- Don’t postpone too much work: In the last few sprints, we postponed a lot of the tickets as we had many other things to do for other lectures. We should try to set sprint goals that are actually achievable and then also try to reach those in the future.
We also learned that we have to specify our goals clearly and detailed. Even some of the above mentioned goals are maybe not detailed enough, so for the next retrospective, we know that we have to specify these better.
We hope that maybe you can also learn something from our retrospective and are looking forward to seeing you in our next post.
Have a nice week,
Betterzon