How to use the catalog of Pattern Languages of Programs (a.k.a. Scrum PLoP)?



  • A few days ago I watched a talk by James "Cope" Coplien, titled "Patterns: The New Defacto Scrum Standard". It is then that I learned that "organizational patterns" is a thing. Apparently, Scrum is just a set of organisational patterns - as in, you could define the Scrum framework in terms of organisational patterns, and that would be equivalent to what is defined in the official Scrum Guide. Frankly speaking, I still had no idea how organization patterns are related to Scrum after watching the whole talk.

    So I found the Scrum PLoP website and the associated catalog of patterns. The catalog is HUGE, but there doesn't seem to be any kind of foreword or introduction page about how to use that catalog in the context of implementing the Scrum framework, especially for software development.

    Has anybody heard about Scrum PLoP before? How do you use it? Or maybe point me to a clear explanation somewhere?



  • Patterns are things that have been observed in the world and found to be good. The idea has their roots in Christopher Alexander's work in architecture and planning, primarily books like The Oregon Experiment and A Pattern Language. They were popularized in the software field by the Gang of Four (Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides) in Design Patterns: Elements of Reusable Object-Oriented Software and have since found their way into other topics and fields as well.

    Typically, patterns are defined in terms of the problem they are designed to solve, a context (appropriate and/or inappropriate situations for their use), and a description of the solution pattern. Patterns aren't necessarily something that you "use". They are more like things that you are aware of. If you have a given problem, you can look at patterns that other people have applied to solve similar problems. You can then look at the contexts in which the pattern has been observed to be successful and see if your context is similar or not. Then, you can choose to implement the solution.

    I've heard of Scrum PLoP before, and have browsed through it. However, it seems unfinished. Not all of the patterns are well-defined and some are missing information about the context and the solutions. I'm not sure what the current state of this project as a whole is, but there are many dead links or bad references.



Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2