What I like to do to keep retrospectives energized is to keep them really short: I set a timer for two minutes to write stickies with feedback, and then 15 minutes for discussion. Action points get written down, and it's no problem if we don't handle all stickies, since we can have these retrospectives really often.
To be honest, I haven't consciously thought about that. When problems keep popping up, I try the "what's the simplest, actionable thing we can do now"-approach. This usually solves most pressing issues. I am aware I may be missing something larger here. We may not always be able to solve larger issues (they only keep popping up if we can't change them), but we can improve our own ways of coping with them. And yes, that may be a local optimization.
Hi Angelo, Great idea! You can do these even twice a week. A question: how do you deal with issues that are symptomatic but for which the underlying issue remains uncovered? How do you address these? Rini
@GroetenUitDelft, where did you get your team shirts from? I like the idea for a scrum team and would like to implement it for my team. Hopefully you will see this message.
Having retrospective over a evening drink is the best everything gets out and opened up.
What I like to do to keep retrospectives energized is to keep them really short: I set a timer for two minutes to write stickies with feedback, and then 15 minutes for discussion. Action points get written down, and it's no problem if we don't handle all stickies, since we can have these retrospectives really often.
To be honest, I haven't consciously thought about that.
When problems keep popping up, I try the "what's the simplest, actionable thing we can do now"-approach. This usually solves most pressing issues.
I am aware I may be missing something larger here.
We may not always be able to solve larger issues (they only keep popping up if we can't change them), but we can improve our own ways of coping with them. And yes, that may be a local optimization.
Hi Angelo,
Great idea! You can do these even twice a week. A question: how do you deal with issues that are symptomatic but for which the underlying issue remains uncovered? How do you address these?
Rini
@GroetenUitDelft, where did you get your team shirts from? I like the idea for a scrum team and would like to implement it for my team.
Hopefully you will see this message.