Difference between revisions of "Common ailments & cures"
(Created page with "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 an...") |
Ben Linders (talk | contribs) |
||
(10 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | A collection of common problems which occur with retrospectives and suggestions how to resolve them. | + | A collection of common problems which occur with retrospectives and suggestions how to resolve them. Generated by running a [[Retrospective Surgery]]. |
If you have an ailment that is not covered please add it at the bottom and hopefully someone will have an answer for you. | If you have an ailment that is not covered please add it at the bottom and hopefully someone will have an answer for you. | ||
Line 6: | Line 6: | ||
'''Ailment: Actions not captured / No obvious record or review of previous retrospective findings''' | '''Ailment: Actions not captured / No obvious record or review of previous retrospective findings''' | ||
+ | |||
'''Cures:''' | '''Cures:''' | ||
*Review the actions from the previous retrospectives at the beginning of each retrospective. | *Review the actions from the previous retrospectives at the beginning of each retrospective. | ||
*Capture/Document actions & follow up by Scrum Master | *Capture/Document actions & follow up by Scrum Master | ||
− | *Maintain backlog | + | *Maintain backlog and have it visible for everybody in the team (e.g. on the Task Board) |
*Focus on last sprint only | *Focus on last sprint only | ||
*Make someone responsible and accountable for each action. | *Make someone responsible and accountable for each action. | ||
*Put the actions somewhere visible in the team space for example to create team building spirit | *Put the actions somewhere visible in the team space for example to create team building spirit | ||
*Reduce actions to a manageable number | *Reduce actions to a manageable number | ||
+ | *More suggestions in [http://www.infoq.com/news/2014/02/retrospective-actions-done Having Actions Done from Retrospectives] | ||
---- | ---- | ||
Line 21: | Line 23: | ||
'''Cures:''' | '''Cures:''' | ||
*Apply velocity to actions, track progress and only take on what velocity dictates | *Apply velocity to actions, track progress and only take on what velocity dictates | ||
− | *Try Plan | + | *Try [[Plan of Action]] Retrospective Plan |
− | * | + | *Focus on the [https://www.benlinders.com/2014/retrospective-exercise-vital-few-actions/ vital few actions], only choose one action |
---- | ---- | ||
Line 28: | Line 30: | ||
'''Cures:''' | '''Cures:''' | ||
− | *Use root cause analysis | + | *Use [https://www.benlinders.com/2013/getting-to-the-root-causes-of-problems-in-a-retrospective/ root cause analysis] |
*Ensure actions are suggestions from the team and prioritised by them. | *Ensure actions are suggestions from the team and prioritised by them. | ||
*Suggests Biased chair - see cures for that symptom | *Suggests Biased chair - see cures for that symptom | ||
Line 57: | Line 59: | ||
*Remind participants to think of good and bad points | *Remind participants to think of good and bad points | ||
*Reminder before the meeting | *Reminder before the meeting | ||
+ | *Use Retrospective Exercises from [https://www.benlinders.com/exercises/ Retrospective Exercises Toolbox] or [http://www.plans-for-retrospectives.com/ Retr-O-Mat] | ||
---- | ---- | ||
Line 74: | Line 77: | ||
*Retrospective “lurking” | *Retrospective “lurking” | ||
*Cross team collaboration needed | *Cross team collaboration needed | ||
+ | *Do a [http://www.benlinders.com/2013/improving-collaboration-in-agile-projects-with-the-retrospective-of-retrospectives/ Retrospective of Retrospectives] | ||
+ | |||
---- | ---- | ||
Line 79: | Line 84: | ||
'''Cures:''' | '''Cures:''' | ||
− | *Refer to The Prime Directive | + | *Refer to [[The Prime Directive]] |
---- | ---- | ||
Line 94: | Line 99: | ||
'''Cures:''' | '''Cures:''' | ||
− | *Have a Devil's Advocate | + | *Have a [http://www.benlinders.com/2011/devil%E2%80%99s-or-angel%E2%80%99s-advocate-which-role-do-you-prefer/ Devil's Advocate or Angel's Advocate] |
− | *Try De Bono's | + | *Try De Bono's [[6 Thinking Hats Retrospective]] |
---- | ---- | ||
Line 107: | Line 112: | ||
'''Cures:''' | '''Cures:''' | ||
− | * Try the Appreciative Retrospective Plan | + | * Try the [[Appreciative Retrospective]] Plan or a [http://www.benlinders.com/2013/using-solution-focused-in-a-strengths-based-retrospective/ Strenghts based Retrospective] |
Revision as of 02:03, 26 December 2016
A collection of common problems which occur with retrospectives and suggestions how to resolve them. Generated by running a Retrospective Surgery.
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
Cures:
- Review the actions from the previous retrospectives at the beginning of each retrospective.
- Capture/Document actions & follow up by Scrum Master
- Maintain backlog and have it visible for everybody in the team (e.g. on the Task Board)
- 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
- More suggestions in Having Actions Done from Retrospectives
Ailment: Too many actions
Cures:
- Apply velocity to actions, track progress and only take on what velocity dictates
- Try Plan of Action Retrospective Plan
- Focus on the vital few actions, only choose one action
Ailment: Unjustified actions
Cures:
- 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
Cures:
- Invite people early
- Pick a time that suits everyone
- Have separate retrospectives for tech team & wider team
Ailment: Biased chair / Agenda hijacking
Cures:
- 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
Cures:
- 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
- Use Retrospective Exercises from Retrospective Exercises Toolbox or Retr-O-Mat
Ailment: People not speaking up/shy
Cures:
- 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
Cures:
- Rotating facilitators
- Shared retrospective blog
- Retrospective “lurking”
- Cross team collaboration needed
- Do a Retrospective of Retrospectives
Ailment: People taking things personally
Cures:
- Refer to The Prime Directive
Ailment: Voting system may result in valid issues not being addressed
Cures:
- 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'
Cures:
- Have a Devil's Advocate or Angel's Advocate
- Try De Bono's 6 Thinking Hats Retrospective
Ailment: Lack of engagement
Cures:
- Try new plans or tips such as the ones on this wiki!
Ailment: Too much focus on negatives
Cures:
- Try the Appreciative Retrospective Plan or a Strenghts based Retrospective