Hi! I’m the Tester!

I just joined a new project, and, again, I am being introduced as the “QA”.  I found many of the terms and ideas I had successfully changed or introduced on my last project profoundly absent – the name of my role heading the list.  Upon arriving home and checking my Twitter account, Lisa Crispin (@lisacrispin) was crusading along the same line at CodeMash (#codemash) in Ohio.  The misrepresentation is rampant and 2014 should be the year we turn it around!
In the spirit of collaboration and communication for all testers everywhere, I offer up a few ideas in the form a statement that you can read during one of your meetings that start your project:

My Fellow Project Team Members,

I was excited to be assigned as a Tester to this project.  I look forward to collaborating with you on requirements, products, and tests.  I respectfully request that I be referred to as Tester.  I am not a “QA”, I don’t “QA” anything, and can rarely assure quality in any product.  While I will work hard, as you all will, to understand what quality means to our stakeholders, and will happily share my interpretations and opinions of that understanding, quality is a team sport.  I believe we all have valuable points of view that contribute to a good understanding of what we should deliver.

When there are discussions around quality, or we are asked to define quality criteria, please don’t look to me to provide the sole definition.  I will have something to say but what I say should be added to a pool of understanding.  What I say about quality should not be taken as the project definition of quality, and certainly not the only definition of quality.  I am interpreting the ideas, concerns, and passions of our stakeholder like everyone else so I encourage you to participate in our quality discussions.  A team understanding will benefit us all by having a common quality goal that we define and that we share.

Thank You!

Advertisements

2 thoughts on “Hi! I’m the Tester!

  1. kabinchi

    Thanks for sharing. Good points in there. Only scrutiny
    – 1. it sounds too scripted.
    – 2. Using “tester” title sounds too vague, you are pretty much saying you want the team to have quality hats on but only you will be doing the tester tasks. Worth having a title to highlight you as the specialist in testing rather. Should help give them the mind set that they can seek guidance from you about testing.

    Reply
    1. Joe DeMeyer Post author

      Thank you for your comments, Kabinchi!

      I agree it is a little scripted. My hope is everyone review the ideas, reflect on them, and use them in a manner that means something to them and their team. I also hope these ideas can be context driven!

      I concur wholly with your second comment. I want to encourage team participation in quality discussions and quality actions. I also agree that a tester not only tests, evaluates, and reviews but should be available to consult with and guide testing, and possibly other project topics, throughout the project. I like your collaborative approach!

      Reply

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s