A sample text widget

Etiam pulvinar consectetur dolor sed malesuada. Ut convallis euismod dolor nec pretium. Nunc ut tristique massa.

Nam sodales mi vitae dolor ullamcorper et vulputate enim accumsan. Morbi orci magna, tincidunt vitae molestie nec, molestie at mi. Nulla nulla lorem, suscipit in posuere in, interdum non magna.

Scrum: Organizational impediments outside the control of the team and the Scrum Master

In the Scrum team, there are a number of items that can be impediments to the working of the Scrum team. There are issues that can be related to the specific features on which work is happening, in which the specific team member or other team members can help. There can be other issues related to dependencies on other teams on which the Scrum Master can do a lot of help, working with them on their schedule, delays, negotiations, etc. The scrum master can even work of morale issues and help to resolve them. In all this, the Daily Scrum meeting ensures that all these impediments come out in the open and everyone in the team knows about these impediments (in the normal project manager led kind of project, typically it would be the leads and the Project Manager who would know about the issues and the team would not be really expected to debate or know much about most of these impediments). For all this, the Scrum Master is the primary custodian of the impediments and they are his/her responsibility. As a result, most of the impediments can be resolved with the full knowledge of the team members, and this gives them more confidence about resolving these issues and even reporting these.
However, not everything is as good as all this. There can be a number of impediments which are outside the control of the team, and even the Scrum Master cannot help resolve them even by working up the organizational ladder (for example, there may be a mandate for a certain kind of tool to be used in the organization, or a certain kind of policy), and these impediments are affecting the team. But the Scrum Master would not really have the kind of power to make the required changes in this area. But, you need to ensure that the team can see that there are some work happening in this area, or atleast that some of these items are under consideration. Even the Scrum Masters have a need for the same. But what is to be done ?
One good way for doing this is to raise this within the organization to the senior managers of the organization, and essentially push for a team to be formed consisting of senior managers who can discuss such issues and come out with recommendations for resolving such matters. Of course, you should probably only try to do this if you are able to see a need within the organization of a number of teams raising such issues; if most of the requests are coming from a selective group of individuals, then you know that you can talk to them and see whether there is a local resolution of such issues. But, if there seems a need within the organization for a larger discussion, then the select group of senior managers can discuss these issues (even consulting with the team members who raised the impediments), and come out with recommendations, on which there can be changes based on the process setup for making such changes. In order to make this easy to work, a tool could be used to which all team members have access, and the requests logged in such a tool can be taken up by the group of managers for discussion on a regular basis. This is one way of dealing with such organizational impediments.

Leave a Reply

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>