Skip to main content

Tips for CST Aspirants

So you want to become a Certified Scrum Trainer? What does it take to become a CST? I facilitated a workshop at the Phoenix Scrum Gathering (#SGPHX) on the challenges of becoming a trainer. Several people shared their experiences, including current and former members of the TAC (Trainer Acceptance Committee) and Tirell Payton, a Certified Scrum Coach whose first attempt at passing the TAC was not successful. 

Tirell wrote the following summary, which I thankfully quote:

During the retreat Peter Stevens facilitated a session on the CST process and some of the potential pitfalls the aspirants encounter as they go through the process.

I acted as the scribe and town crier, and as such lots of people have come up and asked me for my list of items.  The items on the list follow 2 key dimensions:  The common items that lead to candidates not being accepted and advice for how to make it through the process with your sanity intact.

For those of you on the list, hopefully these items will be helpful to anyone you're mentoring through the process.  Tomorrow at the gathering if anyone has any questions on these items, I am willing to give advice and share my experiences.

Some of the items that are a challenge for applicants:
  • Knowledge.  Know your stuff backward and forward.  Even better, be able to communicate it clearly and succinctly
  • Community Involvement.  The TAC really likes to see a breadth of community involvement
  • In person techniques.  Context matters, be mindful of the fact that when you are in front of the TAC review, some techniques that work very well in the context of a 2 day training course may not work well at all in your TAC panel session.
  • Personal Statement.  The TAC wants to understand how you will make an impact as a trainer. Becoming a CST is just as much an affirmation of your passion and commitment as well as a platform for you to go on to greater heights.  How will you change people's lives in 2 days?
  • Co Training.  The TAC wants to see very good evidence that you have co-trained with CSTs.  Yes its difficult, yes its hard to coordinate schedules, but its very worthwhile.  Co-training depends your connection with your training community, spreads effective techniques, and provides an opportunity to observe stylistic differences.

Some of the advice from the session:
  • Don't give up.  If you don't get through on the first try, understand you are not the first person that this has happened to.  
  • Be accepting of feedback.  Listen.
  • Treat it like a job interview with the same level of professional discipline and focus
  • Ask and ye shall receive.  Make yourself visible in the community.  Help.  Enlist others to be co-conspirators in your success.


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…