Skip to main content

How to choose a QA specialist for your team?

To be honest interviewing for any position it is a hard task and QA is no different. Interviewer have to know what is the set of required qualities to do the requested tasks and what is the set of qualities that should be placed in "Nice to Have" category. From that perspective QA is the most complicated position in IT market as two general approaches are gaining ground in the field: "Technology View" and "Quality View". So which one of those two is more efficient in finding highly rated QA professionals?


Technology View
In this approach interviewer assumes that Quality Assurances its all about familiarity with a specific technology or business field, so if a person worked for 3 years in banking industry this person will be a perfect candidate for any banking position, or if a person performed nicely for several years testing in JAVA environment this person will be a terrific match for any QA position in JAVA development environment, unfortunately live are not so simple and those assumptions are usually incorrect and harmful for the company.
Quality View
In this approach the goal is to find quality oriented specialist which is interested in understanding how the required system working, interested in finding out what are the weak and breakable points of each feature, has a great attention to details and seas each test cycle as a new challenge. This person should have a technical set of mind, terrific understanding of SDLC, QA`s place in the company, and finally see his (or her) work as mission, a quest for better quality and product.

So when we are looking for QA  specialist his (or her) technical set of mind and a passion for quality should be the mandatory skills for any QA position. Don't get me wrong, a previous experiences in a specific business field is a nice-to-have advantage and can be a discussion maker on final stages of a selection process, but its completely wrong to use those factors as requirements in the initial selection process.
Some time ago I consulted a company that was in a process of creating a new QA department they started by hiring a new QA manager which came from development department and was all about hiring by using a Technology View approach (which is very useful and popular in development departments). His approach was all about mirroring the hiring process in development, so if the company planning to develop a trading system in .NET environment - developers should have .NET experience and QA should have trading experience, which led to poor quality results in QA. My suggestion was to switch to Quality View in the hiring process. I instructed the HR team accordingly and the result was terrific, in 6 months since my arrival the new QA team performed faster and better then their predecessors.
My suggestion to both HR and the hiring managers is to use Quality View as the candidate selection method for QA position.

If you are interested in hiring quality assurance specialist please visit Broad Sky Inc
Labels:

Comments

Post a Comment

Popular posts from this blog

Proper QA estimation in Agile project

  Today, I want to chat about a common issue in Agile development – story point estimation. You see, it's easy to get caught up in estimating how long a feature will take to develop and forget about the crucial Quality Assurance (QA) effort.  It happens to often: your team is in the middle of sprint planning. New user stories are being discussed, and estimations are given, but there's a catch. You've estimated the development time perfectly, but you've barely even glanced at how much effort QA will take. Why? Agile talks about Development Team and you mistakenly thought that it is all about DEVELOPMENT. Sound familiar? Trust me; it's a more common scenario than you might think. So, what's the big deal? Well, when you leave QA effort out of the equation, several not-so-great things can happen: Vilocity can suffer: You might think you can squeeze more into a sprint than is humanly possible, setting your team up for disappointment and overcommitment. Quality can de...
Post a Comment
Read more...

What is the velocity of an Agile scrum methodology?

Let's discuss some of the important measurements in Agile, and that is the Velocity of the Scrum team work. Based on Wikipedia definition Velocity is " ...the rate of change of its position with respect to a frame of reference and is a function of time...", which when transferred to the scrum world can be summarized as: The amount of work that the scrum team completed in a single measure of time - in a sprint. How we Calculate Velocity? Velocity is actually a very simple to calculate, it is done but totaling the number of story points of fully completed user stories from the sprint backlog. So if a current sprint included 4 user stories: 2 with 8 story points each, one with 3 story points and one with 32 story points. and by the end of the sprint the 32 one was not fully done the velocity calculation will be: 8+8+3=19 Note: the 32 story points are not part of the velocity calculation as this user story was not completed. What Velocity is used for? The v...
Post a Comment
Read more...

What is Quality Assurance?

What is Quality Assurance (QA) in the software development world? This one will be the most popular question,with the widest variety of answers, which by its own gives me a good reason to answer it. So, I will start with dictionary(Wikipedia) definition: Quality assurance, or QA (in use from 1973) for short, is the systematic monitoring and evaluation of the various aspects of a project, service or facility to maximize the probability that minimum standards of quality are being attained by the production process. QA cannot absolutely guarantee the production of quality products . By large this is a nice definition, though it has two issues that need to be discussed further more: 1.minimum standard of quality. 2.quality of a product. But before we go there let me say something about "assurance"
4 comments
Read more...