Roger Brown (CEC, CST) posted these tips on the CTC candidate mailing list, you can find the original thread here.
I decided to post a copy of these tips here and obtained his permission to do so on August 26th, 2016.
Hi All,
Here are some tips for you when filling out and waiting for a review response to your application, Parts I and II.
– Reviewers use the comment feature in Google Docs to ask questions for clarification and elaboration. We want to help you get your application to the right level of information to make a meaningful assessment.
– Set Notifications for comments (click the Comments button in the upper right of your Google Doc) so that you can know when a reviewer has a question for you. We try to also manually send an email when there are are comments, but sometimes that get missed. Also, a conversation can result through the comments that would require a lot of redundant email notifications if you do not enable them in the document.
– Please answer any questions that a reviewer asks by editing the relevant document section. Do not put elaborations in the comment reply. You can reply that you have addressed the question. Reviewer comment-questions are intended to help you submit a more complete and clear application. Reviewers can see what you added or changed using the revision history feature.
– If you address a comment, do not “Resolve” it in the comment tool. Your reviewers will do that. Otherwise we can lose track of what was asked.
– A common feedback suggestion is that it would be nice to include photos or other documents in the application. Feel free to include supporting evidence as links in the application. Inline photos are OK, too. Links to further information are especially helpful if you refer to some technique or tool that is not widely known to the community or that you invented yourself.
– If you are technically blocked from using Google Docs, let us know and we will come up with an alternate collaboration channel for you.
– When listing the teams you coached, include non-Scrum teams when appropriate – for example leadership teams, kanban teams, marketing teams. If your coaching of one team or other group (like a Community of Product Owners or a collection of Stakeholders) influences many Scrum teams, let us know in your entries in Section I-B.
– If your public community experience section is sparse, include events internal to your company. Valid community events do not have to be open to the public.
Other tips are welcome…
– Roger Brown
Posts in the Certified Team Coach (CTC) series:
- CTC Mentoring Pilot: Overview
- CTC Mentoring Pilot: Application specific learnings
- CTC Mentoring Pilot: Coaching (To be written, tweet me if you want to be notified.)
- CTC Application Process Tips by Roger Brown
- CTC Quick pointers for candidates by Vernon Stinebaker
- CTC Application Insights by Nils Bernert