[hidro]

I like how Scrum promotes transparency and trains each individual to become self-managed (or at least getting better at it). But it often feels like it's being hyped up, with many people getting obsessed over its practices/rituals.

Estimating work is a nice idea, but using 'story points' for it just feels like a bad API decision - I have never seen a new Scrum team member (including me) getting it at 1st try.

And maybe it's just me, but having a full time, dedicated Scrum Master, who serves solely as a facilitator (without having any actual role in product delivery) is a nightmare, especially for teams that are used to Scrum practices.

[UK-AL]

"I have never seen a new Scrum team member (including me) getting it at 1st try." - I've never seen one get an accurate time based estimate either. Even experienced ones.

[matthewmacleod]

That's one of the reasons that Scrum doesn't use time-based estimates.

[blub]

I am a SM and a dev and it's not at all a comfortable position to be in, because it's often making demands on my time and there are conflicts of interest (but not as bad as SM/PO or SM/manager).

The SM is major piece of the Scrum puzzle and a lot of practices lose their value if the SM is not paying attention.

This over-reliance on the SM is a minus for Scrum IMO.