To start with the discussion of the above-said topic, I wish to take a real-life example:
Imagine a husband and a wife, living in the same house, are not communicating with each other. Or let’s say there is nothing to communicate between them. They just text each other if anything important needs to be taken care of. Otherwise, both are busy with their own lives and do not disturb/take care much about each other. What happens after days? A frustration rises, irritation multiplies, anger surfaces and finally an explosion occurs. Any relationship strengthens only if there are frequent communications, rare fights and multiple agreements and celebrations exist with each other.
Now, compare the above situation with the software project lifecycle.
What makes you think you are good at testing? Why do you qualify as a tester?
The question still bangs in my ears whenever it comes to an interview.
This was the question I was asked at the beginning of my career as a software tester. The interviewer asked some aptitude questions as usual and suddenly he threw this question to me. I was almost speechless. Most of the time, we think we are good at something because we are doing it or maybe we presume we are good at it. Continue reading →
We’ve established that managing a test team is a different ball game. It may not fit in within the boundaries of traditional management techniques, because of the mindset, environment and challenges faced by test teams.
Who is this article for?
This tutorial picks up from where the first tutorial left off. Out here we will discuss on how to have a happier test team. Whether you’ve been in this role or have been promoted recently, the few pointers below will definitely help in gaining Continue reading →
The importance of testers and the testing teams has been established again. An application or product’s success is largely attributed to efficient and effective testing techniques which form the basis for valid bug exposure.
A test team can comprise of individuals having varying skill levels, experience levels, expertise levels, different attitudes and different expectations/interests levels. The attributes of all these different resources’ need to be tapped rightly, in order to maximize quality. Continue reading →
Teatime discussion with a fellow friend from same industry raised the point about why projects see higher failures in terms of expectation and timeline. The critical demands from today’s projects were not the case before 5 years. Mobile applications have changed the definition of word ‘project’ in many terms.
Nowadays, everything is quick, everyone needs quick results, everywhere there is an opportunity and each part of the world is communicating with the remaining. With this level of globalization, it is really difficult to win a project, complete it, and mark it as successful.
Onsite offshore model is a very common working method for many IT teams across the industry, especially the QA teams. The way this works is, one/more (depending on the magnitude of the project) of the service provider’s QA team member works along with the client at their location.
The client location and the service company’s workplace can be geographically any place – across the globe or sometimes in the same city.
When this is the working model, there are some expectations from the Onsite and Offshore resources respectively. Let us see what they are:
What is the first thing we do when we get to work (or sometimes as soon as we wake up)? – Check email, right? Sometimes we don’t know what our day is going to be like until we read right through each email in the inbox.
In this article, we will focus on one specific section of written communication – Email. We are sharing some tips and tricks to make email communication smoother and more effective. This is applicable to all teams and not just the QA team.
Most testing professionals are technically strong enough to test their solutions, but to form a strong Test Team having various skill sets, and to maintain it, requires some different individual skills that are equally important.