CSD vs CSM: Different Roles, Not Different Levels

CSM certifies the Scrum Master role: facilitation, coaching and serving a team. CSD certifies agile engineering practice: writing code the way a Scrum team needs it written. Neither is a step up from the other. The practical differences that decide it are that CSD requires hands on coding in the classroom, has no standardised exam, and is held by far fewer people than CSM.

Key Highlights

• These certify different jobs. CSM is for the person facilitating the team; CSD is for the people building the product.
• CSD requires at least 14 hours of formal training and assessment is set by the trainer, not by a standard exam.
• CSM has a fixed exam of 50 questions requiring 37 correct, so every holder passed the same bar.
• CSD classes are heavily hands on. Without current coding ability the course is difficult regardless of interest in the subject.
• CSM is recognised far more widely in job postings. CSD is a much smaller credential by holder count.
• Both renew every two years through SEUs and a fee.

What Each One Certifies

The confusion here is treating them as tiers of the same thing. They are not.

CSM covers the Scrum Master role: The framework, the accountabilities, the events, the artefacts, and how one person serves a team by facilitating, coaching and removing impediments. It assumes no technical background and asks you to write no code.

CSD covers agile engineering practice: Scrum Alliance describes it as demonstrating both an understanding of the framework and engineering skills for working in an agile environment. In practice that means the technical disciplines that make short iterations viable: test driven development, continuous integration, automated testing, collective code ownership and managing technical debt.

So the choice is not which certification is better. It is which of two different jobs you do. A Scrum Master taking CSD will spend most of the class writing code they will never write at work. A developer taking CSM will learn to facilitate events they will attend but not run.

If you are weighing the Scrum Master side, our free CSM practice test gives a quick read on where you stand.

Side by Side

Two rows carry most of the practical weight, and neither gets much attention in comparisons. They are covered next.

CSD Has No Standardised Exam

The difference most comparisons omit, and it matters for a specific reason.

Scrum Alliance states that CSD candidates demonstrate understanding through an assessment which may be an exam or an active classroom based evaluation, depending on how the course is designed. There is no single fixed test that every candidate sits.

For CSM the opposite is true. The exam is 50 multiple choice questions, 37 correct to pass, taken within 90 days of the course, and it is the same for everyone.

Three consequences worth understanding before choosing.

The CSD credential means slightly different things depending on where you took it: Two people holding it may have been assessed quite differently. That is not a flaw in the certification so much as a design choice reflecting that engineering competence is hard to test with multiple choice questions, and it does mean trainer selection matters more for CSD than for CSM.

You cannot fail CSD in the way you can fail CSM: Assessment is embedded in the course rather than sat afterwards, which removes the 90 day window and the resit anxiety that CSM carries.

Course quality varies more: With CSM the exam sets a floor on what was covered. With CSD the floor is whatever the trainer decided, so reading the specific course outline before booking is worth more here than it is elsewhere.

The details for a given course are set out in our guides to CSD certification prerequisites and the CSD certification process.

You Will Be Writing Code

The practical barrier people underestimate.

CSD classes are built around hands on programming. A substantial majority of class time involves writing code, pairing, and working through engineering practices on a real codebase rather than discussing them. This is the point of the certification, and it is also why it is unsuitable for anyone who does not currently write software.

The people who struggle are usually not those who lack interest. They are analysts, managers and Scrum Masters who found the syllabus appealing and arrived without the ability to keep up with a pairing exercise in an unfamiliar language. The subject matter is accessible; the format is not.

The honest guidance is that CSD suits developers with meaningful coding experience who want to formalise agile engineering practice. Someone earlier in a development career gets value from it, and someone not in a development role does not, however relevant the content sounds. Our guide to how to become a Certified Scrum Developercovers the route in more detail.

By contrast, CSM assumes nothing technical. It is regularly taken by people from delivery, business analysis, operations and management, and none of them are disadvantaged by not writing code.

The Recognition Gap

The most decision-relevant fact, and the one no comparison article states plainly.

CSM is one of the most widely held professional certifications in the agile field, and it appears constantly in Scrum Master job postings. CSD is held by a far smaller population and appears in job requirements much less often.

That is not a judgement about quality. It reflects that Scrum Master is a named role that organisations recruit for by title, so a credential attached to it becomes a screening filter. There is no equivalent job title for CSD. Organisations hire software engineers and rarely specify a Scrum development certification, so the credential is a differentiator rather than a requirement.

The practical implications differ accordingly.

If your goal is getting past application filters, CSM does that in a way CSD does not, because the postings name it.

If your goal is the capability, CSD teaches engineering practices that most developers never receive formal training in, and that value exists regardless of how many other people hold the certificate.

If you are unsure, search job postings in your market for both terms and count. That takes ten minutes and gives you an answer specific to where you work rather than a general claim.

