3 ms·
I'm not opposed to a dedicated scrum master, but the issue I have is that I have yet to meet one who ever defends the developers' right to have the agile/scrum
by developer2 11y ago
I'm not opposed to a dedicated scrum master, but the issue I have is that I have yet to meet one who ever defends the developers' right to have the agile/scrum process respected. Really, they just wind up being another manager that happens to spend a lot of time in Jira. I've butt heads a lot with scrum people who bend over and say "yes" to every single (unreasonable) demand thrown at them from the business side. :'(
- ktRolster 11y ago> I'm not opposed to a dedicated scrum master ok, here's something I've been wondering. Assuming your team is in the 8-12 programmer range (which is typical for an agile team), what does the scrum master do with all his time? How is there enough for him to do to fill up a full time job?
- developer2 11y agoI would hope much of their time would be spent really organizing and understanding the scope of each project/task. In my experience, most tasks still get dropped into a sprint without anyone really understanding the full scope. I can easily see 40 hour weeks being spent making sure that everyone is signing off on well-defined tasks. Anything to help reduce the surprise factor is a win in my book.