Skip to content

Sprint Retrospective

Josua-Louw edited this page Aug 17, 2026 · 10 revisions

Sprint 1

What worked well? What could be improved? What will we commit to doing in the next sprint?
The 2-week sprint worked well because it gave us enough time to develop features properly. Regular stand-ups also helped us track progress and backlog commitments effectively. Frontend and backend integration could be improved by using better tools or techniques. More code comments would also make the codebase easier to understand. We will focus on improving and securing the authentication system (register and login, and routing from the frontend side) and work on the next three highest-priority use cases.

Sprint 2

What worked well? What could be improved? What will we commit to doing in the next sprint?
Having a list of things to do for the sprint written out on the sprint wiki helped to keep focused on what we need to get done. Work progress was slow since everyone is getting ready for exams. We can improve on just focusing on smaller tasks instead of trying to tackle big tasks. In the next sprint we will focus on completing what could not be completed this sprint and start adding services for the new features for future sprints.

Sprint 3

What worked well? What could be improved? What will we commit to doing in the next sprint?
Focusing on completing use cases in this sprint worked well to complete the services that are in development. We can improve on communication to keep everyone updated on each area that each team member is working on to be able to track team progress on the system. In the next sprint we will be taking more of a break and work slowly on current features in development.

Sprint 4

What worked well? What could be improved? What will we commit to doing in the next sprint?
Working slowly while on break worked well to keep some progress on our system going. We can begin improving our velocity now by spending more time on the project in future sprints. We will commit to integrating the system as a whole in the next two sprints making sure that the system is ready for demo 2.

Sprint 5

What worked well? What could be improved? What will we commit to doing in the next sprint?
Began integrating and connected all the services with the events using Rabbit Integration communication can improve. Testing policy can be improved. We will begin working more together when back from vacation which will improve integration velocity. Getting everything connected.

Sprint 6

What worked well? What could be improved? What will we commit to doing in the next sprint?
Having a practice demo with our clients helped us understand the project in a more business oriented aspect. Setting up proper plans on what we need to complete on our project board can help us. We will set up a good list of issues on our project board to commit to complete at the end of the sprint.
We also used a check list to make sure we had the core features ready for demo 2.

Sprint 7

What worked well? What could be improved? What will we commit to doing in the next sprint?
Setting up proper issues that we planned to get done by the end of the sprint increased our productivity. Sticking to the issues and actually completing all that we planned can be improved. Seeing what issues are really needed for the sprint.

Sprint 8

What worked well? What could be improved? What will we commit to doing in the next sprint?

Clone this wiki locally