The Agile Scrum framework has some fairly simple principles. Implementing them correctly can be complex. Scrum is not changeable and although implementing only parts of Scrum is possible, the result is not Scrum. So where is the best place to start?
How Scrum as we know it came about is open to some debate There is no doubt that the term was first mentioned by Hirotaka Takeuchi and Ikujiro Nonaka in their 1986 Harvard Business Review article, “The New New Product Development Game”.
The framework for Scrum as we know it now was written by Ken Schwaber and Jeff Sutherland. It is still updated by them on a periodic basis. It has been developed, defined and refined since the 1990’s.
A public document, The Scrum Guide, defines the most official version of Scrum. It is the place where the framework is considered at its most up to date in the eyes of its creators.
A PDF version is also available for download.
This definition consists of Scrum’s roles, events, artifacts, and the rules. It is a key document to be understood if you are to use the framework in your organisation. There are many other great resources for learning about Scrum, but this document is the one to read and understand if you want to implement the framework fully and correctly.