Skip to main content

Scrum Certification Exam required after Oct. 1

I just got this from my CST mentor and co-trainer Andreas Schliep:
Currently, an individual is certified when he or she has attended, participated in, and completed a Certified ScrumMaster course.

Effective 1 October 2009, all CSMs will be required to complete a Certified ScrumMaster course and pass a Certified ScrumMaster (CSM) online certification exam [in English, ed.] to maintain certification.  Click here for the Exam Objectives or Click here for the Exam Administration and Retake Policy.
They seem to really mean it this time.

Personally, I have mixed feelings about the exam. On the one hand, being required to demonstrate some basic understanding of Scrum before getting the certification seems like a good thing.

One the other hand, the value of the Scrum course lies in its experiential nature. Yes, you learn facts and theory, but you spend a lot of time "in motion": doing games, simulations, exercises, working out problems with your teammates.

I think there is a very great danger that the CSM exam will change the emphasis of the CSM course from experiencing Scrum to preparation for passing the test.

Some people might feel the certification deadline is a reason to take the CSM course in September...

Erratta

My calendar for courses has wrong dates for the December courses:
  • The CSM for Advanced Users with Andreas is on December 3 & 4, not 2 & 3
  • The Practical Product Owner Course is December 10 & 11, not 9 & 10.
A corrected Scrum course calendar is now online.

Comments

As of October, my resume will state "ex-CSM". I don't have time to waste on test training... I'd prefer more experience.
Peter said…
I suppose you could wait until your membership expires before writing Ex-CSM :-)

For my part, I'm going to take a wait and see attitude. I wonder how many people will actually take the test.

Popular posts from this blog

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

10 Warning Signs, that your team is not self-organizing

How do you know that self-organization is working? The Bern Chapter of Scrum Breakfast Club looked into this questions, and identified the following warning signs (which I have taken the liberty of translating).

The team reports to the Scrum Master at the Daily ScrumPeople wait for instructions from the Scrum MasterTeam members don't hold each other responsible [for their commitments]The same impediment comes up twice"That's the way it is" => resignation"I" instead of "We"Flip charts are lonelyCulture of conflict-avoidanceDecisions processes are unclear, nor are they discussedPersonal goals are more important than team goals
To this list I would add my a couple of my favorites:
you don't see a triangle on the task board (not working according prioritization of stories)after the daily Scrum, people return directly to their desks (no collaboration)there are a least as many stories in progress as team members (no pairing)
P.S. You can join the …