In your current or previous project, how did you handle retrospectives and plan for the next sprint when there were issues present?

During my last project, we used a structured retrospective format each sprint. First, the team gathered to review what went well and what didn’t. We used the "Start, Stop, Continue" method to surface issues. For example, we discovered that our automated tests were flaky, causing delays. We documented this as an action item and assigned a developer to investigate. Next, we prioritized action items based on impact and effort, and incorporated them into the next sprint backlog. We also updated our Definition of Done to include test stability checks. By the end of the sprint, we had a clear plan: address flaky tests, improve test coverage, and refine our CI pipeline. This iterative approach ensured that problems were addressed promptly and that the sprint plan reflected the team’s learning, leading to a 15% reduction in cycle time over the next three sprints.