About agilepatterns.org

The patterns are roughly collated under three headings: Patterns of Method, Patterns of Responsibility, and Patterns of Representation. The Agile Transformation Framework pattern transcends all three categories. In addition we present a collection of antipatterns...which are not so much an indication of best practices, but rather of common mistakes that are best identified in order to avoid them.

Each pattern is accessible from the sidebar, and is defined using a simple pattern language with the following elements:

1. a name, which must be unique

2. a supporting diagram

3. a description of:

   • the intent behind the abstraction of the pattern

   • any proverbs that help illustrate its everyday relevance

   • any terms by which it might also be known - this entry is optional

   • the motivation for using it

   • the structure of the pattern, with particular relevance to the supporting diagram

   • the situations in which the pattern is most applicable

   • the consequences of using the pattern

   • common implementations of the pattern

   • references to related patterns or items of interest

Pattern Availability

Each pattern is provided under the Creative Commons License Attribution-ShareAlike 4.0 International (CC BY-SA 4.0). The startup@scale® trademark refers to the transformation framework and associated patterns as they appear and are described on agilepatterns.org. Producers and users of any derived works should avoid using this trademark when referring to such derived works. The agilepatterns.org repository is curated by Ian Mitchell.

The wider community: other pattern-based approaches

• Mike Cohn has advocated a pattern-based approach to agile transformation (See the Patterns for Adopting Scrum chapter in his book Succeeding with Agile), including an improvement backlog and a sponsored "Enterprise Transition Community" that guides the transformation with respect to a suitable cadence.

• Jeff Sutherland has also recently adopted a pattern-based approach to achieving "Scrum at Scale".

• The use of transformation backlogs, strategic visioning, and transformation rollout teams has been presented by Ken Schwaber and Jeff Sutherland in their book Software in 30 Days, in the Scrum at the Enterprise Level and Scrumming Scrum chapters.

• Dean Leffingwell, the originator of the Scaled Agile Framework, has advocated a set of seven transformational patterns.

• The Scrum Pattern Community has promoted the use of patterns in the enterprise for several years now. This experience has been brought to bear in Jim Coplien's Organizational Agility Program in which patterns are selected for adoption with strong management sponsorship for change.

You can follow @gilepatterns.org on Twitter: https://twitter.com/gilepatterns