Thursday, October 18, 2007

Pragmatic Software Testing

What do I mean by "Pragmatic Tester"? Well, over the last couple of decades, two archetypes for software testers have emerged:

  1. The quality cop, a customer last, best hope to get good software. Generally an unhappy, crotchety tester who feels that they are a second class citizen. Their goal is to stop software from releasing (actually, their goal is to ensure that bug free software is delivered to the customer but that is next to impossible) and inevitably fail. I am over maligning these people, they are usually not so dramatic or mean spirited but they often have an unrealistic view on the level of quality the product needs to have in order to meet customer needs.
  2. The pragmatic tester, one who understands software must be delivered to meet customer needs and works with the team to ensure the best possible outcome.

Now, there is an entire spectrum here but most quality professionals can be put into one camp or another. I started in Camp 1 and moved to Camp 2 during my career. And it is my firm belief that agile projects cannot deal with people in Camp 1. This blog will be about my thought and suggestions on how to best apply pragmatic testing without totally selling out :)