Are you moved to a new testing team within the same organization or to a new organization recently?If yes then I am sure you may be starting exploring or learning the current team/organization’s testing process. And by this time you would have noticed the usage of various software testing related jargon/terms which may be different from your past team/organization.Slowly you would have started learning the new team/organization’s testing terms and processes.
As a test lead or test manager you will be in a position to find out various hidden and open problems related to software testing terms, processes and other stuffs. I was also in that same situation. As a new person there in the team it was too early to create the personal rapport with the members of the testing group.Slowly I had started interacting in person with the people and tried collecting their view points and inputs on the testing process they were following. But people were little reluctant in answering my queries (may be due to fear/hesitation with a new person in place?)
Nothing worked out for me but my main task at that moment was to find out the inconveniences being experienced in the testing processes followed by the testing group.When called for the meeting for an hour and asked about their openings people shared only about their career related issues and not the real improvements needed with the current software testing process.
Then I decided to change my strategy to get suggestions from people in a different way as follows: Circulated a email to the entire group stating like a suggestion box will be kept between so and so dates at a common place where the testing group members can post their suggestions in writing on a paper and we highlighted in bold letters that there is no need to mention their name or employee no or project name or domain name in that suggestion paper.
As communicated the suggestion box was placed for a week and at the end of the week we have opened the suggestion box found that there were around 35 suggestion papers placed by the people.
The further course of actions we had done were self analysis of those suggestions; filtering out a few invalid ones; forwarding the valid ones to the QA group(Process group) for their analysis and to hear their decision to include those valid suggestions into day to day testing practice.
This way of getting suggestions by keeping suggestion box helped me a lot in my environment. This way may work out to you as well when you try but the results may not be guaranteed since it depends mostly on your people and environment.
No comments:
Post a Comment