Learnings, inspiration, and behind-the-scenes about remote agile retrospective best-practices and tools, from our team to yours. How to close your agile retrospective meeting The work isn’t done for the facilitator when the agile retrospective meeting ends. There are some key steps you’ll wan...
Using Confluence and Jira together integrates retros into your sprint process – allowing you to document, track, and act on feedback all in one place. Best practices for running retros with Confluence and Jira Streamline retrospective creation After completing a sprint in Jira, streamline the creat...
The best thing about a retrospective is that it happens at the very last when the sprint ends. This way fresh ideas are churned out and teased out by the whole team in the next Sprint. Afterall, the real purpose of the Sprint Retrospective is to bring about a positive change in the pr...
A sprint demo should occur at the end of each sprint, before the sprint retrospective. This timing ensures the development team can present the most up-to-date work and functionality achieved during the sprint. Scheduling the demo at this point allows stakeholders and team members to review an...
Scrumis all about continuous improvement, and Sprint Retrospective is an event that solely focuses on improvements on every aspect of Sprint. Why is Sprint retrospective so important? Let's find out The dedicated time slot that just focuses on improvement. Every other hour in Sprint is concentrate...
Learn more: Scrum best practices, Sprint planning meetings.Sprint retrospective meetingsThe Sprint review or retrospective meeting occurs at the end of a sprint. This meeting is when the team demonstrates the work that they completed during the sprint. The product owner, customers, and stakeholders ...
It can be deceptively easy to refer to the past. Getting stuck on old problems, conversations, and projects can muck up the analysis of the current iteration. Stay focused on your single sprint. It’ll make the retrospective far more manageable, while also ensuring any new team members (who...
A 4 Ls retrospective should last no more than 30-60 minutes total.4 L's sprint retrospective (Click to use this template) WWW The WWW (or what went well) retrospective technique is a basic technique that focuses on the team’s strengths and weaknesses. It’s best used when your team ...
When done well, retrospectives are often the most beneficial ceremony a team practices. When done poorly, retrospectives can be wasteful and grueling to attend. Anatomy of a Healthy Sprint Retrospective Scrum says little about the internal structure of Sprint Retrospectives. Rather than prescribing how...
A sprint retrospective is a way to bring scrum teams together and plan the best ways to increase quality and effectiveness in regard to people, interactions, processes, tools, and each person’s definition of done. What is a sprint retrospective meeting?