Skip to main content

Becoming a Certified Scrum Practioner

Someone recently asked me what does it take to become a CSP. So I looked up the CSP requirements on the Scrum Alliance web page, to double check the requirements.

The CSP is the first rating in the Scrum Alliance structure that actually means something. A CSM has attended a class from a Certified Scrum Trainer (and starting October 1, will have passed a multiple choice test on Scrum). So a CSM is a trained apprentice.

A CSP is someone who actually has experience with Scrum. To become a CSP, you must provide evidence of at least one year of Scrum practice and be a member in good standing of the Scrum Alliance as a CSM or CSPO. The latter requirement means you must have taken a CSM or CSPO course from a Certified Scrum Trainer. You must have been doing Scrum for at least a year. You no longer have to wait 12 months after taking the CSM course - which is a sensible change. If you're the type who will read a book and then do Scrum, you probably have the right stuff to become a Practitioner, with or without the CSM Course.

Unlike other certifications, the CSP is not a multiple choice test which is graded to some arbitrary standard. It is a collection of 15 essay questions about how you have used Scrum in a real project, 5 questions about how Scrum works, and one question about how you have worked with the Scrum Community. It is reviewed by other Scrum Practitioners (If someone can give me better information about the process, please let me know).

So the CSP is a peer reviewed certification of people who have actually been doing Scrum. It means, you're now a journeyman ScrumMaster.

I became a CSP in August 2008. As I write this, there are some 60'000 CSM's and about 800 CSP's (and only 20 Certified Scrum Coaches, CSCs, the master level of certification).

The CSP hasn't really captured the attention of the marketplace, which is unfortunate, because these are the people who really know and do Scrum. I think the CSP is a way of demonstrating competence in and commitment to Scrum and should be recognized by the market.


charlie said…
Hi Peter, I'm a beggining scrum practitioner in Argentina. I was thinking to became in certified in scrum, but I don't know if I can do this here in Argentina or I have to do it somewhere else. Also I'm posting my experience implementing scrum in the electronic design in a factory here, its located in if you want to take a look. If you can recomend the best way to be certified, I'll appreciate it. Thank you very much.
Carlos Barroso
Peter said…
Hi Charlie, You can find a list of certified Scrum courses on the Scrum Alliance home page.

It looks like the nearest courses are in Sao Paulo, Brazil. As an alternative, you might contact a nearby Scrum Trainer, and see if you can convince him/her to offer a public course closer to home.

In any case, good luck!


Popular posts from this blog

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…

Explaining Story Points to Management

During the February Scrum Breakfast in Zurich, the question arised, "How do I explain Story Points to Management?" A good question, and in all honesty, developers can be an even more critical audience than managers.

Traditional estimates attempt to answer the question, "how long will it take to develop X?" I could ask you a similar question, "How long does it take to get the nearest train station?

The answer, measured in time, depends on two things, the distance and the speed. Depending on whether I plan to go by car, by foot, by bicycle or (my personal favorite for short distances) trottinette, the answer can vary dramatically. So it is with software development. The productivity of a developer can vary dramatically, both as a function of innate ability and whether the task at hand plays to his strong points, so the time to produce a piece of software can vary dramatically. But the complexity of the problem doesn't depend on the person solving it, just …

Money for Nothing, Changes for Free

“Money for Nothing, Changes for Free” encourages both customers and suppliers to focus on value.

A key advantage of Scrum projects is that at least once per sprint you have something that could be shipped and no work in progress. You can change direction every sprint, and you can reevaluate whether the project is a good investment or if your money could be better spent elsewhere. Abrupt cancellation is risky for the supplier.

While the concept of an early-exit penalty is not new, Jeff Sutherland gave it a unique allure with his allusion to the Dire Straits hit.
Desired Benefit Incentivize both customers and suppliers to focus on functionality that provides genuine value.
Structure This works with Agile software projects because there is little or no work in progress. After each Sprint, functionality is either complete or not started. Work is basically on a Time and Materials basis with a cost target, often with the intention that the project should not use up the entire project budge…