Differences

This shows you the differences between two versions of the page.

--- 2014:methodology_patterns_workshop [2013/11/14 20:11] – jonjagger
+++ 2014:methodology_patterns_workshop [2016/06/11 14:05] (current) – external edit 127.0.0.1
@@ Line 6: / Line 6: @@
 **Duration**: 90 mins\\
 **Description**: \\
-I've recently started to work on the idea of "Methodology Patterns" as an alternative way for teams to come up with a methodology fit for their needs--a one methodology per project as proposed by Alistair Cockburn. The idea is to describe all the practices (all meaning technical like TDD, but also managerial, leadership, etc.) we use every day as patterns and to connect them in a set of overlapping pattern languages which, in turn, can be used as starting point to implement the one-methodology-per-team approach--using patterns and pattern languages to do that is not a new idea, see for example Jim Coplien's "Organizational Patterns" book, but it has been overlooked in the main methodology debate, which, instead, has been mostly focusing on finding "The Methodology" to solve all problems.
+I've recently started to work on the idea of 'Methodology Patterns' as an alternative way for teams to come up with a methodology fit for their needs - a one methodology per project as proposed by Alistair Cockburn. The idea is to describe all the practices (all meaning technical like TDD, but also managerial, leadership, etc.) we use every day as patterns and to connect them in a set of overlapping pattern languages which, in turn, can be used as starting point to implement the one-methodology-per-team approach - using patterns and pattern languages to do that is not a new idea, see for example Jim Coplien's 'Organizational Patterns' book, but it has been overlooked in the main methodology debate, which, instead, has been mostly focusing on finding 'The Methodology' to solve all problems.
 The use of patterns and pattern languages has several advantages, among the others:\\