Good question.
The ScrumMaster is a team coach, not a player.  The ScrumMaster is to
care for and improved the performance of the team.  Sometimes
technical knowledge can be an asset to accomplish this goal.
Sometimes it could be a liability if he gets wrapped up in technical
things instead of the team. So it depends, doesn't it.

An interesting tangent discussion of this topic is a thread from some
time back: "Compelling case for dedicated ScrumMaster"
http://groups.yahoo.com/group/scrumdevelopment/message/32026?var=1

Alan

On Thu, Jun 10, 2010 at 3:40 AM, poojawandile <poojawandile@...> wrote:
>
>
>
> Hi,
>
> I would like to hear from forum members:
>
> "Does it help to have a scum master on a team without technical
> background, does he/she adds value to the team?"
>
> IMO:
>
> Having a scrum master with techncial background definately is a big
> plus. He/she can help in resolving technical issues. Once the team has
> matured and understands scrum ceremonies there is not much value add
> from a scrum master. Day in day out the team is struggling in getting
> the issues resolved and focusing on sprint deliverables. For most the
> time they are interacting with the technical expert and since that
> person resolves their issues eventually helping them in completing their
> deliverables, he gets more visibility/credibility as against the SM. The
> role of a SM just gets confined to a process consultant and hence lacks
> visibility as well as credibility.
>
> Any takers on this?
>
> thanks,,
>
> pooja
>
>