Making Sprint Retrospective Meaningful
Sprint Retrospective has become predictable!
Do this if you are struggling with the same issues in your retrospective -
1. Do a root-cause analysis for all the recurring issues
2. Clearly identify ones which are beyond the influence of the scrum team and which are within the influence of scrum team. Key is to manage both separately -
2.1 Causes within the influence of the scrum team
2.1.1 Agree with team which are the top 2-3 issues that the team wants to focus on first.
2.1.2 Create an action plan, define interim stages, don't try to make it perfect in one go.
2.1.3 Seek volunteer(s) (1-2 members) from the team who would own the action plan
2.1.4 Refer the steps during the sprint to reinforce the change
2.1.5 Review the progress in next retro
2.1.6 Repeat
2.2 Causes outside the influence of the scrum team (Systemic issues)
2.2.1 Conduct retrospective playback with the Execs /sponsors and other key decision makers
2.2.2 Walk them thru the issues along with the impact on the team deliverables. Call out possible recommendations/solutions
2.2.3 Agree with them on top 2-3 issues that should be worked on priority
2.2.4 Create an action plan, define interim stages, don't try to make it perfect in one go.
2.2.5 Assign owners.
2.2.6 Follow up during the sprint.
2.2.7 Communicate to the Scrum team on the updates from this retrospective
2.2.8 Repeat
Now when these issues are highlighted in future retros, you can provide an update on progress made by Execs/sponsors.
Note: Not everything will be resolved within a few sprints specially the systemic issues. Key is to be persistent with your communication and transparent with the sponsors / execs and your team