Cameron Wallace McKenzie wrote:Or is Scrum a process framework?
If you are taking the Scrum Master exam, or you don't want to upset the applecart, you must embrace the idea that Scrum is a framework.
Saying anything contrary will lose you points on the exam, and saying Scrum is better described as a methodology or a process will get you bullied and harassed in the Scrum community.
The Scrum community is very tribal over certain things, and this is one of them.
The truth?
It's not a framework. The Scrum Guide admits this when it says Scrum is a 'purposefully incomplete framework.'
Something that is incomplete is not the thing it aspires to be. I have an incomplete PhD. Do I have a PhD? No.
Furthermore, it does not fit the dictionary definition of framework. It fits better with process or methodology.
And even given modern usages of the term framework it doesn't fit.
Scrum insists you must use every part or it's not Scrum. Frameworks have more of a 'pick and choose' type of usage. You can use the Sprint Boot framework without using its REST APIs. But if you miss a single Scrum event, you're not doing Scrum.
Having said that, members of the Scrum community will get outright nasty with you if you speak truth to power, so I don't suggest discussing this topic unless you are in for a fight.
It always upsets me to see tribalism dominate technical domains, but this tribalism is quite evident in the Scrum community.
