How about we cancel this sprint retrospective, we do not have time!!!
For your own sake, I hope you never hear such words coming from your team’s scrum master.
Though it might be tempting, here are some reasons why you should never even attempt to cancel a sprint retro:
- ?The idea of just proposing to your team skipping the next sprint retro, even if you get there support on that, is a recipe for disaster. Once done, you will never be able to group them back again in another retrospective. Giving the impression that this scrum event is not important will make your team take it forever for granted. Every scrum event is equally as important. Once you start questioning this notion, the team will start questioning each and every event which will make them lose confidence in the whole process.
- One of the basic principles of agile is continuous improvement. There are different scrum events that might contribute to the improvement of the product, but not many focus on the process. A sprint retro’s main purpose is to identify how we can improve our processes, methods, tools and procedures to better perform as a team in the next sprint. In other words, missing this event is missing on the core idea of agile.
- ?The sprint retro is an opportunity for the team to let out some steam, period. It gives the team members the sense that they are heard and that their opinion matters. It is pure empowerment. Imagine yourself working hard all through the sprint, identifying ways to better enhance the efficiency of the team, yet not given the opportunity to share and apply them. The result is one: Demotivation. And from there it is a snowball effect across the rest of the group.
Your Job as a Scrum Master is to find the value in every scrum event and spread it among your team and organization. Never question the event itself but challenge how it is being applied.
Increase your team's feedback thanks to TeamMood.com
1 年Funny picture!