the blog for developers

ScrumMaster and ZenMaster: The joke of certification

Many people object to ScrumMaster certifications:

  1. It’s a money making machine
  2. Scrum Masters do not learn anything during classes
  3. The certification is nothing worth – because nothing is certified

I have been a Certified ScrumMaster (CSM) and a Scrum practioner for some years. People who object to the certification do see it from the wrong angle. You need to understand Zen to understand the goodness in CSMs.


Nénuphare
Creative Commons License photo credit: darkpatator

Certification is a Zen joke, because the role of a ScrumMaster cannot be certified. It’s not about knowing some technical questions. What should a trainer certify in such a class? That you can lead an agile Scrum team as a ScrumMaster? No one can certify the fact that you’re a leader, catalyst and enabler. You either are or you aren’t. Zen masters (ha, another master without a master!) would laugh at the fun in the ScrumMaster certification. They laugh about the idea of certifying enlightenment.

Scrum without ScrumMasters

As another parallel, both in Scrum and in Zen, masters are only enablers. They are not needed after the act of enabling Zen/Scrum. My Scrum trainer told me, the goal of a ScrumMaster is to make himself obsolete. There is a Zen koan which goes like this:

If you meet the Buddha, kill him.
— Linji

If you see a ScrumMaster, kill him. Zen tells you:

If you are thinking about Buddha, this is thinking and delusion, not awakening. One must destroy preconceptions of the Buddha. Zen master Shunryu Suzuki wrote in Zen Mind, Beginner’s Mind during an introduction to Zazen, “Kill the Buddha if the Buddha exists somewhere else. Kill the Buddha, because you should resume your own Buddha nature.”

If you think the ScrumMaster is Scrum, you’re delusioning yourself. In Scrum the product owner and the scrum team can, and should from my view, act by themselves, without the need of a ScrumMaster. The ScrumMaster helps them achieve their Scrum. Helps them overcoming initial obstacles in their productivity.

Kick your ScrumMaster
If the ScrumMaster is not good enough for them, certification and coaching inside the company hasn’t helped, the Scrum team has always the right to kick their SM if he isn’t good enough for them. And they should do so. If in Zen a master isn’t good, pupils will just leave him. This might lead to problems within the organization, especially if the ScrumMaster is their boss, but that should be the problem of the organization, not a team problem.

Practitioner certification

There are many more certifications from the Scrum alliance. If you dig deeper, the real fun part is that CSM doesn’t mean anything, practitioner means much more:

The practitioner level of certification (CSP) is only offered to those CSMs who have hands-on experience using Scrum. Applicants must complete an extensive questionnaire with probing questions that focus on applicants’ real-world experience using Scrum on software development projects. Their application is reviewed for answers demonstrating competence and comprehension of principles that can only result from hands-on work. The applicant may be questioned to determine eligibility. To maintain CSP status, you must submit a new application every two years.

Is the certification any use?

Yes. The Certified Scrum Master training has several merits:

  1. Calling the Scrum training “Certified” guaranties the quality of the trainer
  2. It motivates the Scrum master to think in Scrum
  3. If managers take part, it helps the organisation adopt a “we can do it” view about Scrum
  4. Certification (CSM) seems to be one of the main reasons for Scrum success in the enterprise. The certification makes Scrum compatible for managment.

The view about acceptance is shared by Peter Stevens:

It is also about branding, and has been quite successful. The acceptance of the CSM program is high (especially from corporate customers, and this is where the money is). I believe the CSM program is an important reason why Scrum is better accepted than say, XP, in corporate management circles.

Scrum is successful. I’ve seen it help development departments gain productivity. If you do not scrum yet, go for it.

You can leave a Reply here. Of course, you should follow me on twitter here.

You can share this post!
Do you want to tell others about this article? Use the social bookmark icons to submit this artice to the service of your choice. Thanks.

About the author: Stephan Schmidt has more than 15 years of internet technology experience and 10 years experience in agile. He was head of development, consultant and CTO and is a speaker, author and blog writer. He specializes in organizing and optimizing software development helping companies by increasing productivity with lean software development and agile methodologies. Want to know more? All views are only his own.
Leave a reply.

Comments

In my experience, most certifications have the issues you are describing.
Also technical certifications are mostly about branding and establishing corporate acceptance.
It is a lot like basic studies in university: You prove that you are able to trade your time and effort to achieve any objective. This makes you valuable in the corporate anthill…

This can be frustrating:
http://blog.jonasbandi.net/2008/09/certification-to-become-braindead.html

By the way isn’t Scrum out of fashion? The new kid on the block seems to be Kanban…

stephan

I think Scrum is very much “in fashion”. It’s over the first hill of the Gartner cyle (Slope of Enlightment). Many companies adopt scrum with good results (From my knowledge fewer Scrum adoptions fail than some years ago).

