If the retrospectives are one of the main improvement tools for Agile teams, they can also be the subjects of improvement. In this article, Tom Monico explains how his team has adopted the starfish model to create a better retrospectives process where feedback is produced in real-time and not only at the end of a Scrum sprint. Author: Tom Monico, https://www.goreflect.com/ Many have embraced the retrospective while others, possibly most, have a more casual attitude towards the value of the retrospective. Personally, I was somewhere in the middle until my teammates and I developed a better way to learn from the past. We were performing very well. We routinely met our commitments and the business was happy. We held a retrospective at the end of each sprint going around the room asking each team member to share something that worked or didn’t work well. It was a very uncomfortable process for everyone. Since we were doing so well, we questioned the value of the retrospective and considered having the retrospective every other sprint, maybe even less often. Luckily, our desire to have the retro less frequently was short lived. We realized that even though we were doing well, we still needed to challenge ourselves to improve every sprint. If we didn’t, we wouldn’t grow as a team and we’d eventually become complacent about improvement. We needed something better. We needed a better retrospective. Retrospective starfish board. Source: http://www.funretrospectives.com/ We wanted to make the retrospective as objective as possible so we [...]
Previous Topic
