Crystal | Glossaire

Crystal is a family of agile methodologies created by Alistair Cockburn, one of the signatories of the Agile Manifesto. Unlike prescriptive frameworks, Crystal offers an adaptive approach where the process adjusts based on team size, system criticality, and project priorities. This philosophy recognizes that no single methodology applies universally to all contexts.

Crystal Fundamentals

Methodological adaptability based on project context (size, criticality, complexity)
Prioritization of direct communication and human collaboration over rigid processes
Color-based classification (Clear, Yellow, Orange, Red) corresponding to different team sizes
Focus on frequent value delivery rather than process compliance

Benefits of Crystal

Maximum flexibility enabling methodology adaptation to real project constraints
Reduced bureaucracy by eliminating non-essential practices for the specific context
Improved productivity through emphasis on osmotic communication
Natural process scalability as team and project grow
Better alignment between methodological rigor and system criticality

Crystal Variants

Crystal comes in several variants, each tailored to a specific team size and criticality level. The color-based nomenclature facilitates selecting the appropriate variant:

Crystal Clear: teams of 1-6 people, low-criticality projects, minimal process
Crystal Yellow: teams of 7-20 people, requires more coordination and documentation
Crystal Orange: teams of 21-40 people, moderate criticality, increased organizational structure
Crystal Red: teams of 41-80 people, high criticality, rigorous process and traceability

Essential Crystal Properties

Alistair Cockburn identified three fundamental properties that every Crystal project should respect to ensure success:

Frequent deliveries: regular deployments enabling empirical validation and rapid adjustment
Osmotic communication: physical or virtual proximity fostering informal information exchanges
Reflective improvement: systematic retrospectives to continuously optimize the process

Implementing Crystal

Assess project criticality across four levels: Comfort (C), Discretionary Money (D), Essential Money (E), Life (L)
Determine team size to select the appropriate Crystal variant
Identify essential properties applicable to the specific project context
Implement minimal necessary practices according to the chosen variant
Organize short delivery cycles (2-4 weeks) with reviews and retrospectives
Promote team colocation or rich communication tools for distributed teams
Progressively adapt the process based on feedback and context changes

Expert Tip

Don't overload your Crystal process with non-essential practices. Start minimalist with the three fundamental properties, then progressively add elements only if their value is demonstrated in your specific context. Methodological lightness is a strength, not a weakness.

Associated Tools and Practices

Kanban boards or physical boards for workflow visualization
Synchronous communication tools (Slack, Teams) to maintain osmotic communication
Physical or virtual collaborative spaces (Miro, Mural) for team workshops
Continuous integration systems (Jenkins, GitLab CI) to automate frequent deliveries
Structured retrospectives using varied formats (Mad/Sad/Glad, Starfish)

Crystal represents a mature and pragmatic approach to agility, particularly suited for organizations seeking to avoid methodological dogmatism. By recognizing that each project has its own constraints and characteristics, Crystal optimizes the value-to-effort ratio of the process itself, thereby freeing team energy to focus on creating business value rather than conforming to a rigid framework.