Crystal
Crystal arose from Cockburn's conviction that there is no universally optimal methodology: what works for a team of three people building an internal application is different from what a team of forty people developing a critical financial system needs.
The two parameters of Crystal
Criticality
It measures the consequences of a system malfunction, according to the integrity levels of the IEEE 1012 standard:
- (c) Comfort: loss of comfort or usability.
- (d) Discretionary money: moderate financial losses.
- (e) Essential money: serious financial losses.
- (l) Life: loss of human life.
Team size
Crystal determines the size of the system by the number of people involved in its development: 6, 20, 40, or 80 people.
The Crystal family
The combination of criticality and size determines which Crystal variant is most suitable. The main ones are:
- Crystal Clear: for teams of up to 6 people on low-criticality projects. It is the most thoroughly documented variant and the one Cockburn described in greatest detail in his 2005 book.
- Crystal Yellow: for teams of up to 20 people.
- Crystal Orange: for teams of up to 40 people.
- Crystal Red: for teams of up to 80 people.
The greater the size and criticality, the more formality, documentation, and structured communication Crystal prescribes.
Common foundations
All Crystal variants share the same principles:
- Iterative and incremental development with a maximum iteration length of 4 months (Crystal recommends between 1 and 3 months).
- Emphasis on people over processes: Crystal is explicitly "human-centric." Cockburn argues that the human factor is the most decisive factor in the success of a software project.
- Emphasis on direct communication: the more fluid and direct the communication within the team, the less formal documentation is needed.
- Adaptability: Crystal is designed to incorporate practices from other agile frameworks (Extreme Programming, Scrum) when the team finds them useful.
Crystal in Perspective
Crystal has seen limited adoption in industrial practice. It has been overshadowed by Scrum, which offers a more specific and prescriptive structure. Its value today is mainly conceptual:
- The idea that there is no universally optimal methodology and that the process must be adapted to the context remains relevant and is well argued.
- Cockburn's emphasis on people and direct communication as primary success factors influenced the Agile Manifesto, of which he was one of the signatories.
Common mistake
Trying to adopt Crystal without adapting the variant to the context. Crystal Clear, the best-known variant, is designed for teams of up to 6 people. Applying it to a team of 30 people ignores the framework's central principle: that the process must be tailored to the size and criticality of the project.
References
- Cockburn, Alistair. (2005). Crystal Clear: A Human-Powered Methodology for Small Teams. Addison-Wesley.
See also
Want to advance in agility? You can search for course and exam calls, or go at your own pace by becoming a member of the Agile Club. This membership includes exclusive resources, e-learning classrooms, and access to Skill Arena: a space to practice and measure your agile skills at your own pace.