What is one of the risks if the Scrum Master is also a programmer on the team?
What is one of the risks if the Scrum Master is also a programmer on the team?
One of the main risks if the Scrum Master is also a programmer on the team is that they cannot stay away from critical path activities. This could lead to the Scrum Master becoming too involved in development tasks, potentially neglecting their primary responsibilities as a facilitator and servant-leader for the team. This dual role can create conflicts of interest and reduce the effectiveness of both roles.
B should be the correct answer (see "Succeeding with Agile" chapter 7 page 124)
The Scrum Master tries to push through changes to the process.
why B is the wrong answer, in this case
I think answer B is the correct one hier acc to Succeding with Agile pg 124. Answer C would be correct if the SM role ist rotated among the team members (pg 123 - Rotating the SM). Of course in reality both answers can be right. This question is not asked properly.
Correct answer is B,
again which answer finally is correct?
If the Scrum Master is also deeply involved in programming tasks, they may get pulled into the critical path activities related to development, potentially neglecting their responsibilities as a facilitator and servant-leader for the team. While C is a potential risk, it is not specific to the Scrum Master being a programmer. Any Scrum Master, regardless of their background, should avoid imposing changes and instead facilitate a collaborative approach to process improvement.