Protecting the Team Cuts Both Ways

This content is syndicated from Mike Cohn's Blog - Succeeding With Agile® by Mike Cohn. To view the original post in full, click here.

It is a generally accepted Scrum dictum that one of the ScrumMaster’s duties is to protect the team. The usual example is that the ScrumMaster must protect the team from an overly aggressive product owner. There is nothing wrong with this example and many teams do need to be protected from a product owner whose desire for more functionality can push the team into cutting quality corners. However, a good ScrumMaster also protects the team from a problem that can be even more harmful: complacency. After acheiving some easy, early improvement from Scrum, some teams become self-satisfied. They stop seeking further improvements. It is up to the ScrumMasters of those teams to protect them from this complacency. So, a good ScrumMaster will occasionally have to stand up to an aggressive product owner and say, “Now is not the time to push this team any harder. They’re working as hard as they can and if pushed more, they’re likely to get sloppy.” But my advice to good ScrumMasters is that for each time they say this, they should later tell the product owner something like, “Now’s the time. The team is rested. They’re ready. Let’s see what they can do. It’s time to push them for more.” If you’re a ScrumMaster, be sure to protect your team from both types of problem.

One Response to “Protecting the Team Cuts Both Ways”

  1. Tim says:

    I believe this is something that most scrum masters do, they stop the Kaizen process and therefore don’t try to seek further improvements. I think scrum masters should take a note (or two) out of a Lean Six Sigma black belts book. Black belts are change agents and are proactive in learning and presenting new process ideas, not just stopping when the process seems perfect.

Leave a Reply

What is 2 + 6 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)