Sprint 1

What We Should Keep Doing:

• Research and Learning Culture: Maintaining a strong focus on research and learning is crucial. The team should continue to carefully read documents, hold productive meetings with professors and teacher assistants, and actively engage in the learning process.
• Equitable Task Distribution: The team should uphold the practice of distributing tasks fairly among its members. This approach ensures that workloads remain balanced and promotes collaborative efforts.
• Effective Task Division: The successful division of tasks related to the code should remain a consistent practice. Assigning team members to different aspects of the project leads to efficient contributions from everyone.
• Streamlined Decision-Making: Continue with the efficient decision-making process that prevents overthinking and fosters quick problem-solving, ultimately avoiding bottlenecks.

What We Should Start Doing:

• Using Writing Tools: The team should consider incorporating tools that assist in verifying writing quality. This will help identify and rectify spelling and grammatical errors, enhancing the clarity of documentation and communication.
• Proactive Work Approach: Embrace a proactive work approach by engaging in tasks throughout the sprint. This prevents work from accumulating and ensures a steady workflow.
• Attention to Class-to-Class Schedule: Paying closer attention to the class-to-class schedule is advisable. This practice contributes to better organization and task management.

What We Should Stop Doing:

• Writing Directly in GitHub Wiki: Discontinue the practice of writing directly in the GitHub Wiki. While there are benefits, exploring alternative writing tools with assistance features is recommended.
• Last-Minute Sprint Work: Avoid leaving tasks to the last weeks of the sprint. Consistent engagement throughout the sprint period prevents rushed, last-minute efforts.
• Unfulfilled Commitments: Ensure that commitments made align with actual actions. Avoid making commitments that cannot be fulfilled, promoting transparency and accountability within the team.

Sprint 2

There was confusion during the retrospective of the second sprint, and that's why we didn't conduct it. However, we used it as an exercise to put into practice what we've been learning.

What We Should Keep Doing:

Regarding teamwork, the use of agile methodologies has been strongly implemented throughout our development. There is excellent communication, ensuring the project's implementation progresses correctly.

On the code side, in the previous retrospective, we mentioned that we were going to stop doing last-minute work, something we improved a bit in this sprint, but there is still room for growth. We need to maintain and increase discipline when performing our tasks.

What We Should Start Doing:

Reviewing the commits made by other team members. On GitHub, you can see the commit history of other team members, and although each person has their specific requirements, it would be good to know what others are working on to get a general sense of how the project is progressing and how our colleagues are doing.

On the code side, we need to increase the number of recommendations provided by the artificial intelligence model, which involves implementing a more up-to-date version of it.

What We Should Stop Doing:

During the weekly meetings, we are not providing as important information at the moment of the meeting itself. Instead, everyone delves deeper into their issues and achievements afterward. It would be good to plan better what we are going to say before the weekly meeting so that others have the opportunity to understand how their colleagues are doing and share their own status.

Sprint 3

What We Should Keep Doing:

We have improved in terms of discipline. In the last retrospective, we mentioned that this was an aspect to consider, and in this sprint, we managed it quite well.

On the code side, in the previous retrospective, we said we were going to stop doing last-minute work, something we improved a bit in this sprint, but there is still room for improvement. We must continue to maintain discipline when performing our activities.

We are supporting each other; if someone has more knowledge in something because they were interested and delved into it, even if someone else needs to complete the requirement, they ask for help from another person to assist with the part they are not so good at. Collaborative work has greatly helped us in developing this sprint.

What We Should Start Doing:

A better understanding of the GitHub platform because we have been experiencing issues with gitignore and our API keys are frequently blocked.

Also, every time someone pushes and pulls, there are several incidents, and we have to resolve them with merges, and sometimes it's not clear what the other person did. So, it would be good to leave comments where something is not easily understandable.

What We Should Stop Doing:

Making commits without valuable information. Sometimes, someone makes a commitment by saying "issue fixed," and that doesn't provide much information about what was wrong or what was fixed.

Sprint 4

What We Should Keep Doing:

This was the last sprint but we have learned a lot of useful things to apply in other projects like the use of Git and GitHub to manage versions, develop an app using Django, requirements engineering, documentation, web app deployment, and multiple other important points to do a good project.

What We Should Start Doing:

In this sprint, we started communicating more. Previously, we only discussed key project matters, neglecting important details that could make a difference. Deep on how the deployment platform for web applications works, and its virtual machines. Learn how to do testing proofs on software. Expand the project scope.

What We Should Stop Doing:

We have mentioned it on numerous occasions, but it is difficult to apply due to lack of custom and nevertheless it is very important to keep in mind. Sometimes when we have problems with files due to version management, such as those that contain cache memory, we delete them because we do not know how to handle these types of errors and we simply pull to obtain the content that someone else was developing and that worked for them. On top of that, the comments we make when executing a commit are not the best.

Regarding the scheduling of the project, there were several requirements that we were missing, due to complexity and organizational issues, since although we did what we had to do in previous sprints, perhaps by implementing better development techniques we would have been able to conclude with more features.