Add an Impediment List as an artifact
The SM must work on impediments, helping the team become more productive and more happy, etc. The SM needs a list of the top X (20?) things that he/she needs to work on.
This will lead to greater focus on removing impediments, and greater success.
How can you build a product without a Prod Bklog (list)? How can you have continuous improvement without an Impediment List?
Everything that can be improved (in any way) might go on the list. (There are many types of impediments.) In theory that could be lots of things (just as the PB could also be endless)...in practice we only track the Top X things.
The goal: more success with Scrum. How? By prioritizing the impediments better, and more actively seeing and fixing them.
Perhaps we should add that the whole team must prioritize the impediments (business-side ones vs tech ones vs org ones, etc, etc.).
1 commentComments are closed
Joseph Little commented
The impediment list is an action list for the SM to get right people (including himself) to get it done. As always, the usual improvement expected from each one is an increase in velocity, but it could be seen as increased happiness, higher quality, more business value, or in some other way.
The key principle is that the SM get the most important (small piece) impediment mitigated first. (Single piece continuous flow.)
It's hard to prioritize a list if you don't have a list.