Danube - A ScrumMaster's Checklist - Comments

Thanks

LaszloSzalvay — Sun, 24 Aug 2008 11:25:28 -0500

Thanks Krivitsky. I noticed that you referenced back to the original post that Michael had.

article translated to Russian

krivitsky — Sun, 17 Aug 2008 07:48:03 -0500

I took the responsibility of spreading out the wisdom of ScrumMaster's job by translating a part of this article to Russian.

A ScrumMaster's checklist in Russian.

All links and copyrights are preserved. Thank you!

Any comments are welcomed!

not part of the team

topcoder — Fri, 17 Aug 2007 05:27:23 -0500

As per my experience when the ScrumMaster is a non participating one - ie he does not take on development tasks sooner or later he becomes more like a project manager and this is a major scrum smell which you would like to avoid. This happens because the SM is not longer treated by the team as a team member and slowly they begin to accept whatever he says as order and quickly revert pre-scrum habits. Therefore I would not consider part time SMs. It may work for some teams but not for the ones I've seen.

Plamen RB CSM, MCSD

A ScrumMaster's Checklist

MichaelJames — Mon, 13 Aug 2007 08:09:16 -0500

An adequate ScrumMaster can handle two or three teams at a time. If you're content to limit your role to organizing meetings, enforcing timeboxes, and responding to the impediments people explicitly report, you can get by with part time attention to this role. The team will probably still exceed the baseline, pre-Scrum expectation at your organization, and probably nothing catastrophic will happen.

But if you can envision a hyperproductive team -- a team that has a great time accomplishing things no one else can -- consider being a great ScrumMaster.

A great ScrumMaster can handle one team at a time.

We recommend one dedicated ScrumMaster per team of about seven, especially when starting out.

If you haven't discovered all the work there is to do, tune in to your Product Owner, your team, your team's engineering practices, and the organization outside your team. While there's no single prescription, I've outlined some things I've seen ScrumMasters overlook.