Difference between revisions of "Common ailments & cures"
|Line 96:||Line 96:|
*Have a Devil's Advocate
*Have a Devil's Advocate
*Try De Bono's [[
*Try De Bono's [[Thinking Hats Retrospective]]
Revision as of 12:13, 25 February 2013
A collection of common problems which occur with retrospectives and suggestions how to resolve them.
If you have an ailment that is not covered please add it at the bottom and hopefully someone will have an answer for you.
Ailment: Actions not captured / No obvious record or review of previous retrospective findings
- Review the actions from the previous retrospectives at the beginning of each retrospective.
- Capture/Document actions & follow up by Scrum Master
- Maintain backlog
- Focus on last sprint only
- Make someone responsible and accountable for each action.
- Put the actions somewhere visible in the team space for example to create team building spirit
- Reduce actions to a manageable number
Ailment: Too many actions
- Apply velocity to actions, track progress and only take on what velocity dictates
- Try Plan of Action Retrospective Plan
- Only choose one action
Ailment: Unjustified actions
- Use root cause analysis
- Ensure actions are suggestions from the team and prioritised by them.
- Suggests Biased chair - see cures for that symptom
Ailment: Not having the right people in the retrospective
- Invite people early
- Pick a time that suits everyone
- Have separate retrospectives for tech team & wider team
Ailment: Biased chair / Agenda hijacking
- Feedback to chair and escalate if necessary
- Rotate chair
- Coach chair on “Agile” principles
- Let team choose an un-biased chair
Ailment: Lack of preparation / Forgetting what’s happened
- Compensate in the meeting by having a good time line (Ed. help everyone remember what happened?)
- Prepare - personal/team log
- Remind participants to think of good and bad points
- Reminder before the meeting
Ailment: People not speaking up/shy
- Chair/facilitator needs to create the right environment
- Suggest box/amnesty
- Try different games which are more suited to retiring types
Ailment: Retrospective actions and tips not shared with other teams
- Rotating facilitators
- Shared retrospective blog
- Retrospective “lurking”
- Cross team collaboration needed
Ailment: People taking things personally
- Refer to The Prime Directive
Ailment: Voting system may result in valid issues not being addressed
- Non-addressed issues get rolled over (& keep votes?)
- Themed retrospectives
- Encourage team to get on well so they empathise more with issues affecting minority
- Vary the retro format (e.g. no voting)
Ailment: Suffering from 'Group Think'
- Have a Devil's Advocate
- Try De Bono's 6 Thinking Hats Retrospective
Ailment: Lack of engagement
- Try new plans or tips such as the ones on this wiki!
Ailment: Too much focus on negatives
- Try the Appreciative Retrospective Plan