Difference between revisions of "Rob's guide to effective retrospectives"
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
===Be well prepared=== | ===Be well prepared=== | ||
| + | Not much to say here as it's quite obvious - make sure you've chosen a retrospectisve plan and have all the materials you need | ||
===Facilitation is a skill=== | ===Facilitation is a skill=== | ||
| Line 13: | Line 14: | ||
===Get someone outside the team to facilitate=== | ===Get someone outside the team to facilitate=== | ||
| − | This is a great technique to avoid the risk of biased facilitators (face it, we're all biased whether we believe it or not!) and | + | Really easy to do if you have more than one software team - ask for someone from the other team to facilitate your retrospective and when it's their turn return the favour. This is a great technique to avoid the risk of biased facilitators (face it, we're all biased whether we believe it or not!) and even better has the wonderful side-effect of being a great way to cross-pollinate ideas between teams. |
===Achievable actions=== | ===Achievable actions=== | ||
===Start each retrospective by going through the actions from the previous one=== | ===Start each retrospective by going through the actions from the previous one=== | ||
Revision as of 04:52, 10 March 2013
Be well prepared
Not much to say here as it's quite obvious - make sure you've chosen a retrospectisve plan and have all the materials you need
Facilitation is a skill
Rotate the facilitator role
A big smell I regularly see and hear about is it being one person's job (usually a scrum master or project manager) to facilitate the team's retrospectives. When this is the case you will often find a general lack of engagement or enthusiasm for them from the rest of the team. It may be one person's job to make sure they happen and everyone turns up, that does not and should not mean they also have to run every retrospective as well.
Instead try and get everyone to take turns facilitating. Not only does this ensure no one feels they're always being driven by one person's agenda, there are many other side benefits:
- Learning how to facilitate is great for developing communication skills and generally how to have effective meetings.
- The burden of planning retrospectives is shared across multiple people.
- Retrospectives are less likely to become dull or repetitive.
Get someone outside the team to facilitate
Really easy to do if you have more than one software team - ask for someone from the other team to facilitate your retrospective and when it's their turn return the favour. This is a great technique to avoid the risk of biased facilitators (face it, we're all biased whether we believe it or not!) and even better has the wonderful side-effect of being a great way to cross-pollinate ideas between teams.