ESCUELA DE CIENCIAS APLICADAS E INGENIERÍAS-Retrospective 4

What should we continue to do?

• Maintain the detailed weekly activity tracking, which has provided clarity and structure for individual and team contributions.
• Continue improving task-specific implementations such as the speech functionality and suggestions toggle, which were handled effectively.
• Preserve the commitment to deliverables, especially ensuring presentations and deployment milestones are met on time.
• Encourage active use of GitHub for documentation and deliverable organization, which has streamlined collaboration.
• Keep leveraging individual strengths to distribute work efficiently across tasks like design, AI functionality, and deployment.

What should we start doing?

• Allocate buffer time: Start planning for unexpected issues to minimize delays, as highlighted in prior weekly reports.
• Improve code review processes: Establish a clear standard for reviewing and testing before merging to the main branch.
• Adopt standardized workflows: Use consistent coding standards and branching strategies to reduce errors and conflicts.
• Refine backlog management: Begin updating the backlog as tasks are completed in real time for better visibility and planning accuracy.
• Incorporate testing practices: Develop and follow a routine for testing functionalities to ensure stability before deployment.

#What should we stop doing?

• Avoid overloading tasks: Limit the number of tasks in progress to prevent burnout and ensure high-quality output.
• Minimize context switching: Focus on one major task or feature at a time to improve efficiency and reduce rework.
• Reduce redundant meetings: Keep weekly updates concise and avoid unrelated discussions that detract from actionable planning.
• Avoid last-minute fixes: Stop leaving critical refinements, such as diagram updates or deployment tasks, to the end of the sprint.