Repository navigation
Sprint Retrospectives
Jonathan Betancur edited this page Oct 21, 2023
·
3 revisions
- We must continue, and never stop improving, our performance, as it has allowed us to tackle the tasks we are committed to as a team on the project.
- We must continue to help each other on details, or resolve issues that one of us may have through good communication. Some may notice weaknesses, others may have better perspectives for one situation or another, so we need to take advantage of those differences.
- We must start focusing on the value we will give to the data within the application, in order to give value to the application.
- It has been found that tasks performed by one of the team members are not accepted in some details by the rest of the team, so it will be necessary to start doing more feedback between team members.
- We must stop not having a relatively good pace during the development of the sprint, so that in the last week we are not overwhelmed by the tasks.
- We should stop speculating too much on how to approach a problem, if we do not reach consensus on something it is good to take advantage of the possibility of a consultancy with the teacher.
- User-Centered Design: Keep focusing on user-centered design principles to enhance the user experience and make the software as intuitive as possible.
- Effective Communication: Maintain effective communication within the development team to ensure everyone is on the same page and can work cohesively.
- Feedback: Establish a formalized feedback with end-users to gather input for future updates and improvements.
- inefficiency of the time: We should stop doing some of the important things by the close finish dates, because that was stressful and sometimes the work didn´t been correctly developed