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.
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.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
ellastf
11 months, 2 weeks agoNosrat
2 years, 5 months agofoxpro7
3 years, 2 months agoKnivesout
3 years, 5 months agoTORA
3 years, 8 months agojuzer
4 years, 6 months agoRudo
4 years, 7 months ago