881 reputation
511
bio website softwaretestingclub.com/…
location
age
visits member for 3 years, 10 months
seen Sep 5 at 22:08

Apr
16
comment How does a programmer tell a business analyst that she isn't right?
+1 for a professional and constructive approach - having a discussion with the BA to make sure there are no other potential impacts sounds like a mature and professional way to handle this.
Apr
16
comment How does a programmer tell a business analyst that she isn't right?
This is really bad advice: suggesting that the original questioner make threats about having a colleague they disagree with replaced is not a great way to build good working relationships. Especially given that responses to other questions suggest that part of his reaction is based on fears carried over from a previous bad environment, not current circumstances.
Apr
16
comment How does a programmer tell a business analyst that she isn't right?
Yup, sounds like Business Analyst. But +1 for "The important thing here is that respectful and truthful communication among all parties is crucial".
Apr
16
comment How does a programmer tell a business analyst that she isn't right?
Is framing this in terms of "winning" and "losing" really a good way to work together? This sounds like an unnecessarily hostile response - "she's trying to...drop the ball on you" assumes malice on the part of the BA, when there's nothing in the original question to suggest any more than misunderstanding about process. If you frame a disagreement as a battle, you may win on this one, but you'll lose overall as working relationships will become antagonistic and everybody will get to spend most of their time on CYA and paperwork.
Apr
16
answered What techniques should be used to ensure clear communication from the customer?
Apr
15
comment What I need to do to learn Quality Assurance?
@Wyatt - I didn't break it, it was already broken when I got it! ;)
Apr
15
comment What I need to do to learn Quality Assurance?
@Stuperuser, the problem is that you're saying "that is only exploratory testing. QA is much, much wider", and then you name things that would be part of an exploratory testing approach. Did you mean to imply ET cannot include non-functional testing? If so - then your understanding is at odds with Cem Kaner's. (I think his definition is canonical, don't you?) If that's not what you meant to convey, what did you mean? What do you think ET is?
Apr
13
comment What I need to do to learn Quality Assurance?
Your understanding of "exploratory testing" seems to be somewhat lacking - try Cem Kaner's definition first: satisfice.com/kaner/?p=42 (he coined the term), and then try reading this: developsense.com/blog/2008/09/evolving-understanding-about There is nothing in the definition of "exploratory testing" that excludes any type of functional or non-functional testing.
Apr
7
answered What's a good book to help non-technical management understand software development?
Apr
4
answered What should I know or learn to get up to speed on being a software QA engineer?
Apr
4
comment What should I know or learn to get up to speed on being a software QA engineer?
The paper sounds a lot more relevant to a manufacturing environment than to a development environment: what made you recommend it?
Apr
3
comment Key phrases showing benefits performing certified software testing for “your” company?
And what benefit does that certification give the customer - does ISTQB promise to indemnify your customer against your (potential) incompetence? Do they promise to decertify you if a customer provides evidence that you have behaved improperly? Or is it just intended as a marketing aid?
Mar
28
answered Is it reasonable for QA department to get higher average salary than that of development department?
Mar
16
comment Can an agile shop really score 12 on the Joel Test?
@Simon - if your agile testers don't care to call themselves testers, I guess they've never heard of Elisabeth Hendrickson, Lisa Crispin, Janet Gregory...
Mar
13
comment What quantitative metrics do you use to measure the quality of an offshore testing team?
Traceability matrix is only applicable to some very specific environments: if you're being asked to confirm compliance to requirements, then you would use it. It doesn't tell you anything however, about other quality aspects of the software, and should be regarded as a bad sign if used in an inappropriate project context.
Mar
13
comment How to Structure Bonuses for Software Developers?
I've seen extreme versions of this, where different depts would not cooperate on anything that ran the risk of reducing their bonus score. It really didn't matter if it cost the company money, it was purely "will I get my bonus? Then I don't care if we lost 2 highly trained engineers to the competition".
Mar
13
comment How to Structure Bonuses for Software Developers?
If people are slacking in an otherwise well-performing group, and this isn't due to some temporary issue (health problems, recent bereavement, etc), then surely the way to deal with this is to ask them to improve, or leave? Carrying a team member who is incapable or unwilling to do the work is a huge destroyer of morale. I don't think incentives are a good way to deal with that issue. +1 for your point in the first paragraph.
Mar
13
comment Is there value in having new developers (graduates) start as testers / bug-fixers?
Testers might write programmatic test cases, and test manually. I would expect testers to be able to bridge both sides - looking at the app from the technical and the business perspective - in order to create really challenging tests. In my organisation, there is a distinct separate role for "tester" - different training, different mindset, different (but overlapping in some places) skillset.
Mar
12
answered Proposal for a new position at work
Mar
12
comment Is there value in having new developers (graduates) start as testers / bug-fixers?
+1 for pointing out the flaw in hiring people to do something, and having them spend the first year doing something else. However, as a tester, I'd say you're wrong about "Hire testers for the things that really need a face in front of the screen". Yes, that is a small part of what I do. But I don't always need my face in front of a screen to find issues - in fact, I often find a lot of issues before the code is even written. You are right that it's a different skill set. The point of having me or my tester colleagues on a team is because we practice looking at things differently.