Effective Retrospectives & Reviews: A CSP’s perspective on continuously improving both the process and the product.
Are your team’s retrospectives really worth the effort? Do the problems you identify actually get solved? If not, your team might need some help learning how to use retrospectives to continuously improve. This article illustrates how Scrum teams can continuously improve by using a combination of their definition of done, working agreements, and the product backlog.
Retrospectives are a time to reflect on what has happened, what your team wants to happen in the future, and what steps you can take to correct course accordingly. Unfortunately, the actions that come out of retrospectives often are either too focused on the present or are so abstract as to be unattainable. Discover one technique for linking actions to goals.
One goal of self-empowered teams is to have the team find, own, and fix their problelms by themselves. Applying gap analysis to team practices enables teams to visualize areas of concern and come up with their own action plan to address the shortcomings.
What's the secret ingredient missing from most sprint reviews? The user stories and use cases you probably discarded may be the greatest story never told.
For some teams, retrospectives start to lose their punch after a few sprints have gone by. If your retrospectives feel a little stale, don't abandon them. Freshen them up instead. Seven things you can do to inject new energy.