Welcome back to another week at www.implementingscrum.com.
So. Last week I wrote about the atrocities I am seeing out there today in trying to fill new spots with the role of a ScrumMaster.
It is amazing what people are doing.
As the comic strip above depicts, it is not always an easy thing to do.
So what should you be looking for in a new ScrumMaster — or someone to come in and coach some of your new Certified ScrumMasters?
Sorry… make that two.
This is something I have found as a trait that successful ScrumMaster candidates I have worked with show as a great attribute.
“Huh Mike?” you may be asking yourself.
Let me put it to you this way.
If you are interviewing some Super-Duper-ScrumMaster who appears to walk-on-water and always-has-THE-answer, can I give you a solid word of advice?
Or throw the candidate some stupid, off-the-wall question like they used to do (maybe they still do) over at Uncle Bill’s house of pain?
I consider myself a good ScrumMaster and Certified Scrum Practitioner and Certified Scrum Trainer. I work with many clients around the world on those thorny “Scrum Issues” and, in reality, I do not give them the answers.
Instead, I try to work with them to see if they can come up with their own answers.
Many of my prospects (or sometimes clients) do not like that way of working with me. They want me to come in like “Captain Obvious” and save the day.
Over time, I have learned this is not the best way for me to be effective.
Some teams do not like to have to “figure out” their own issues.
Some teams do not like how it feels to, “Fail Fast.”
This concerns me.
If someone comes in spewing some Scrum Religion BS silver bullet theory — be very cautious.
If someone comes in with some war wounds and is humbled to be in your presence…. it may be worth a further look and more conversation.
This is only my opinion.
But I have seen it start to work in the real world.
Gotta run!.Please send comments, questions, criticisms, ideas, or whatever here.
You can also enter The Scrum Community to discuss this entry and other Scrum topics. Thank you!
November 19, 2007