The urge to create actions put too much pressure and hectic in the retrospective
How they dealt with it:
Have a complete session dedicated to learning each person’s feelings about the topic
PM did not take the need of his team serious, even after serious intervention
How they dealt with it:
Role descriptions
Work descriptions
See overloads
Give more time to discuss
Escalate to management
Someone who is not interested in the retrospective and shows it with non verbal communication
How they dealt with it:
Suggestions
ESVP exercise (See Agile Retrospectives book)
Halt the retrospective (don’t just simply run with it)
People who were not interested in the purpose 'sucked' energy from the group
How they dealt with it:
Attendance of meetings voluntary
People who get stuck on complaints and don't want to go forward
How they dealt with it:
Blank
Suggestions
Two separate action plans (one for the team and one for others)
Prioritise “what can we do ask others to do” and list out separately “what can we do”
Focus on group responsibility “what can we do?”
Link action short term to long term goal
Remove blockers
Another retro involving a wider group
Heartbeat Retro "No time for discussion"
How they dealt with it:
Refocussed onto agreed outcome and agenda and and confirmed. Consequence did not have time for depth in this session with action for further discussion. It was unsatisfactory ... never had depth.
Suggestions
Create meeting just about the topic
Followed up with the person who wasn’t happy with topics
Extend with more time
Create an additional action plan
2 Retrospectives in one day "Quart in a pint pot" Run out of time
How they dealt with it:
Running out of time in the afternoon. Team only just opening up to talk about issues deferred action planning to the next day (result is dissatisfied)
Suggestions
Checklist (pre contract)
Ensure all participants are there for the entire retrospective (as the group shifted throughout the day)
