Some Thoughts on Coaching

While writing a mail to giving comments on my colleague’s work coaching TA, I feel my comments are so common, and could be used as advices to anybody who want to be a coach, then, here you are.

RE: Robot Cases review, thanks


I’ll mainly comment xxxx from now on, and let’s xxxx to improve. And I felt it also
worth to share to all
yyyy members, spreading knowledge is always a pleasure

1. How you coach the team
depend on how mature the team is. From those two testcases, it gave an
impression that they are not junior Robot users, otherwise they copied other
testcases and modify to be theirs. If there are junior, so it may means they
know something, but not clear where is wrong and why and how to improve, then
you need to answer those questions.

2. It’s very good that you
first listed the referece "
TA Robot Case implementation Checklist", then the team knows what should they refer to and where
your comments come from.

3. In order to use your
reference effectively and make sure the team understand your comments, _for this
junior level team_, you can always point out the parts which is not good, and
the exact item inside your reference. And, do not forget to give your reasons
"why it is wrong". Normally you provide your suggestions also, but it depends on
the situation, avoid giving solutions to open questions, instead of encouraging
the team to think, and help them to find out the best solution for them. You
should not think for them, but bring up their ability to think

– e.g. for the comment
"fa81" the extra startup
msg shall be defined as variable to make them readable
", you could give one example, say
"fa81" the extra startup
msg shall be defined as variable to make them readable
, for example | ${extra startup message
id} | fa81 |, and consider move it to some resource files since message id is zzz wide available, it’s a kind of common resource.

4. Avoid using sentences
which is a judgement, only when it aims to invoke thinking and you’ll provide
more descriptions later. Most of times, you could substitute with questions e.g.
"how about consider in another way …?", "I think it’s not good, but let’s check
how you think, why you want to use in this way?", understanding their reasons
first, and provide help according to their context.

5. Anytime you feel mail
review or discussion is not sufficient / effective, ask for a face-2-face
communication, and demonstrate your suggestions.


About Kaveri, Yi XU

Agile Coach & Consutlant


Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / 更改 )

Twitter picture

You are commenting using your Twitter account. Log Out / 更改 )

Facebook photo

You are commenting using your Facebook account. Log Out / 更改 )

Google+ photo

You are commenting using your Google+ account. Log Out / 更改 )

Connecting to %s