[2] They in turn have provided inspiration for the Agile software development movement, and for the creation of parts of Scrum and of Extreme Programming in particular.
Patterns are those arrangements or systems of internal relationship which give to any culture its coherence or plan, and keep it from being a mere accumulation of random bits.
These empirical studies were based on subject role-play in software development organizations, reminiscent of the sociodramas of Moreno's original social network approach.
The recurring successful structures were written up in pattern form to describe their tradeoffs and detailed design decisions (forces), the context in which they apply, along with a generic description of the solution.
Kent Beck was the shepherd (interactive pattern reviewer) of the Coplien paper for the 1995 PLoP, and he mentions the influence of this work on extreme programming in a 2003 publication.
[23] The idea of daily Scrum meetings in fact came from a draft of an article for Dr. Dobb's Journal [24] that described the organizational patterns research on the Borland QPW project.
[25] Beedle's early work with Sutherland brought the pattern perspective more solidly into the history of Scrum.
In this vein, the first ScrumPLoP conference took place in Sweden in May, 2010, sanctioned by both the Scrum Alliance and the Hillside Group.