Posted By Ian Mitchell on 06 Oct 2013 11:47 PM
A Scrum Development team must control its own process, i.e. everything that is needed to bring their work to completion such that it meets the Definition of Done.
This means that the ability to resolve the matter of a failing resource must also lie under their control. It is not a matter that should fall under the control of any other authority.
Great point Ian, too add to it just a bit:
This is probably one of the hardest concepts for a Scrum Master to accept - especially if he/she comes from a PMPish background where command and control are favored methods. Stepping back and respecting the authority of the team is CRITICAL to their ability to self-organize and to solve problems. Resisting the urge to solve the problems for the development team is something that I think most SM's will struggle with initially.
If a Scrum Master insists on solving all of the problems all they do is coach the development team to be reliant on them. It's far better to ask probing questions and help guide the team to their own solutions.