The Scrum Guide opens with a little historical information about its development and refinements. The authors, @Jeff Sutherland and @Ken Schwaber , were also members of the cohort who released the Agile Manifesto although that came after development began on scrum but before the first Scrum Guide was made public.
We developed Scrum in the early 1990s. We wrote the first version of the Scrum Guide in 2010 to help people worldwide understand Scrum. We have evolved the Guide since then through small, functional updates. Together, we stand behind it.
From: The official Scrum Guide While Scrum does have critics, there is a reason it has stood the test of time and is worthy of being stood behind.
The Scrum Guide contains the definition of Scrum. Each element of the framework serves a specific purpose that is essential to the overall value and results realized with Scrum. Changing the core design or ideas of Scrum, leaving out elements, or not following the rules of Scrum, covers up problems and limits the benefits of Scrum, potentially even rendering it useless.
From: The official Scrum Guide We follow the growing use of Scrum within an ever-growing complex world. We are humbled to see Scrum being adopted in many domains holding essentially complex work, beyond software product development where Scrum has its roots. As Scrum’s use spreads, developers, researchers, analysts, scientists, and other specialists do the work. We use the word “developers” in Scrum not to exclude, but to simplify. If you get value from Scrum, consider yourself included.
From: The official Scrum Guide As Scrum is being used, patterns, processes, and insights that fit the Scrum framework as described in this document, may be found, applied and devised. Their description is beyond the purpose of the Scrum Guide because they are context sensitive and differ widely between Scrum uses. Such tactics for using within the Scrum framework vary widely and are described elsewhere.
From: The official Scrum Guide When was Scrum developed? When was the first version of the Scrum Guide written and why? What does the Scrum Guide contain? What does each element of the framework serve? What happens if changes are made, core element are left out, rules of Scrum are not followed? Is Scrum only used for software development? What is the word “Developers” used for? What doesn't the Scrum Guide include and why not?