Crystal: Adaptability to Context

Crystal is not a single agile methodology, but a family of methodologies designed to be adaptable to the specific context of each project.

Developed by Alistair Cockburn in the early 1990s, it is based on observation of successful agile teams and recognizes that different projects require different levels of rigor and formality in their processes.

Rather than a "one size fits all" approach, Crystal proposes adjusting the "weight" or formality of the methodology based on key factors such as team size and project criticality.

It is a pragmatic approach that seeks to be as lightweight as possible without compromising safety or success, emphasizing communication and team skills.

Size and Criticality Based Family of Methodologies

Crystal's central idea is that there is no single "right" way to work agile; the methodology must be tailored to the specifics of the project.

The two main factors that determine which "flavor" of Crystal is most appropriate are:

Team Size: The number of people involved in the project. Lighter methodologies work well for smaller teams, while larger teams require more coordination and, therefore, a methodology with a bit more structure.

System Criticality: The potential consequences of a product failure. This is often measured in terms of impact on life, essential money (funds needed for continued operation), discretionary money (funds that do not threaten operation), or comfort.

High criticality projects (where a failure could cost lives or lead to bankruptcy) need more rigorous processes than those where a failure only causes inconvenience.

Crystal offers different methodologies within its family to accommodate these variations.

The Color Scale and its Meaning

Crystal uses a color scale, based on the hardness of the minerals, to represent the "weight" or level of formality of each methodology within the family.

Each color corresponds to a specific combination of equipment size and criticality:

• Crystal Clear: The lightest, for very small teams (1-6 people) working on low criticality projects (loss of comfort or money at will).
• Crystal Yellow: For small teams (7-20 people) on projects of moderate criticality (loss of money at discretion).
• Crystal Orange: For medium teams (21-40 people) and essential money criticality.
• Crystal Orange Web: A variant of Orange specifically tailored for web projects.
• Crystal Red, Maroon, Diamond, Sapphire: Progressively heavier and more formal methodologies, designed for larger teams (up to 200 people or more) and/or very high criticality projects, where even human life could be at risk.

This scale allows the selection of a methodological starting point appropriate to the project context.

People-Centered Approach

A fundamental pillar of all Crystal methodologies is their strong focus on the people that make up the team.

Crystal recognizes that project success depends largely on the skills, talents and communication within the team, rather than following rigid processes.

It prioritizes team interaction, building a collaborative community and leveraging individual capabilities.

Tools and processes are considered secondary and should be adjusted to support the team, not the other way around.

It defines some key roles such as Executive Sponsor, Lead Designer, Developer and Expert Users, but the main emphasis is on human dynamics and effective communication.

Summary

Crystal is not a single methodology, but a family of methodologies. They were designed by Alistair Cockburn to be adaptable to the project context.

It recognizes that different projects require different rigor. Proposes to adjust the "weight" of the methodology according to the size of the team and the criticality of the project.

It uses a color scale (Clear, Yellow, Orange, Red) to represent formality. Crystal has a strong people-centric approach.