Skip to main content

More tips for CST Aspirants

What does it take to become a Certified Scrum Trainer (CST)? Passion and Energy. You should stand out from the crowd!

Aspirant: How high do we have to climb?
TAC: What we really want is someone who can leap tall buildings in a single bound!
The Scrum Alliance Trainer Acceptance Committee held its first ever workshop for CST Aspirants last week at SGPHX, the Phoenix Scrum Gathering. This gave candidates a chance to ask questions and understand what is really expected of a CST to get through the final examination.

The answers to two questions really stood out for me in this workshop:

  • Why do I have to submit my own learning materials?
  • How many students must I have taught?


Why do you have to submit your own learning materials?

Many Aspirants today work for a company that has already created a "deck" for teaching Scrum. I am told that Scrum.org even requires their trainers to train to a standardized deck. Why reinvent the wheel? 

If an Aspirant is using someone else's materials, here is a typical conversation during the final interview:
  • Examiner: What does this diagram on page 35 mean?
  • Aspirant: <dances around the question without really answering it>
  • Examiner: Try again. What does it really mean?
  • Aspirant: I'm not sure. It's something the company put in, but I don't really use it in my course.
A CST must know their stuff! A CST should not be training materials that they do not understand or support fully. If you don't create it, it's almost impossible to learn it well enough to teach from it effectively and without blind spots.

How many students must you teach?

The Scrum Alliance requires an Aspirant to have taught at least 100 students in CSM-like context (2 day course). This should demonstrate that you are capable of doing the job of a CST. 

Does training 100 students guarantee that you will be accepted? No.

The Scrum Alliance wants its trainers to come from the top 1%. That top 1% are the people who motivate and convince others to want to do Scrum and do it well. You're job is to convince the TAC that you belong there already, so all they have to do is recognize your accomplishment!

A CST is not merely a trainer. A CST is an ambassador of Scrum. So the criteria on the Scrum Alliance website are perhaps best to be understood not as acceptance criteria, but as exclusion criteria. If you don't meet these criteria, don't bother applying. If your objective is simply to satisfy the absolute minimum requirements necessary, then you probably haven't understood what being a CST is really about, and are therefore unlikely to pass.

What does it take to become a CST?

Above all else, perseverance! Don't give up. Not everyone makes on the first try. I needed four tries, an extreme case, to be sure, but many need two tries to get through, and some very good trainers even needed three. Passion, energy, and perseverance! 

P.S. To my padawans who came up for evaluation in Phoenix: Congratulations and high fives to Joe Justice! Joe needed two tries to get through. And to Lizzie Morris, I say don't give up! Both of you are awesome trainers who deserve to be recognized as such!

P.P.S. Are you a CST Aspirant? If are on the path to becoming CST, check out our network


Comments

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 …