4 ms·
I worked as a scrum master for a while. I worked with multiple teams. Besides the mechanics of stand-ups, estimation, grooming, and retrospectives. I did a lot
by Tagbert 4y ago
I worked as a scrum master for a while. I worked with multiple teams. Besides the mechanics of stand-ups, estimation, grooming, and retrospectives. I did a lot of work going over stories with product managers clarifying requirements, getting them to put in more details, and helping them prioritize the backlog. I also spent a lot of time tracking down the sources of blockers for team members. Often this was getting other teams to respond on information requests or negotiating for work to be done by other teams. I agree that one scrum master can handle more than one team, but don’t assume that the only work you saw was when they were in meetings with you. Do you expect them to assume you only work during stand-ups?
- HeyLaughingBoy 4y agoEverything you describe was part of my job as a team lead. I also wrote code, BTW.
- karmakaze 4y agoI was getting the sense that that is more than what a Scrum Master (facilitator? showing it's outdatedness) should do. I googled it[0]. Seems only to be responsible for meta/process improvement things. The SM is supposed to have the team doing all those things more effectively rather than doing any themself. [0] https://www.scrum.org/resources/what-is-a-scrum-master https://www.scrum.org/resources/what-is-a-scrum-master
- nicbou 4y agoI've done this too. There was no Scrum involved. I was a sort of project manager slash secretary slash developer advocate. I did not carry a toolbox full of markers and postits, and kept working people out of meetings. It feels weird to call that being a scrummaster.