Talent Management Of Software Testers Case Study

1341 Words3 Pages

Title Talent management of software testers within an insurance company. Background Talent management for Software Testers has proven to be a problem within the Information Technology spectrum (Perry and Rice(2013); Gaur and Chillar(2013); Karthik (2013); Graham and Foster(2012)). Perry and Rice(2013) are of the opinion that some organizations still practice manual testing which is labor intensive, unreliable, imprecise and because of these factors testers get bored when having to do their job and end up signing off poor quality artifacts. According to Rice (2013) organizations tend to use non-technical people to do testing and at the same time they don’t offer any formal training for these testers. Some of the testers stay in the field without up-skilling and when tools get introduced they become obsolete because of lack of skills. Karthik (2013) points out that manual testing in its nature is repetitive and manual testers are at times under looked by developers because of being non-technical. Most younger testers end up taking other streams in Information Technology or go to organizations where testing is taken seriously. Gaur and Chillar (2013) state that at times organizations don’t make exciting career opportunities available to testers but tend to invest in testing tools. In addition to that manual testing doesn’t make the job to be interesting and there’s not much to learn. Problem statement: Organization does not make opportunities available for young testers resulting in young people leaving the industry. Aim: The aim of this paper is to understand how organizations have bridged the gap of up-skilling software testers vs. the use of software tools and outsourcing. How their solution(s) can be used to address the talen... ... middle of paper ... ...on-technical business people to do testing and they are usually not given any formal/informal training on testing as a profession. This results in poor quality testing. • Building relationships with developers : Testers are usually treated like the “poor cousins”. When an application in production is found to have bugs the people blamed are testers and forgetting the developer who actually wrote the code. • Making time for testing : In most projects the delay is always coming from development resulting in less time being allocated for testing. Less time means not everything will be tested thoroughly. • Fighting a lose-lose situation: When testers sign off an application that they know has bugs they’ll be accused of not doing a good job with their testing but if they still don’t sign it off they are still hammered and told that they are causing project delays.

Open Document