Scrum++: Optimising your Scrum
Organisational patterns were one of the foundations of Scrum: Daily Stand-Ups were inspired by the pattern-based empirical research on software development at Bell Labs in the early 1990s. Nonaka-sensei, the grandfather of Scrum, points to organizational patterns as an interim step between his own work and the emergence of Scrum. These days, Scrum’s inventor Jeff Sutherland uses patterns in his Scrum courses; he talked at length about his patterns at Agile 2013. And a group of industry leaders including Mike Beedle, Gabrielle Benefield, Jeff Sutherland, Jim Coplien, and many others, meet regularly in a forum called Scrum PLoP® to build a body of literature that comprises an authoritative, rationalized definition of Scrum — and you’ll learn the foundations of that literature in this intensive two-day course.
Most Scrum courses give you the surface process-level tools of Scrum: the lightweight high-level process itself, the artifacts manipulated by these these processes, and the governance between the roles that carry out the process. However, Scrum while Scrum isn’t heavy on process, its meat lies in how we structure time, work, and organizations. These secrets aren’t far beneath the surface of Scrum but, unfortunately, some teams never get to them. Scrum community experts have been collecting these patterns for years, and even the inventor of Scrum, Jeff Sutherland, now uses them as a central part of his training and of describing Scrum. Now they’re openly available to you. Come and learn how to use them and what they mean to your organisation!
You cannot read about these ideas in the Scrum Guide or Agile Atlas. The Scrum patterns are your way to Kaizen (continuous improvement). We want you to be able to tell a story of your own Scrum team that goes like this — exemplary of five of the most important patterns of successful Scrum teams:
In our Stable Team we have a Definition of Ready. It gives us Enabling Specifications for our Product Backlog Itemsbefore we enter a Sprint. During the Sprint we perform our tasks by Swarming while our ScrumMaster ensures Illegitimus non Interruptus. Most of our Sprint Goals are based on the Happiness Metric.