Jeff Sutherland and Ken Schwaber first codified Scrum in a paper presented at OOPSLA in 1995. Since then they have been the curators of the definition of what Scrum. The Scrum Guide has gone through a number of revisions, mostly in an effort to get Scrum down to its absolute essentials. It isn't designed to tell people what not to do, almost every Scrum implementation is adapted to any organizations unique environment and culture. Instead it is designed to tell people, this is the absolute minimum. This is all that you need to do to be doing Scrum, everything else should serve your needs, but this is what you absolutely must do to do Scrum effectively.
We, actually, recommend a number of other patterns and practices to companies we consult with, but they aren't part of the core of Scrum. They are just ideas we've found useful.
You can read the Scrum Guide and download it freely here.
What are your thoughts on the Scrum Guide? What could make it cleared and more helpful? What ambiguities and language do you find puzzling or distracting? If you've been scratching your head over a concept or practice, here's the place to ask.
The Scrum Guidescrum guide
No replies to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users