Retrospectives, even though a valuable part of any sprint, are often disregarded and underestimated by scrum teams. Team members and the scrum masters feel that if there were no major issues during the sprint, there is really nothing to be discussed. This could not be further from the truth however and in fact goes against the constant innovation and improvement philosophy of agile. So what should you do in case your team is falling into the pattern? There are exactly three things propose to keep in mind.
- Remind the team why it is important
First and foremost, the team needs to understand the importance and value that a retrospective adds. While it is all clear when the project begins, teams often tend to devaluate retrospectives towards the middle of the project. Even though the major kinks within the team are worked out by then, there are still improvements to be made and things to be discussed. Think about it – the type of work your team is doing at each stage of the project is likely not the same and therefore does require different approach to maximize results.
Thus make sure to remind your team that as their process is changing, their approach will likely change as well. Make them understand the retrospective as a great opportunity to voice their issues, hear out others and reach a mutual understanding for going further as a unit.