If Scrum is so simple, why is it so hard to describe? Tobias Mayer recently launched the idea of Simple Scrum – Scrum reduced to its essence. I think the essence Scrum can be defined even more concisely – in 100 words or less. 100 words, which will be understood by the novice, without using the Scrum lingo — Product Owner, ScrumMaster and other such words are not allowed.
The Essence of Scrum in 100 Words:
Scrum is an empirical management process for addressing complex problems that ensures effective communication between a Requester and an implementation Squad. The Requester represents the interests of all stakeholders. The self-organizing, interdisciplinary Squad produces finished outcomes at regular intervals in response to prioritized requests. They measure their progress in terms of finished outcomes.
The maximum interval is 30 days. After each interval, the Squad has produced an improved product or service and made themselves more productive and happier. A Court Jester helps Requester and Squad improve their performance, and encourages positive change in the rest of the organization.
(actually 98 Words)
The Court Jester?
Why did I call the ScrumMaster a Court Jester? Court Jesters were the original change agents. They were trained and expected to criticize their kings and queens. How would you like to be a Certified CourtJester? Could be fun, could be dangerous…
The Essence of Scrum defines the ‘What’. I think you can derive all of the ‘How’ from this definition. Have I missed anything? How would you describe Scrum in 100 Words or less?