Scrum is Kanban (pull instead of push) from my understanding. At least for the development part. Kanban-pull needs to spread though. Customers need to pull features. The Kanban “line” is too short in most Scrum implementations.

And Poppendieck hasn’t arrived here in Germany yet. But lean is on the horizon.

(The most interesting part of Scrum for me is pull and lean)

smyd scrum,

I make money off of SCRUM because it is such bullshit. It is so hilarious. I read some books then I go to companies and fix their problem. Usually they problem is they aren’t actually following any process whatsoever. So I just give em more SCRUM. Sometimes it works.

You don’t need SCRUM, you need the ability to reflect and the an understanding of how to utilize process to improve your product.

Raoul Duke

(i’m also a CSM, although i have long since lost the diploma :-)

http://en.wikipedia.org/wiki/Dharma_transmission

I scenario I often come across is development companies that say “we are doing Scrum internally, we are only displaying a waterfall facade for our customer” …

In my opinion this is not possible, I suspect, that those people did not get what Scrum is all about …

What do you think?

stephan

@Jonas: I agree, they do not get Scrum.

This behavior is cargo-cult-Scrum.

From my experience Scrum is all-transforming, breaking up organizations, changing roles, flowing through everything in a company.

If it doesn’t, then the team will have perpetual impediments that are rooted in the current form of organization and which don’t go away. A permanent point of pain.

I guess in those cases Scrum fails sooner or later.

Well, as far as I experienced Scrum, the customer is an essential part of Scrum.
The customer himself has to understand the concepts behind Scrum and really believe and trust in those concepts.

If not everybody involved in a Scrum project is committed to Scrum it is not Scrum …

In a product-development project, the role of the customer can be represented by a member of the internal team. But when we are talking about customized enterprise software, I believe that it is not really possible to do it without the real customer/end user.

I had such an experience:
http://blog.jonasbandi.net/2008/10/scrum-pigs-musing-about-commitment.html

stephan

“Well, as far as I experienced Scrum, the customer is an essential part of Scrum.
The customer himself has to understand the concepts behind Scrum and really believe and trust in those concepts.”

Yes, the customer/product owner needs to believe in Scrum and trust the team. He needs to write the right stories with the right size and with top business value. He needs to channel and filter demands from outside the team.

Nowadays Scrum trainer make the point that a product owner might not be enough and a real user (XP!) should be part of the team. From my experience a good product owner should be a good substitute, although he’s tempted to implement his ideas instead of the customer needs.

Vitor BVS

I understand your point, but all about you said about certifications is valid not only for SMC. Many technologies have certifications and I’ve seen good professionals that don’t have one, and bad ones the have tons of shiny papers on their workstations.
In the end, your Zen approach would be nice if people started to destroy the certification paradigm too, and started to pay more attention to quality of the work being done.

Leave a Reply

What people wrote somewhere else:

Additional comments powered by BackType

Guide to CodeMonkeyism

Over the last 4 years I wrote many articles on this blog. To make it easier for you to find the relevant ones, I've organized them into topics.

Top 10

6 reasons why my VC funded startup did fail

Go Ahead: Next Generation Java Programming Style

Java Interview questions: Write a String Reverser

The dark side of NoSQL

7 Bad Signs not to Work for a Software Company or Startup

Is Java dead?

Scala vs. Clojure

Never, never, never use String in Java

No future for functional programming in 2008 – Scala, F# and Nu

Clojure vs Scala, Part 2

Java Developer

Is Java Dead?

Go Ahead: Next Generation Java Programming Style

Be careful with magical code

All variables in Java must be final

Never, never, never use String in Java

Bending Java: More readable code with methods that do nothing?

NoSQL Guy

NoSQL: The Dawn of Polyglot Persistence

The dark side of NoSQL

Essential storage tradeoff: Simple Reads vs. Simple Writes

Sharding destroys the goals of your relational database

The unholy legacy of databases

Startup/CTO

Development Dream Teams

6 reasons why my VC funded startup did fail

American vs. European style of Software Development

12 Things to Reduce Your Lead Time and Time to Market

The high cost of overhead when working in parallel

Essential storage tradeoff: Simple Reads vs. Simple Writes

Job Seeker

Another Good (Java) Interview Question

7 Bad Signs not to Work for a Software Company or Startup

Java Interview questions: Write a String Reverser (and use Recursion!)

Java Interview questions: Multiple Inheritance

As a Manager: What I value in developers

Top 10 Tips (+1) to Get a Pay Raise

Agilist

What Developers Need to Know About Agile

5 Practices Better to Change in Your Scrum Implementation

Scrum is not about engineering practices

ScrumMaster and ZenMaster: The joke of certification

What is Trans-Scrum?