4 ms·
Another vote for Scrum Master here. It's only in the past 5 years or so that I've personally seen it as a job in itself - previously, I'd seen Scrum Master as p
by GordonS 6y ago
Another vote for Scrum Master here. It's only in the past 5 years or so that I've personally seen it as a job in itself - previously, I'd seen Scrum Master as part of the role of one of the developers or similar.
But now in large corps, Scrum Master exists as a distinct job, which appears to require doing very, very little - chairing most of the regular scrum-related meetings (daily standup, planning, demo, and the much loathed retrospective), sending out meeting invites, occasionally futiley butting heads with the Project Manager, and... actually, I think that's it?!
I've worked with some good people in the Scrum Master role, but beyond being good people to work with, they are glorified secretaries, and really don't have anything to do all day.
- pbronez 6y agoWhy on earth would you have a Scrum Master AND a Project Manager? Makes sense to have a dedicated less-technical person to manage schedules, coordinate with clients and keep people honest on commitments... but dear god why would you ever start splitting that role up into multiple people
- dannyw 6y agoBecause sometimes projects are complicated and require lots of business knowledge, and the project manager may be managing multiple projects. The idea of a "secretary" is not a bad one for high performing teams.
- GordonS 6y agoI've been tech lead on projects with as many as 30 team members, and still the full-time Scrum Master had very little to do.
- kjjjjjjjjjjjjjj 6y agoScrum Masters are basically secretaries with more steps