The CST journey

Tips & Tricks

The first things to learn :)

 

  1. This is not a checklist!
  2. The whole application has no a checklist
  3.  Becoming CST is a journey, not a process
  4.  Try to see and understand the TAC, how they can get an easy about you, if they do not know you yet...
  5.  Keep it short, the more concise you can be, the better.
  6.  If you really want, you can do it, never give up!

To become a CST, you have to find your own way. These are just ideas and hints that can be helpful. Do all of this does not mean it will be enough or good...

These are notes from TAC members and the CST that I collected during talks and discussion with them in person and in conferences...

Electronic documents must be in MS Office and/or PDF format. These documents must be compressed in a Zip file identified with your name and address. All documents must be in English.

Keep a simple file name and maybe separate additional materials. That will support the application...

If you have some extra notes, maybe it need a "Read me first file..."

Personal Statement

  • Not what you accomplished and you will accomplish   
  • It's not about your life story
  • Less is more (maybe 1 page?)
  • Let them understand your passion
  • Why do you like to train day and night?
  • What is driving you?
  • What make you unique?
  • What will you drive to become a CST?
  • Who you want to be?
  • What can you contribute to the community as a CST?

Keep it short, maybe just 2 pages or less (recommendation, not a must)

 

Scrum experience document

  • Share anti-pattern and what you could learn from them
  • get experience in at least one Role

 

Training experience

don't worry you will have it anyways if you work serous on the journey

 

 

The 10 required trainings do not need to be CSM classes, but it should have at least 100 students and follow the CSM Lo’s...
Anyhow, if you make Co trainings, you also will get trainings, but it need to cover 50% and more

 

How to learn other CST's

  • To get co-training opportunities, you can join their class and learn from other CST, build a relationship, so that they have the possibility to learn more about you
  • Make and share a video of how you would teach it
  • Join Conferences

 

Training materials...

  • Think about How and Why and explain ... based on LO
  • Show the real documents that you are using...
  • If you are using the 4 c's (note down how you will do it, what you do for each C) "Training From the Back of the Room"

    Connection

    Concept

    Concrete practice

    Conclusion

  • Explain what kind of games you are you using and explain how you will debrief your exercises, this will be important
  • Maybe write a word document that explains your Ideas and that maps to your materials
  • Reference the source or the permission from where you take the information and pictures and if it’s not produced by yourself (eg. books, internet, think about copyright)
  • Explain each single slide, what is your idea, what each slide is about and how you like to share this message (it’s not enough if you only mention the DoD, you need to explain that you will talk about the DoD and importantly, how you will do it...) so that they understand how you make the training.
  • Make it explicit what Scrum is  in all your training materials. (this is very important)) (e.g. if you teach planning poker, make a note in your materials, that planning poker is not a part of Scrum!)
  • Submit the learning objectives that each exercise has

 

Training Mapping -> Learning objectives

  • If you have multiple slides, prepare an appendix, maybe a kind of facilitation document including pictures of exercises that are matched with the slide numbers. (name the pictures, make short description, do not just put 100 of pictures together in a folder) 
  • Keep in mind that the reviewer should easy understand the idea

 

Letter of recommendation

Use the template, available here: Candidate CST Recommendation template.

  • Start with some conversation to get relationships to CST so that they will be aware about you, e.g. with blogs or discussions in conferences, join CSM classes...)
  • Should have 5 recommendations that can give trusted feedback about your Scrum knowledge (CST, CTC, CEC are for sure the most valued recommendation, because they can talk about Scrum)
  • Letter of recommendation does not require a Co-Training, but needs to have proof that the Trainer knows you, e.g. from a retreat... or other events. (Friends, Partner, same Company as yours... are mostly not objective enough)
  • Additional recommendations are welcome, but should be separated, so that it is not messed up (make it easy for the TAC, so that he know what has the most value)...
  • If there are co-trainers but no recommendation ... people will be asking why ...
  • The recommendation should not be just awesome, they should also explain something about the knowledge...

 

Additional recommendation are possible as:

Any CST who has observed you in action, during a training class, a session you presented or even during the training classes you have participated in yourself, llike the CAL, the Open Agility with Daniel Mezick, could be useful...
You could also provide videos of your running parts of training classes to compensate. That is, something that Scrum Alliance encourages

(BUT you need the permission of the class to do it)

 

Co-training

  • 50% covered by us
  • You always need more Co-trainings but 5 is maybe a good point to start
  • You need to teach a minimum of 100 students
  • Host a minimum of 10 multi-day Scrum training sessions based on the CSM Lo

 

Video

  • Can help, but just short moments... (I found this quite difficult, even I have a lot of records...)
  • Be aware about: Photo & Video Disclaimer, get permisson to make records
  • Can be everything, can be even a talk.... at a conference ... but it should help the TAC to understand you better
  • This is optional, but keep it short and crispy.

 

Student Feedback

Inspect and adapt, explain how you inspect and adapt

  • Share the feedback that helped you improve
  • Maybe an inspected and adapted documents (what you could learn)
  • Collection feedback  starfish -> pictures
  • Collection feedback  paper -> scan
  • Collection feedback  online -> excel ...
  • Translate all feedbacks to English

Get feedback of 4 classes (max one year old) (full feedback, positive and negative, explain, what you learn and how you will improve, this can help)

While Likert scale feedback data can help the TAC to see the improvement over time, responses to the open-ended survey questions (such as “how could the training be improved?”) allow the TAC to understand more thoroughly about your opportunities for growth as a trainer.

 

Community involvement

  • Blogs
  • Articles, should have the possibilities to get feedbacks or comments...
  • TED talks 
  • Joining conferences
  • Something, that we bring to the community, and is not your business...
  • You may can collect all this in an simple file with bullet points ...
  • Maybe they will google your name ...
  • Are you visible in the internat (when people google the name and scrum, agile)
  • You should be visible around 2 years before the application

Information for the TAC session

 

SUBMIT, be sure that all things, that you submit has a reason, explain why this will help and support but short and crispy.

JOIN a MOCK- session is i helpful plus.

 

The time box is 20 min for the topic that we need to explain...

How to exercise:

  • Use poker cards under 20 points... 1,2,3,5,8,13
  • Take all learning objectives...  and use the poker cards as a time box

The TAC

  • Start with a Q&A (often about the personal Vision)
  • 20 min teach a topic (short preparation possible)
    • if you use teaching from the back of the room, maybe explain what you do in each C and then make the debriefing explicit
  • 5 min personal own reflection

 

Information for CTC / CEC

Helpful if you can share  and know some coaching frameworks.

  • 1 for CTC
  • 3 for CEC

(ORSC, Co-Active, NLI,...)

 

Co-training, observe opportunities in Vietnam

Links

Kommentare

Bitte geben Sie den Code ein
* Pflichtfelder
Es sind noch keine Einträge vorhanden.
Druckversion | Sitemap
© Sebastian Sussmann