A cricket match is divided into fixed periods of play called innings, similar to Agile delivery cycles called sprints. The aim in both cases is for the team to score as many runs as possible in an innings/sprint through coordinated collaboration, adjusting on the fly to situational demands. While the match duration and overs per innings are pre-defined in cricket, the number of sprints and sprint duration in Agile have some flexibility based on project scale and priority. However, the focus is consistent - orchestrating the team to maximize outcome delivery within the current time period before a reset.
Just as cricket teams conduct sprint reviews analyzing performance at end of an innings, Agile teams participate in retrospectives assessing what worked and what needs improvement in the sprint that just concluded. These then feed into planning for the next innings/sprint in both cases rather than waiting until end of match/project.
The iterative nature of innings/sprints encourages course corrections without major deviation from longer-term match/release plans. Staying relentlessly focused on immediate priority tasks while upholding overarching strategies is crucial to success in both cricket and Agile settings with constantly moving finish lines.