The "Kronos Guy" Blog

A Few Good Testers

  

 Email Article  

Tweet  

  

  

  

 delicious  

  

  

A key part of managing change is testing and quality assurance. This guest post was written by a dear friend of mine after finishing another arduous sprint on an Agile-run project. Here's to all our QA people out there who ensure we deliver quality Kronos projects! 

Friends, we live in a world that has software and that software needs to be thoroughly tested. Who's gonna do it? You? You, [fill in a name]?  I have a greater responsibility than you can possibly fathom.

You coddle the developers who miss deadlines and curse QA's setting of high goals; you have that luxury.  You have the luxury of not knowing what I know: that setting high goals, holding people accountable and enforcing processes, while difficult, creates a quality product and that my existence, while grotesque and incomprehensible to you, creates a quality product.

You don't want the truth because deep down in places you don't talk about at meetings you want me to test, you need me test. QA uses words like accuracy, consistency, quality.  We use them as the backbone of a QA person working hard to create a quality product. You use them as a punchline.  I have neither the time not the inclination to explain myself to a person who rises and sleeps under the blanket of quality I provide and then questions the manner in which I provide it.  I would rather you just said "thank you" and went your way. Otherwise, I suggest you learn how to QA and match the level of our commitment to quality. Either way, I don't give a damn what you think, for we in QA
will not change.