Infinity’s Sprint Retrospective template lets you analyze the latest sprint. Acknowledge success, resolve questions, and plan improvements for the next sprint.
You’ve scheduled your sprint retrospective for one hour (or three), but does that mean that you have to use the whole hour? It’s okay to end meetings early. Stay focused Your retrospective meeting should not be a social gathering. Stick to your agenda to stay focused. Create a retrospe...
Scheduling a Scrum retrospective at the end of every sprint ensures that needed changes are understood and implemented before they are lost in the rush of new work. It helps each Scrum team member to identify how they can improve the specific things they contributed to the sprint, asking: What...
Create an agenda and distribute itto your team (more on the specifics below). Don't forget to consider the discussions and feedback from yoursprint reviewand/orsprint retrospective. As part of the agenda preparation, also ensure that you’ve taken care of the necessary meeting logistics, inclu...
Sprint Review vs Sprint Retrospective Sprint Increment Review Duration of Sprint Review Sprint Review Meeting Template The sprint review is an informal meeting which the development team, the scrum master, the product owner and the stakeholders will attend. The team gives a demo on the product and...
Incorporate retrospective insights into planning During the planning phase, be sure to touch base on your most recently completed sprint to see if there’s an opportunity to incorporate anyretrospectivelearnings into your next sprint. This will help support your team and improve every sprint, which...
Learn from your mistakes and successes. All online retrospective boards are completely customizable. Features include voting, groups, tags, breakout boards.
During the retrospective, you collect feedback about people’s experiences integrating into the team, communicating code changes, or whatever else affected the process. The retrospective is intended to be a kind of debrief where everybody can learn how to work together better, regardless of the pr...
1. Perform an agile retrospective Running a retrospective is important to evaluate your team’s performance during the previous sprint and prevent similar loopholes proactively in the next ones. 2. Have a clear vision It’s true that agile planning is open to changes, but it doesn’t mean tha...
At the end of the sprint, the team often runs a sprint review and sprint retrospective to review the results and reflect on what went well and what didn't. These learnings are then applied during the next sprint planning. Sprint planning tips Preparing for an upcoming sprint doesn't require...