There are some things a Scrummaster can do on her own initiative like updating reports or getting the right information up on the walls. However, most of the really sticky impediments end up being things she just can't do on her own because they require skills she doesn't have, approvals from outside the team, or participation from the whole team. The important point is that just because she can't do them herself does not mean she isn't responsible. The SM role is figuring that stuff out and seeing that it gets done.
On Monday, October 21, 2013, Vikrama Dhiman wrote:
Yes, there is an impediment which Scrum Master should not try and solve. The impediment is 'what she thinks should be solved but the team does not think so'. As a thumb rule, she can't solve an impediment which the team does not bring up. If you are strongly convinced, discuss with the team, debate with the team but don't go about doing anything till the team brings it up.
Agree with Adam, I'm not sure there is some kind of a "rule" about which impediment the SM has to manage. If he can't unblock an impediment by himself, he should feel free to ask for help
On Friday, October 18, 2013 1:41 AM, Adam Sroka <adam.sroka@...> wrote:
All impediments are owned by the SM. However, as often as not he will have to get help from others to resolve them.
The point is to not unnecessarily burden the team with these things. Let the SM chase them down and tilt at windmills while the team focuses on valuable work.
On Wednesday, October 16, 2013, Sudhir Rana wrote:
Interested to know what impediments does not fall under Scrum Master's realm to resolve.
Please provide name/example of such impediments.