# Crystal Methods

Crystal is a family of people-centered Agile methods tailored to team size, system criticality, communication needs, and local context.

- Type: method
- Domain: Delivery & agility
- Level: Intermediate
- Last reviewed: 2026-09-22
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/crystal-methods/>)

## What it means

Crystal is Alistair Cockburn’s family of Agile software-development methods rather than one universal process. Variants such as Crystal Clear and Crystal Orange adjust the amount of coordination and ceremony according to the number of people involved and the consequences of defects, while prioritizing communication and a habitable working method.

## Why it matters

Projects differ in scale, risk, distance, skills, and organizational constraints. Crystal makes method design an explicit contextual decision. It emphasizes frequent delivery, reflective improvement, close communication, personal safety, focus, access to expert users, and a supportive technical environment instead of assuming one process fits every team.

## When to use it

Consider Crystal when a team needs lightweight guidance and has enough experience to tailor its working agreements responsibly. Crystal Clear was designed for small, closely collaborating teams on non-life-critical work; larger or more critical efforts require additional structure, evidence, and coordination rather than a casual copy of Clear.

## How it works

1. Assess team size, geographic distribution, system criticality, and communication constraints before selecting an initial method shape.
2. Set short delivery, iteration, and integration cycles that provide working software and rapid feedback.
3. Create rich communication through proximity or deliberate remote substitutes, visible information, and direct access to knowledgeable users.
4. Protect personal safety and focus so people can surface bad news, resolve disagreements, and complete meaningful work.
5. Hold regular reflection workshops, retaining helpful conventions and experimenting with changes as the project evolves.

## A practical example

A seven-person internal-tools team begins with Crystal Clear. It releases every six weeks, integrates daily, keeps priorities visible, and schedules weekly access to payroll experts. In a monthly reflection workshop, the team notices remote members miss design conversations, so it adds recorded decision notes and scheduled collaborative modeling sessions.

## Where it breaks

Crystal’s flexibility can feel underspecified, particularly for inexperienced teams seeking concrete roles and events. Its classic emphasis on close or face-to-face communication requires thoughtful adaptation for distributed work. Tailoring can become an excuse for weak discipline, and high-criticality systems need rigorous assurance practices beyond a lightweight Crystal variant.

## Common mistakes

- Choosing a color or variant without assessing team size and system criticality.
- Using flexibility to avoid explicit working agreements and technical discipline.
- Assuming remote chat automatically provides the rich communication Crystal expects.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/crystal-methods/#visualization-crystal-methods>)

## Sources

1. [Introduction to Agile \(Crystal\) Methodologies](<https://www.cs.utep.edu/isalamah/courses/5389/Intro-to-Agile.pdf>) — University of Texas at El Paso · University course material
2. [Critical Factors: Select a Fitting Project Management Approach](<https://www.pmi.org/learning/library/select-fitting-project-management-approach-6915>) — Project Management Institute · Institutional research article
3. [Will Agile Development Change the Way We Manage Software Projects?](<https://www.pmi.org/learning/library/agile-development-change-manage-software-7717>) — Project Management Institute · Institutional overview

## Related topics

- [Extreme Programming](<https://wiki.soroush.uk/topic/extreme-programming/>)
- [Agile Product Development](<https://wiki.soroush.uk/topic/agile-product-development/>)
- [Dynamic Systems Development Method](<https://wiki.soroush.uk/topic/dynamic-systems-development-method/>)
