I agree with Joe's points, I am a Consultant QA with Thoughtworks and yes there is more value to QAs in a Truly Agile environment than in a traditional model. I have worked with 4 other companies (IBM, Oracle, CSC, eBay) before Thoughtworks and in those places, QA was considered as a overhead which has to be borne by the team because they have some processes to be followed and QA is just one of them.
During my initial days as a tester in traditional environments, I was given a set of test cases in an excel file and was asked by the "QA Manager" to just execute them, though before becoming a tester I was a developer working on enterprise apps on mainframe machines I never found any value in what was being done by me as a QA simply because the job was more mundane and fellow testers were not questioning any work that was given to them and it was more like a Humanoid Tester just running set of test cases, and that is when I ventured out and started learning more about testing and that added more value to me. I wouldn't really blame any company for someone not learning about testing as learning is more a personal choice.
- Karthik
From: Savita Munde <savitamunde@gmail.com>
To: agile-testing@yahoogroups.com
Sent: Thursday, 5 January 2012 7:29 PM
Subject: Re: [agile-testing] Re: Are testers equally valued on agile teams?
Hello Lisa,
I apologies for the inconvenience. Today is my first day to agile yahoo group.
I would keep in mind that i will keep agile group in loop in future discussions.
MNC means 'Multinational Corporation'. It means any enterprise which has office in more than one country.
Regards,
Savita
I apologies for the inconvenience. Today is my first day to agile yahoo group.
I would keep in mind that i will keep agile group in loop in future discussions.
MNC means 'Multinational Corporation'. It means any enterprise which has office in more than one country.
Regards,
Savita
On Thu, Jan 5, 2012 at 7:20 PM, Lisa Crispin <lisa.crispin@gmail.com> wrote:
What IS an "MNC"?
Let's do keep this discussion civil, I don't think anyone intends to make a personal criticism.
-- Lisa--On Thu, Jan 5, 2012 at 5:20 AM, Gishu <gishu.pillai@gmail.com> wrote:
--- In agile-testing@yahoogroups.com, Rohan Sarker <rohansarker1@...> wrote:
>
> *Savita:* It is your personality problem to challenge my experience and
> work.
> *Regards*
> *Rohan Sarker*
I think the point Savita is trying to make is 'don't make a sweeping generalization' (not justifying her line/tone of questioning).
I work for one of the largest MNCs in India. I've been here nearly 8 years.. and actually moved from development into QA/Test to help out.
First, Name calling for instance is unacceptable if it makes anyone in the team uncomfortable (some friendly banter is ok). It's upto the org to lay down the law and nip it in the bud - provide a good working environment.
Second, if you dislike the environment - change it. Or Change it - law of two feet. I choose NOT to work in bad places.
So your statement could be true for *Most* not for *All*. The reasons are too varied to discuss here. IMHO If you get things done, can communicate well + add value to the development team - you should be valued by your team (irrespective of your title).
- Gishu
Lisa Crispin
Co-author with Janet Gregory, _Agile Testing: A Practical Guide for Testers and Agile Teams_ (Addison-Wesley 2009)
Contributor to _Beautiful Testing_ (O'Reilly 2009)
http://lisacrispin.com
@lisacrispin on Twitter
http://entaggle.com/lisacrispin
--
Savita
__._,_.___
MARKETPLACE
.
__,_._,___
0 comments:
Post a Comment