Our Product/Tech team has been transitioning towards Agile project management in the last year or so, and we hold daily standups, weekly planning meetings and biweekly retrospective meetings. We also use a Kanban board.
As the team's Scrum Master, I've been trying to make the retrospectives more actionable, as some team members have pointed out that we often end up discussing the same issues that don't get solved. I'm worried about the impact of this on team members' morale and desire to participate, so I've tried several approaches to make things more concrete, such as 15% solutions, and limiting the number of action items that we commit to doing to the bare minimum (i.e. 1-2). We've also been adding those items to our Sprint board to give them visibility. This has helped quite a bit with ad hoc, concrete action items.
What I'm struggling with right now is what I call "intangible" action items, i.e. items that are linked to habits or behavioural change and/or are recurring in nature. Here are some examples:
- When pulling a PBI into Building, take some time to think about how it will be reviewed so that it doesn't create bottlenecks in the Ready to Review column
- When estimating roadmap items, multiply by 2 so that we provide more realistic estimates
- During the scoping phase, map out dependencies so that we can plan the work better
I could of course put all of these in a document and share it, but it would probably end up on the proverbial shelf and never get implemented. From my experience, even when these solutions emerge from the team to tackle very real problems, because of their intangible nature, they quickly fall by the wayside when things get busy. Hence my question: How do you make sure those action items get implemented? How do you keep track of them?