Twitter

ScrumMaster Removing Obstacles

I had a lingering issue resolving connection to an outside VPN and getting into a CVS repository for weeks. I’ve been on and off trying to get it resolved between typical management tasks. Today I mentioned it as an impediment in Scrum where I’ve volunteered to do some coding. By 1:30 in the afternoon the problem had been solved. Sign of a Scrum Master on the ball.

4 comments to ScrumMaster Removing Obstacles

  • Hey, Ed, they say what we’re doing is wrong.

    I’m a Software Development Manager down in Fresno. I am, like you, also the team’s ScrumMaster. Most scrum gurus say that juggling these dual roles is a bad idea. So far, it’s worked for my team, but I’d love to hear your perspective.

  • Currently I’m not having to serve as a Scrum Master on a project, just filling in from time to time when a Scrum Master is out.

    I think it’s suboptimal to be a manager and Scrum Master, but then lots of Scrum projects have to deal with suboptimal practices on something. I think if it’s working for you I wouldn’t worry about it too much. My plan was to mentor up some others and that’s worked pretty well. I’ve seen some dyed in the wool PMPs change as they realized Scrum had a lot of process to it and they actually got a chance to really pitch in with the team and not just deal with Gantt charts and meeting minutes all day.

  • You mentoring description sounds like exactly what I’ve done. Next month, my two teams will adopt Scrum Masters from within the teams. After a year in the dual roles, I will be happy to have time to focus more on the big picture, but at the same time, it will be exciting to see how the mentorship has paid off.

  • Mentoring can pay pretty good dividends. Congrats on reaching the milestone of handing over the reins.