A related point that cuts the other way. Because CSD is uncommon, it stands out on a developer's CV in a manner CSM does not on a Scrum Master's, since a large proportion of Scrum Master applicants hold CSM. Scarcity reduces recognition and increases differentiation at the same time, and which of those matters more depends on how you are being screened. If a keyword filter is reading your application, common wins. If a hiring engineer is reading it, uncommon and relevant can be the better card.

Salary data for the developer path is covered in our guide to Certified Scrum Developer salary, and as with most certifications the dominant factors are experience and location rather than the credential itself.

Which One to Take

The decision is usually simpler than the comparison suggests, because your job has generally already made it.

You are or want to be a Scrum Master: CSM. Nothing else applies.

You are a working developer on a Scrum team: CSD is the better match for your daily work, and it will teach you things CSM will not. Check how often your market names it before paying for it.

You are a developer wanting to move into a Scrum Master role: CSM, and start now. The developer background is an advantage in the role and the credential is what gets you considered.

You manage a team and want to understand what you are asking for: CSM. It covers the framework without assuming technical skill.

You are not currently writing code: Not CSD, regardless of how interesting the syllabus looks.

Your employer is paying and has a preference: Take theirs. It is usually tied to their environment, and the conversation is shorter than the analysis.

Facilitation, coaching and the accountabilities that sit behind the first of those paths are what CSM Certification Training is built around.

The Scrum Master roles and responsibilities guide covers what the first path involves day to day, and Scrum developer roles and responsibilities covers the second.

Can You Hold Both

Yes, and a small number of people do, usually developers who later moved into a Scrum Master role or team leads who work across both.

The sequence that makes sense depends on where you are starting. A developer intending to stay technical has no strong reason to add CSM, since the facilitation content will not be used. A developer moving toward Scrum Master should take CSM and can leave CSD unless the engineering content is independently useful.

Two practical points if you are considering both.

Each carries its own renewal cycle: Both run on two year cycles with SEUs and a fee, and holding two means two sets of obligations rather than a combined one. Details are in our guides to CSM renewal cost and CSD certification renewal.

The same learning can usually count toward both: SEU qualifying activity is broadly relevant across Scrum Alliance certifications, so the continuing education effort does not simply double even though the fees do.

What CSD Actually Teaches

Worth setting out, because the syllabus is the strongest argument for it and comparisons tend to summarise it as technical practices and move on.

Test driven development: Writing the test before the code. Genuinely difficult to learn from a book and one of the practices that benefits most from working through it with a trainer and a pair.

Continuous integration: Integrating to a shared trunk frequently with an automated build verifying each change. The discipline rather than the tooling, which is the part teams usually get wrong.

Automated testing beyond unit tests: What to automate, at which level, and how to keep a suite fast enough that people actually run it.

Refactoring. Improving structure continuously rather than deferring it to a cleanup Sprint that never arrives.

Collective code ownership: Any developer can change any part of the codebase, which removes the bottleneck of one person owning a module and being unavailable.

Managing technical debt: Recognising it, describing it in terms a Product Owner can weigh, and repaying it incrementally.

The reason this content is valuable is that most developers are never formally taught any of it. It gets absorbed unevenly on the job, and the gaps are usually invisible until a codebase becomes hard to change. A structured course with a practitioner trainer is a reasonably efficient way to close that.

It is also why the certification is a poor fit for non developers even though the topics sound broadly useful. Understanding test driven development conceptually is worth little; doing it under time pressure with someone watching is the part that changes practice, and that requires being able to code.

What CSM Teaches That CSD Does Not

For balance, since the developer syllabus above is concrete and the Scrum Master one often gets described in vaguer terms.

Facilitation: Running the four events so each produces something. Sounds procedural and is not: keeping a Retrospective honest when the team is defensive, or holding a planning session to its timebox when a Product Owner wants to keep talking, are learned skills.

The accountabilities in detail: Who decides what, and where the boundaries sit. Most workplace friction in Scrum comes from these being blurred, and knowing precisely where they fall is what lets a Scrum Master name the problem rather than manage the symptom.

Coaching a Product Owner: A large share of the job. Backlog ordering, saying no to stakeholders, and writing a Sprint Goal that means something are things Product Owners frequently need support with, and the Scrum Master is usually the person providing it.

Removing impediments: Including the organisational ones that sit above the team and cannot be solved by working harder inside it.

Protecting the team: From scope changes mid-Sprint, from pressure to drop quality, and from being reallocated across too many things at once.

The through line is that CSM content is about people and boundaries, where CSD content is about code and craft. Both are genuinely difficult, and they are difficult in unrelated ways. A developer who is excellent at test-driven development may be poor at holding a boundary with a senior stakeholder, and the reverse is equally common.

That is the clearest argument that these are not tiers of one credential. Nobody would describe learning to coach a Product Owner as the advanced version of learning continuous integration, or the reverse. They are separate skill sets attached to separate roles, and CSM Certification Training is built around the first of them.

