Scrum Primer – Obey my rules!

I’ve taken a look today at what we call the Scrum Primer – this is the Scrum Guide written by the Scrum notoriety Ken Schwaber and Jeff Sutherland. Check it out here: https://www.scrum.org/Portals/0/Documents/Scrum%20Guides/Scrum_Guide.pdf

As you might now, Scrum is an Agile methodology, so it should be a framework that would sustain the Agile principles. And here they are ( http://agilemanifesto.org/principles.html ) written and signed in 2001 by the same guys above.
There are 1 line in these principles that is beautiful:
‘At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly’.
This means that team is wise enough to decide what is working and what is not and they are also empowered to change the game in order to maximize their efficiency.

Now comes the interesting part: if you search the Scrum primer you can find 10 occurrences of the word “rule”. The paper closes with this statement:
“Scrum’s roles, artifacts, events, and rules are immutable and although implementing only parts of Scrum is possible, the result is not Scrum. Scrum exists only in its entirety and functions well as a container for other techniques, methodologies, and practices.”
In time more and more rules were added to Scrum: velocity, story points, ready for development, acceptance criteria, grooming, pre-grooming and others that do not pop in my mind.

Isn’t it strange that a methodology derived from Agile comes up with rules and if you break them consciously and based on educated decisions you are no longer doing Scrum?

Sorry Scrum primer and Scrum parents, but sometimes it all comes down to delivering with good quality, in time, with a motivated team, what the customer needs, so I’d break any rule !

——————————————————————————————————
To encourage or discourage my writing adventure a like or a comment will be greatly appreciated. Thanks