Skip to main content

Certified Scrum Practitioner

I received a nice email today from the the Scrum-Alliance, Subject: CSP Application Approved (and Next Steps). So what does it mean to be a Certified Scrum Practitioner? How do you become a CSP?

The process for applying is relatively simple. After you have been a CSM for a year, you download the form, answer the questions and send it in. They only ask for money when your application is approved. (+1 for customer friendliness -- that was the item "Next Step" in the E-Mail.).

The application "form" -- template would be a better word -- consists of 14 essay questions about a particular Scrum project, 5 questions about Scrum in general, and one question about your work with other Scrum Masters to promote Scrum and the Scrum Communitity.

So a CSP is expected to
  1. Have actually worked with Scrum in a real project
  2. Really understand Scrum ("get it")
  3. Promote Scrum
  4. Be able to write coherently about Scrum and his/her experience with Scrum.
This last two criteria makes the CSP different from any multiple choice based certification, which can be evalulated by a computer. Somebody has to actually read the application.

Value of the CSP

A certification can offer value in many ways. It can:
  • improve your market value/be prerequisite for certain jobs
  • recognition for your skill
  • be a step on a career path
How does the CSP measure up?

Market Value: There are some 25'000 CSMs out there and only about 800 CSPs. So there is some exclusivity in being a CSP. But... a search of Monster.com produced exactly 59 jobs for a Scrum Master, 7 jobs postings requiring a CSM. I found one requiring "CSP equivalent", but it had expired. Conclusion: doesn't appear to be a career move. Of course, I'm not looking for a job, but rather coaching and training assignments, so the estimate of market value is even harder to judge.

Skill Recognition: Yes, somebody has read my application and said effectively, "you're doing good, keep up the nice work". Of course, I already knew that, but it's nice to get some warm fuzzies from the Scrum Alliance confirming that. That there are only 800 people worldwide who have taken this step is also nice. Of course, there are many more than that doing Scrum at high level without the stamp of approval.

By comparison, the German language Project Managment Forum in Xing has over 32'000 members. Don't have any figures on actual, PMP or ITIL certifications, but it seems it must be a much larger number.

Career Path: Since the change in the qualifications for becoming a Certified Scrum Trainer (CST), the CSP is a stepping stone to becoming as CST. This is where I see the major value. I like giving courses and look forward to becoming a CST.

So its done and is worth celebrating. I will bring a some Prosecco to the September Scrum Breakfast to toast this step forwards. Hope to see you there!

Comments

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…

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…

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 …