Member-only story
Drawbacks of Scrum-like methodologies
I’ve already worked in several Scrum teams. Some of it applied a part of Scrum rules with problems, mostly because of management comfort or short-term interests.
This article is a part of my Scrum series, see with free links (including to this article):
I like Scrum. The good Scrum.
If a few Scrum rules are violated, some Scrum concepts will be injured. See Scrum concepts in my article The Scrum concept. To keep the Scrum concepts, other substituting rules should be agreed, otherwise the people (including managers) will be faced with drawbacks.
Scrum Master role on a team member
Scrum Master is not a team member. They drive the ceremonies, but don’t pick tasks from the backlog. Practically, a Scrum Master drives more teams, because only one team does not consume their whole resources.
If a team member plays the Scrum Master role, it’s a sign about bad management (in most cases): the management doesn’t want to invest enough in Agile processes, instead spending precious engineer time on them. It’s comfortable only for the management and the engineers can be blamed because of slow velocity.
The Scrum Master role will be in conflict with another role, which is hard to solve by one person, for example:
