Cockburn grades projects by the worst probable effect of an unremedied defect, from loss of comfort to loss of life (Agile Software Development, 2001). The Scrum Guide (2020) has no equivalent input, and that gap is the cleanest way to tell the two methods apart.
Scrum fits a single team that can put its work into a backlog. Crystal Clear suits a small team that shares a room and wants the lightest process that still delivers often.
Past that, it comes down to how much each one dictates. Scrum fixes its accountabilities, events and artifacts. Crystal is a family of agile methods whose rigor rises with team size and project criticality.
What is the difference between Scrum and Crystal methodology?
Scrum comes as a prescribed framework, built around time-boxed sprints with fixed accountabilities, events and artifacts. Crystal is a family of methodologies, color-coded by team size and project criticality, and it puts people and communication ahead of process.
The Scrum Guide calls Scrum lightweight, yet it also says that implementing only some of its parts doesn’t count as Scrum (Scrum Guide, 2020).
Crystal runs the other direction. Cockburn defines it by properties a team has to reach, and the procedures for getting there are the team’s call.
Both belong to the wider family of agile methods, which is the only reason they get compared at all. The values are shared. The amount each one dictates is not.
| Attribute | Scrum | Crystal |
|---|---|---|
| Created by | Ken Schwaber and Jeff Sutherland | Alistair Cockburn |
| Structure | Fixed accountabilities, events, artifacts | Properties first, practices tailored |
| Team size | Typically 10 or fewer | Rises with color, from about 6 to 8 for Clear |
| Criticality | Not a Scrum Guide factor | Four bands, comfort to life |
| Cadence | Fixed Sprints, one month or less | Frequent delivery, length set by the team |
| Communication | Daily Scrum, 15 minutes | Osmotic, in a shared space |
Boiled down, Scrum orders work by backlog priority, while Crystal decides how much rigor a project gets by looking at its criticality.
Who created Scrum and Crystal, and when?
Ken Schwaber and Jeff Sutherland developed Scrum in the early 1990s, according to the Scrum Guide, and Alistair Cockburn built Crystal in the same decade. All three later signed the Agile Manifesto at Snowbird, Utah, in February 2001 (Agile Alliance).
Scrum’s team idea traces back to a 1986 Harvard Business Review paper by Takeuchi and Nonaka, which compared product teams to rugby. Schwaber and Sutherland first presented it at OOPSLA in 1995. The first Scrum Guide appeared in 2010, and the current edition is dated November 2020.
Crystal started somewhere else entirely. IBM Consulting Group hired Cockburn in the early 1990s to document a methodology for object-oriented development, so he interviewed project teams and wrote down what they said made projects succeed or fail.
The Crystal family grew out of that record. Cockburn published the detail in Agile Software Development (2001) and Crystal Clear (2004).
Scrum documents a working pattern and names its rules. Crystal catalogs what successful teams already did, and the rules stay loose.
How Scrum is put together
The 2020 Scrum Guide defines Scrum through 3 accountabilities, 5 events and 3 artifacts, and each artifact is tied to one commitment. Everything runs inside the Sprint, a fixed-length container of one month or less.
The guide says “accountabilities”, not “roles”. It also dropped the separate Development Team, so the people who build the product are simply the Developers.
The Product Owner orders the Product Backlog and owns the Product Goal. Developers own the Sprint Backlog and create a usable Increment every Sprint. The Scrum Master’s job is to establish Scrum and remove impediments to the team.
The Sprint contains four formal events, and together the five Scrum events give the team its inspection rhythm.
| Event | Purpose | Maximum time (one-month Sprint) |
|---|---|---|
| Sprint | Container that turns ideas into value | One month or less |
| Sprint Planning | Set the Sprint Goal and select work | 8 hours |
| Daily Scrum | Check progress toward the Sprint Goal | 15 minutes |
| Sprint Review | Inspect the outcome with stakeholders | 4 hours |
| Sprint Retrospective | Plan ways to improve quality and effectiveness | 3 hours |
Shorter Sprints get shorter events (Scrum Guide, 2020).
Each artifact carries a commitment that keeps the work visible to everyone inspecting it. The Product Backlog commits to the Product Goal and the Sprint Backlog to the Sprint Goal. The Increment commits to the Definition of Done.
Plenty of comparison pages still describe the 2017 guide. That edition sized the Development Team at 3 to 9 people (Scrum.org), where the 2020 edition sizes the whole Scrum Team at typically 10 or fewer.
Crystal’s color-coded family and its properties
Crystal is a family of agile methods in which a color marks how many people work on the project and how much damage a defect could do. Lighter colors suit small teams and low-criticality work, and darker colors suit larger or riskier projects.
Crystal Clear
Crystal Clear is the lightest variant, built for small teams that sit together. Cockburn set it out in Crystal Clear: A Human-Powered Methodology for Small Teams (2004).
He lists seven properties that the best teams set up:
- Frequent delivery
- Reflective improvement
- Osmotic communication
- Personal safety
- Focus
- Easy access to expert users
- A technical environment with automated tests, configuration management and frequent integration
Crystal Clear requires only the first three. The other four move a team further into what Cockburn calls the safety zone (Crystal Clear, chapter 2).
The last property is the tooling one. It asks for automated tests, tracked builds and configuration management so any teammate can reproduce a working version.
Frequent integration is what most teams now call continuous integration, merging and testing code in small, regular steps.
Osmotic communication is the one property Cockburn says does not apply to projects of every size. It assumes the team sits close enough to overhear each other.
Crystal Yellow, Orange and Red
Published team-size ranges for the colors disagree, starting with Clear itself.
| Variant | ToolsQA | Zartis |
|---|---|---|
| Crystal Clear | 1-6 people | Up to 8 people |
| Crystal Yellow | 7-20 people | 10-20 people |
| Crystal Orange | 21-40 people | 20-50 people |
| Crystal Red | 40-80 people | 50-1000 people |
monday.com gives 2-6, 7-20 and 21-40 for the first three colors, so it matches ToolsQA on Yellow and Orange but starts Clear at 2 people.
ActiveCollab prints two sets of figures in the same article. One list says up to 8, 10-20, 20-50 and 50-100, which sits close to Zartis except for Red. Another says 7-20, 21-40 and 40-80 for Yellow, Orange and Red, which matches ToolsQA.
Cockburn prefers to call Crystal Clear a methodology generator, so the numbers read as starting points for tailoring, not cutoffs.
Yellow teams typically add progress tracking and early risk checks on top of Clear (monday.com). Beyond Red sit Maroon, Diamond and Sapphire for the largest or life-critical projects, and the published summaries do not agree on how those map either.
Team size and criticality decide the fit
Crystal reads two inputs before it picks a color: how many people work on the project and how much damage a defect can cause. Scrum reads neither, because the Scrum Guide offers one structure for every Scrum Team.
Cockburn formalized both inputs in the Cockburn Scale, published in Agile Software Development (2001). Criticality is the worst probable effect of an unremedied defect, and size is the number of people on the development staff.
The scale has 4 criticality bands: loss of comfort (C), discretionary money (D), essential money (E) and life (L). The most common size values are 6, 20, 40, 100 and 200 people. Two examples show how the labels read. L6 is a two-person, life-critical project, and D100 is a 50-person project whose failure could hurt profits but not threaten the organization’s survival.
The size columns are labeled by their upper bound, so the four that map to Clear through Red run roughly 1-6, 7-20, 21-40 and 41-100 people. The first three line up with the narrower ranges ToolsQA gives for Clear, Yellow and Orange. The Red column tops out at 100, far below the 1000 Zartis gives for Red.
Cockburn’s own practice bends the columns. In Crystal Clear (2004) he describes Géry Derbier’s 25-person team at La Poste, building software for a mail facility in northern France, and places it in the Crystal Yellow category.
The team stretched Crystal Clear to fit its size. Its contract paid on integrated test results every few months, so frequent delivery drove the billing.
A 25-person team sits above the size the Scrum Guide describes as typical, yet inside a color Cockburn assigned himself. Treat the size columns as guides, and let criticality carry more of the decision.
Cockburn says project classes toward the larger, more critical corner of the grid need more formal process. Crystal’s weight therefore rises along two axes, while Scrum’s weight stays where the guide fixes it.
Cadence, process weight and communication compared
Scrum fixes the rhythm and prescribes the meetings. Crystal fixes the properties and leaves the rhythm and the meetings to the team.
Iteration cadence
Cockburn puts a Crystal Clear iteration anywhere from an hour to three months in principle, and two weeks to two months in practice (Crystal Clear, 2004).
For Crystal, delivery to real users counts for more than the iteration itself. Cockburn found no gap longer than four months that still keeps a project safe, with two months safer and web teams delivering weekly.
Scrum treats the iteration as the fixed unit. The Scrum Guide still lets a team deliver an Increment before the Sprint ends, though, and it says the Sprint Review is never a gate to releasing value.
Both methods fix the end date of an iteration and keep release separate from it. What differs is which clock gets the cap. Scrum caps the iteration, and Crystal caps the gap between deliveries.
Process weight and documentation
Scrum’s weight is set by the guide, which warns that leaving out elements covers up problems. Crystal’s weight is set by where the project lands on the Cockburn Scale.
Crystal Clear leaves most conventions unstated for the team to finalize, and reflection replaces most prescribed process. Seating, iteration length and the timing of tests all stay open to change.
Cockburn says an hour every few weeks or once a month will do for that reflection. It does the job the Sprint Retrospective does in Scrum, without a prescribed format, and he rates the format as less important than the fact that the team holds one.
Project Ingrid shows what a reflection workshop can do. After a first iteration planned at four months overran, the team released 23 of its 24 client-side programmers and hired 23 new ones, and it was ahead of schedule by the fourth iteration (Crystal Clear, 2004).
Communication model
Cockburn’s test for osmotic communication is whether a question reaches the person who might answer it in 30 seconds or less, which a shared room makes possible.
| Aspect | Scrum | Crystal |
|---|---|---|
| Daily sync | Daily Scrum, structure chosen by Developers | Overheard conversation in a shared room |
| Growing team | Split into several Scrum Teams | Osmotic inside subteams, close communication across them |
| Distance | Events share a time and place when possible | No osmotic communication seen without physical proximity |
The Daily Scrum schedules what a shared room does by accident. Cockburn counts adjacent rooms with two or three people each as keeping many of the benefits.
Where Scrum and Crystal stop working
Scrum breaks down when one Product Owner cannot order the work or the team will not adopt the full framework. Crystal breaks down when the team cannot sit close together or cannot supply the properties itself.
On the Scrum side, partial adoption is the obvious one. The Scrum Guide says implementing only parts of Scrum is possible, but the result is not Scrum. Large products hit a second wall, since the guide’s answer to a team that grows too big is several Scrum Teams sharing one Product Goal, one Product Backlog and one Product Owner.
That ties into the third problem. The Product Owner is one person, not a committee, so every ordering call for the product runs through that person, and the shared Product Backlog keeps a single owner no matter how many teams work from it.
Crystal’s weak spot is distance. Cockburn has yet to see osmotic communication achieved without physical proximity, and it only really works with small teams anyway.
Team skill matters too. Crystal Clear leaves details to the team, so a team that cannot choose working conventions has nothing to fall back on. And politeness gets mistaken for safety more than you’d expect: a team can look safe while hiding disagreement, and mistakes then go uncaught.
Life-critical or regulated work adds another problem, software compliance. Neither method ships with a mapping to regulatory requirements.
AAMI TIR45 fills that gap for medical device software. It debuted in 2012, and AAMI reissued it as a second edition in 2023 to align agile practices with FDA 21 CFR 820, ISO 13485 and IEC 62304.
Cockburn’s L6 example shows the Crystal side of the same problem. Two people is small enough for Crystal Clear on size, but a life-critical project needs a heavier process than Clear provides.
Which should you pick, Scrum or Crystal?
Go with Scrum when one team can own a product with an orderable backlog and the cost of a defect is moderate. Go with Crystal Clear when a small team sits together and wants the lightest process that still delivers often.
Scrum is the default and the safer pick for a team that wants its routine prescribed. A small, co-located team that finds that routine heavy has a real alternative.
Most cases settle in a fixed order. Start with criticality, meaning where the project lands from C to L on the Cockburn Scale. Then look at size and whether one team can own the product or it needs several. After that, ask whether the team shares a room (or at least adjacent ones), and finally whether it wants its events and cadence prescribed.
High criticality overrides everything else in that list. At E or L, start from the compliance requirements and fit the method around them.
Pros and cons of Scrum
Scrum gives a team a shared vocabulary and a fixed rhythm of inspection. It also keeps extra meetings down, since the defined events replace them (Scrum Guide), and ownership of the backlog is never in doubt.
The downsides are real, though. It works as written or not at all, it takes no criticality input, and growth means more teams on one backlog.
Pros and cons of Crystal
| Pros | Cons |
|---|---|
| Tailored to team and project | Details left to the team to choose |
| Weight rises with criticality | Osmotic communication needs proximity |
| Delivery to users anchors the work | Sources disagree on color boundaries |
How to get started
- Classify the project on the Cockburn Scale by size and criticality.
- For E or L work, map the method to the applicable compliance standards before the first iteration.
- Choose Scrum, or the Crystal color that matches the size and criticality.
- Run the first iterations with a fixed end date and deliver something to real users.
- Hold a reflection session after each cycle and keep or change conventions based on what it shows.
If neither method fits, other software development methodologies are worth a look before the team commits.
Scrum vs Crystal Methodology FAQ
Can you combine Scrum and Crystal?
Yes, at the practice level. The Scrum Guide calls Scrum a container for other techniques, and Crystal Clear accepts any procedure that produces its seven properties.
The limit is the guide’s own rule. A team that drops Scrum elements is no longer running Scrum.
Is Crystal methodology still used today?
In some places, yes. Cockburn wrote in October 2024 that Crystal has been used successfully since 1998, and that Clear, Yellow and Orange cover teams up to about 50 people.
He adds that interest returns whenever a dominant framework crowds out lighter options.
Which is more widely used, Scrum or Crystal?
Scrum. Digital.ai’s 17th State of Agile report (2024) found 63% of agile teams run it, the most widely adopted methodology in the survey.
The 18th report (2025) dropped the team-level framework question, so no newer comparison exists.
Is there a Crystal certification like the Scrum Master one?
Not from its creator. Cockburn publishes no counterpart to Scrum.org’s PSM I, an 80-question, 60-minute online assessment with an 85% pass mark.
Any Crystal credential on offer comes from a training provider.
Switching Between Scrum and Crystal Mid-Project
Switching between Scrum and Crystal costs least at an iteration boundary. The Scrum Guide bars changes that endanger the Sprint Goal, so a mid-Sprint change is the expensive one.
The order that follows from that is simple. Finish the running Sprint or delivery cycle, re-grade size and criticality on the Cockburn Scale, and start the new method at the next boundary.
Cockburn’s four-month ceiling between deliveries leaves room for the move. A Scrum team on one-month Sprints that releases at least every third Sprint already stays inside it, so frequent delivery survives the switch.
The price is judgment. Crystal Clear hands the team the ordering and convention decisions that the Product Owner and the fixed events settle in Scrum.
This position rests on the November 2020 Scrum Guide and Cockburn’s October 2024 write-up, verified in October 2026. A new Scrum Guide edition would change the Scrum side.
A team that stays on Scrum can study the full Scrum framework before its next Sprint Planning.
- MongoDB Cheat Sheet - October 20, 2026
- Adding AI Video Generation to a Software Product: Architecture, Cost Guardrails and QA - October 20, 2026
- Show Hidden Characters, Spaces, and Line Endings in Notepad++ - October 19, 2026
