Summarizing Scrum (a list)
The more I think about Scrum, the more it becomes a Gestalt…a whole thing. It becomes somewhat misleading to talk about its parts.
Scrum itself is actually very small. We recommend you do all of Scrum; it will lead to better results almost always. It you only take part of the medicine…well, you will not get the real benefit.
Still, we must discuss Scrum one word at a time. For reference and other purposes, we can simplify this into a list as a basis for discussion. In normal circumstances, these discussions lead to a better life for you, your Team and your customers.
Scrum was ‘co-created’ by Jeff Sutherland and Ken Schwaber. Their definition of it, the core definition, is in the Scrum Guide. This is now about 17 pages.
I now have a two-page list of things that define Scrum. The link goes to my latest version (V5).
This list is based mainly on the Scrum Guide, and discussions with Jeff Sutherland, and reading and experience.
The first thing to note is how simple the basic framework of Scrum is.
Secondly, you will note my bias, which is that the ideas behind Scrum are at least as important as the explicit Roles, Meetings and Artifacts of Scrum.
The items in brackets [ ] are things that are not in the Scrum Guide. I believe all of them are ‘supported’ by Jeff Sutherland, if not others as well. Thus, I do not feel I am adding unfairly to Scrum.
But, they are not all required to be doing ‘the bare framework of Scrum.’