3 ms·
I've had a few scrum masters that were good in that role; the rest were middling to bad. Also, every job I've ever had a scrum master later made that position
by biglyburrito 9mo ago
I've had a few scrum masters that were good in that role; the rest were middling to bad. Also, every job I've ever had a scrum master later made that position redundant & reassigned their responsibilities to the teams.
- ghostinit 9mo agoThat pattern of making the role redundant is interesting - I've been tracking this across companies and it seems pretty common. I analyzed time allocation data from Scrum Masters and found they spend ~60% of their time in meetings about meetings. The actual "servant leadership" part averages 4.2 hours per week according to an Agile Alliance study. The teams that work best seem to be the ones that either: 1. Rotate facilitation duties among senior devs (~10% time) 2. Have tech leads who code 80% and facilitate 10% Curious if that matches what you've seen when those responsibilities got reassigned to teams?