Skip to main content

Savio Saldanha - Personal Annual Leadership Review and Feedback: 2016-2017

It is with great joy and gratitude that I present to you my first ever self review, wherein I was evaluated by the members of my team at a leading IT major on multiple parameters.

I have initiated this evaluation with a view to ensure that the teams that I guide and nurture truly benefit from my services, grow successfully and realize their capabilities. Given the encouraging response received, I intend to factor in the reviews and pursue my goals with continued zeal and excellence in mind.

The team was polled for the following:

  1. Fair treatment
  2. Individual professional and personal development
  3. Trustworthiness 
  4. Recommend my services
 And here are the results:


100% positive responses from my team on all counts. I am humbled. This result goes to show that it is through the attitude of servitude that we build great teams. And I shall continue to do so.

NOTE: The poll was taken on paper and is ready for presentation upon request.

God bless.

SavioS
Labels:

Comments

Post a Comment

Tell me what you think

Popular posts from this blog

3 Common mistakes that testing teams should avoid

A friend and I were recently talking about the kind of common yet critical mistakes that are made quite unknowingly during the test phase of the SDLC. Some of the points mentioned below are the kind of processes mandated by companies for ages! It is not uncommon to see that test managers, along with the test leadership within companies making such blunders. And if you see such practices being followed at your company, let them know that they should be ridding themselves of these common mistakes. 1. Test cases are not traced back to the requirements One of essential artifacts of the testing phase is the Requirement Trace-ability Matrix. What this matrix does is help you link your requirements to your test cases. As a result, you would be aware of the coverage your test cases provide to your requirements. Not having an RTM puts you and your team at the risk of coming up with an incomplete coverage of the requirements  and the possibility of leaking defects. Her...
1 comment
Read more

A quick guide to writing better test cases

This topic has been touched many times over on the internet; I'll leave out the advise of keeping simple, your test cases and the language of your test cases. Without going into methodologies and techniques used in testing, I'd like to outline a few principles of test case writing that you should bear in mind the next time you're writing test cases. 1. Design scenarios Firstly, don't think of writing test cases.. :) Or anything related to test cases. For the particular application / unit under test (AUT), take time to think through and identify possibilities of: Inputs - All possible inputs that can be given to the AUT. Your inputs can be data or a certain action to be performed, like clicking a button Outputs - All possible outcomes / behaviours of the AUT in response to the input  Trigger points - Conditions that when activated, cause the AUT to perform certain action(s) Alternate flows - When testing workflows, always ensure you identify flows other than t...
Post a Comment
Read more

Attention! These 3 Activities are Slowing Down Your Testing!

These are activities you perform almost daily. You're tired of the monotonous work involved and yet its hard to realize that these are the activities that you must optimize in order to speed up your testing process. You would probably have these at the back of your mind.. Let me help you bring them to the fore! 1. You derive your test cases from a requirement document: We're all faced with this situation each time some piece of code needs to be tested. We look for the requirements, and frame our test scenarios and test cases. Have you ever thought what exactly are you doing by writing test cases? You're simply rewording the requirements! Something simple for example: Requirement = The login page will allow system access to the user by authenticating his/her username and password. The user will be allowed to enter the username and password through text boxes of not more than 20 characters (this does not mean the data type char). Test Case#1 = Verify the presence of ...
Post a Comment
Read more