How It Compares
How Harmonic Composition fits alongside Scrum — what it adds, where the two coexist, and how to start applying it without abandoning your current process.
How It Compares
Harmonic Composition is not a replacement for Scrum. It addresses the parts of delivery that Scrum intentionally leaves open — context preservation, durable capability definitions, and an explicit destination. Teams running Scrum daily will recognize the problem it solves.
What Scrum solves — and what it leaves open
Scrum is excellent at organizing a team's execution rhythm: the sprint cycle, the daily sync, the retrospective, the review. It defines who is accountable for the backlog, who owns the team process, and how often work gets checked. These are real, hard problems and Scrum solves them well.
What Scrum does not prescribe is what sits above the backlog: the reasoning behind the work, the destination the team is converging toward, the decisions that shaped which stories were written the way they were. A Product Backlog tells you what to build next. It does not tell you what the system needs to be capable of doing — or why.
The result, after two or three years on a live product, is a team that has shipped many sprints but cannot answer the question: "What are we building toward, and why did we make the choices we made to get here?"
Harmonic Composition fills that gap. It does not replace the sprint; it gives the sprint a destination and gives the team a way to preserve the reasoning that got them there.
How the concepts map
These are approximate analogies, not equivalents. Scrum and Harmonic Composition solve different problems, and the metaphors break down at the edges.
| Scrum | Harmonic Composition | Where the analogy holds — and where it breaks |
|---|---|---|
| Product Goal | Coda | Both define a destination for a phase of work. The difference: a Coda is explicitly phase-scoped and evaluated before Beats begin. The Product Goal is often implicit or aspirational. |
| Product Backlog item | Beat | Both represent work the product needs. The difference: a Backlog item closes when it ships. A Beat persists as long as the capability matters — it accumulates versions over time rather than being deleted. |
| Sprint Backlog item | Beat Version | Both represent a planned increment of near-term work. A Beat Version is more structured: it carries a description, explicit scope, and binary acceptance criteria. |
| Sprint | Revision | Both are time-bounded delivery units. A Revision is PR-scoped (one pull request) rather than time-boxed — it ships when it ships, not when the two weeks end. |
| Definition of Done | Quality gates | Both define when work is considered complete. Harmonic Composition's quality gates apply at the Beat level (is this capability well-defined?) and at the Beat Version level (is this increment well-planned?) before delivery begins. |
If the analogy breaks down, trust the definition on the concept page. These are comparison handles, not technical equivalents.
Where they coexist
Harmonic Composition does not replace Scrum's team ceremony or sprint cadence. A team can — and many do — run both.
The sprint review still happens. The retrospective still happens. The daily standup still happens. What changes is what the team brings to those ceremonies: instead of a backlog of tickets, they have a set of Beats that describe durable capabilities, a Coda that describes the destination for the current phase, and Notes that explain the decisions behind the work.
Sprint cadence and team ceremony. Daily coordination. Stakeholder review rhythm. Team accountability (PO, SM, Dev team). Incremental delivery pace.
Explicit phase destination (Coda). Durable capability definitions (Beats) that persist beyond sprint closure. Versioned context (Notes) that survives team changes. A planning layer (Beat Versions) that sits above individual stories.
In practice: Beats replace the long-lived epics that tend to pile up in backlogs and never close. Beat Versions replace the sprint goal when it needs to be more precise. Notes replace the "tribal knowledge" that walks out the door when a senior engineer leaves.
If you use Scrum and want to try this
You do not need to change your sprint process to apply Harmonic Composition. Three entry points that work alongside a running Scrum team:
1. Write a Coda for your next sprint planning session. Before the next sprint planning, spend 30 minutes writing a specific, phase-scoped destination: what does the product need to be capable of doing by the end of this quarter? That is a Coda. Check your proposed sprint goals against it.
2. Rewrite your top three epics as Beats. Take three long-lived epics from your backlog — the ones that have been open for more than six months — and rewrite them as outcome-oriented Beats. A Beat describes what the system must be able to do, not what needs to be built. See Beats for examples of the before/after transformation.
3. File one Note after your next decision. The next time your team makes a significant decision — a technical choice, a product tradeoff, an architectural constraint — write it down as a Note with its rationale. Not in Slack. In the system. That is how the context starts to accumulate.
None of these require switching tools or changing your sprint cadence. They are additions to your existing process, not replacements for it.
Start applying Harmonic Composition →Vibe Coding
Vibe coding means building software by prompting AI agents conversationally rather than writing code by hand. It is fast for prototypes — but at enterprise scale it needs structure. Harmonic Methods is how enterprises keep the speed without losing control.
About
The history and motivation behind Harmonic Methods, created by Mike Merchant, Founder and CEO of Codazen.