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.

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…

Five Simple Questions To Determine If You Have the Agile Mindset

My company has started a top-down transition to Scrum and Kanban. Will that make us an Agile company? About 2 years ago, I attended a conference hosted by the Swiss Association for Quality on the topic of Agility. As a warm-up exercise, the participants were given the 4 values of the Agile Manifesto, then asked to arrange themselves in space. How Agile is your company? How Agile do you think it should be? Very Agile on left, very traditional on the right. There was a cluster of people standing well to the right of center. “Why are you standing on the right?” It turns out that they were all from the railway. “Our job is to run the trains on time.” They were uncertain whether this agility thing was really aligned with their purpose.
Is Agility limited to software? Steve Denning has collected the evidence and laid out the case that Agile is not limited to software, nor is it merely a process, nor is it something you can do with part of your time, nor is it something you can have your …