A meta-retrospective is an excellent exercise to foster collaboration within the extended team, create a shared understanding of the big picture, and immediately create valuable action-items. It comprises of the team members of one or several product teams—or representative from those—and stakeholders. Participants from the stakeholder side are people from the business as well as customers.
Meta-retrospectives are useful both as a regular event, say once a quarter, or after achieving a particular milestone, for example, a specific release of the product. Read more on how to organize such a meta-retrospective.
Are you—as a scrum master or agile coach—experiencing more communication kerfuffles with “your” team? Is its speed of improvement stalling? Are you under the impression that the team is slipping back into old habits and patterns? Maybe, it is time to run a reverse retrospective where your share your observations with the team.
Learn how to run a reverse retrospective to realign with your scrum team.
After rebuilding an existing application on a new tech stack within time and under budget our team had an overall retrospective with stakeholders this week to identify systemic issues. We found more than 20 problems in total and derived eight detailed recommendation the organization will need to address when moving forward to the next level of agile product creation.
Read on and learn how we achieved this result in under two hours with an overall retrospective attended by 16 people.
How to prevent retrospective boredom? One way to achieve that is never to repeat the same combination of retrospective exercises twice.
Avoiding repetitions might sound like much work for a single team. However, if your product delivery organization comprises of more than one Scrum team, I can highly recommend creating a retrospective exercises repository as it improves the quality of the retrospectives and saves much time if you share the retrospective exercises with your fellow scrum masters.
Learn how to build such a retrospective exercises repository.
What ceremony could better embody scrum’s ‘inspect and adapt’ mantra than the sprint retrospective? I assume all agile peers agree that even the simplest retrospective—if only held regularly—is far more useful than having a fancy one once in a while, or in the worst case having none at all. And there is always room for improvement. Learn more about 21 common sprint retrospective anti-patterns.
This website uses cookies, which may include third party cookies, to improve your browsing experience and deliver personalized marketing content. To find out more, including how to disable the cookies, read our Cookie Policy. By continuing to browse this website, you agree to our use of cookies.Got it!
