In Scrum framework, retrospective is the last event of each sprint and has also been one of the most rushed events in our experience. This has meant that the event has failed in helping the team, consequently failing in its purpose and has thus been considered mostly as an helpless event. There could be broadly three reasons why this happens : The team is using the same technique all the time and they are already bored enough. The team is using multiple new techniques where the ‘fun’ gets more important than retrospection. They may failed to improve on identified pointers and think retro is primarily a routine instead of a meaningful event. To counter this, below is one format that we suggest you try for your retrospective.
Read More →