How we canceled retrospectives /Wrike company blog /Habr
Once, for our team, retrospectives stopped working.
On retro, we discussed eternal topics: we need to better decompose tasks, we need to better evaluate tasks, we must stop carrying debts between sprints, etc. Someone coded in parallel, someone answered messages, someone just stuck to the phone. Sounds familiar?
These were my first sprints as a scrum master, and I felt the team had no confidence in retrospectives. Yes, and there is no need either - there are complaints about the “scrum-day" clogged with rallies. And when to work?
I decided something terrible for the scrum master: I suggested that the team cancel the retrospectives - and this is what came of it.
I'm trying to do a boring retrospective
Enter , you are welcome.
Are retrospectives useful for your team now?
Yes, I regularly see
No, nothing changes
Unsubscribe in the comments
No one has voted yet. There are no abstentions.
It may be interesting