Both Are Foundational

Worth stating clearly, because people sometimes assume CSD is the advanced version of CSM.

Scrum Alliance runs separate tracks with their own progression. The Scrum Master track runs from CSM through advanced and professional levels. The developer track runs from CSD through Advanced Certified Scrum Developer and onward in the same shape.

CSD is the entry point of the developer track, exactly as CSM is the entry point of the Scrum Master track. They are parallel, not sequential, and neither is a prerequisite for the other.

That structure is worth knowing when planning beyond the first certification, since the sensible next step depends on which track you are actually on rather than on collecting the other track's entry credential.

Misconceptions Worth Clearing Up

Five that come up repeatedly and lead people to the wrong choice.

That CSD is the advanced version of CSM: It is not. Both sit at the entry point of separate tracks, and neither requires the other. This is the single most common misunderstanding and it leads developers to take CSM first as a supposed prerequisite when they have no interest in the Scrum Master role.

That CSD is only for people who want to become Scrum Masters eventually: The developer track exists in its own right and progresses through its own advanced and professional levels. A developer can build an entire certification path without ever touching the Scrum Master track.

That the technical content of CSD is optional knowledge for a Scrum Master: Partly true and worth qualifying. A Scrum Master does not need to write tests, and understanding why a team without automated testing cannot sustain a Sprint cadence is genuinely useful. The understanding matters; the certification is an inefficient way to acquire it.

That holding both signals seniority: It signals two things were paid for. Interviewers respond to demonstrated capability, and a candidate with one certification and clear examples of applying it reads better than one with several and no stories attached.

That the certification is what teaches you: For CSD in particular, the value is concentrated in the hands on classroom time rather than the credential. Someone who attends, engages fully with the pairing exercises and never renews has probably extracted most of the value available. The certificate is a record that you were there.

That last point applies to both, and it is worth sitting with before spending on either. These are short courses. They give vocabulary, structure and a set of practices to try. The competence comes from applying them over months on a real team, and no certification shortens that part.

The corollary is that the choice between them matters less than the choice to actually change how you work afterwards. Someone who takes CSM and then facilitates a genuinely different Retrospective next week has gained more than someone who takes both and changes nothing.

Frequently Asked Questions

1. What is the difference between CSD and CSM?

CSM certifies the Scrum Master role, covering facilitation and coaching. CSD certifies agile engineering practice, covering test driven development, continuous integration and related technical disciplines. They are different roles rather than different levels.

2. Is CSD harder than CSM?

Different rather than harder. CSD requires coding ability and a substantial hands-on component. CSM has a fixed exam but assumes no technical background.

3. Does CSD have an exam?

Not a standardised one. Scrum Alliance states that assessment may be an exam or an active classroom-based evaluation, depending on how the trainer designed the course.

4. Do I need to be a developer to take CSD?

In practice yes. The classes are heavily hands-on, and people without current coding ability find the format difficult regardless of their interest in the material.

5. Which is more recognised by employers?

CSM, by a wide margin, because Scrum Master is a job title organisations recruit for. CSD is a much smaller credential and appears in job requirements far less often.

6. Can I take CSD without CSM?

Yes. They are separate tracks and neither is a prerequisite for the other.

7. How long is the CSD course?

At least 14 hours of formal training. Delivery varies by provider, and most run it as a live instructor-led course.

8. Do both certifications expire?

Both renew every two years, requiring Scrum Education Units and a renewal fee.

9. Is CSD the advanced version of CSM?

No. They are the entry points of two separate tracks. The Scrum Master track runs from CSM upward and the developer track runs from CSD upward, and neither is a prerequisite for the other.

10. I am a developer moving into a Scrum Master role. Which first?

CSM. The developer background is already an advantage in the role, and the credential is what gets you considered for it. CSD can follow later if the engineering content is independently useful to you.

11. Will CSD help me if my team has no automated testing?

Yes, and that is arguably the situation where it helps most, since the course covers exactly the practices the team is missing. The harder part is bringing them back to a team that has not agreed to change, which is a different problem from learning them.

Closing Thoughts

The useful framing for this comparison is not which certification carries more weight. It is which job you actually do, because these two credentials describe different work.

If you facilitate a team, CSM is the one. If you build the product and want formal grounding in the engineering practices that make short iterations sustainable, CSD is the one, and it will teach you things most developers never get taught.

Two things are worth checking before committing to CSD specifically: your comfort coding in a classroom setting, and how often employers in your market name the credential at all. Neither question is difficult to answer, and both are more useful than any general comparison including this one.

If the Scrum Master path is the one you are on, CSM Certification Training covers the framework, the accountabilities and the facilitation the role depends on. Request the curriculum to see the agenda and upcoming dates, or start with the free CSM practice test to find your gaps first. If you are a working developer and the engineering practices are what you want, CSD Certification Training is the equivalent starting point on the developer track.