Cockburn Scale
Encyclopedia
The Cockburn Scale, also known as the Project Classification Scale, is a method of describing how much formal process a software project
requires. The scale was described in Alistair Cockburn
's book Agile Software Development. According to the author, the scale can be applied to other types of project, not only those that employ Agile
methodologies.
Process criticality is defined as the worst probable effect of an unremedied defect:
Process size is defined as the size of the project's development staff. It is an open-ended scale, but the most commonly used values are 6, 20, 40, 100, and 200.
A project is described by a pair of criticality and size indicators: for example, a two-person, life-critical project is categorized as a L6, while a 50-person project that, if it fails, could jeopardize the profits of an organization but not the organization's continued existence is categorized as a D100.
Project classes further from the bottom left corner of the table require a more formal process than project classes closer to the bottom left corner.
Project management
Project management is the discipline of planning, organizing, securing, and managing resources to achieve specific goals. A project is a temporary endeavor with a defined beginning and end , undertaken to meet unique goals and objectives, typically to bring about beneficial change or added value...
requires. The scale was described in Alistair Cockburn
Alistair Cockburn
Alistair Cockburn is one of the initiators of the agile movement in software development, helping write theManifesto for Agile Software Development in 2001 and the agile PM Declaration of Interdependence in 2005...
's book Agile Software Development. According to the author, the scale can be applied to other types of project, not only those that employ Agile
Agile software development
Agile software development is a group of software development methodologies based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams...
methodologies.
Definition
The Cockburn Scale categorizes projects according to "criticality" and "size".Process criticality is defined as the worst probable effect of an unremedied defect:
- Loss of Life (L)
- Loss of Essential Money (E)
- Loss of Discretionary Money (D)
- Loss of Comfort (C)
Process size is defined as the size of the project's development staff. It is an open-ended scale, but the most commonly used values are 6, 20, 40, 100, and 200.
A project is described by a pair of criticality and size indicators: for example, a two-person, life-critical project is categorized as a L6, while a 50-person project that, if it fails, could jeopardize the profits of an organization but not the organization's continued existence is categorized as a D100.
Application of the Scale
The criticality and size of a project can be juxtaposed on a grid:| L | L6 | L20 | L40 | L100 |
|---|---|---|---|---|
| E | E6 | E20 | E40 | E100 |
| D | D6 | D20 | D40 | D100 |
| C | C6 | C20 | C40 | C100 |
| 1-6 | 7-20 | 21-40 | 41-100 |
Project classes further from the bottom left corner of the table require a more formal process than project classes closer to the bottom left corner.
External links
- Methodology per project - Alistair Cockburn's article in which he defines the scale that is now known as the Cockburn Scale
- Cockburn Scale discussion - An extract of the relevant discussion by Alistair Cockburn
- A Practical Guide to Seven Agile Methodologies - uses the Cockburn Scale to compare different Agile methodologies and their applicability.