Friday, May 13, 2016

Boxing the tester

I write this post out of slight frustration, to clear out stuff in my head. The frustration is related to discussions that keep coming up in my tweet stream. There's a few themes there:

  • Are we or are we not preventing bugs? (I don't care, except for the part about early and continuous involvement of perspectives for full picture)
  • Are we or are we not making decisions on releasing as testers? (I am, and it seems to be working well for me. I have friends in testing who are not because they feel risk-averse. It's not a role thing)
  • Are we called quality assurance since we don't assure anything? (I don't care, I prefer being a tester but would hardly want to focus my energy on just a term without relevant practical implications)
I love the products and making them great and valuable. Testing is a means to that end. Testing for me is something I'm really good at (and not so humble about), and I love working with people who are good on the programming bit because together, we're magical for the products. The longer I am in this industry, the more I break out of the boxes of the "tester role". I code. Not test automation, but just regular production code. I work on technical designs and architectures. I make decisions on those, just as much as people in my team. 

Today was a great example of me driving through a collaborative decision-making process where we'd hear from every team member before I eventually summed up what we decided. Consensus is something the Swedes do well, and Finns struggle with, but we seem to be a lot better at that culturally than e.g. Americans who seem to assume hierarchy to extents I never experience. (Sorry for the boxes, I realize they are incorrect and stereotyping but I can't resist using them anyway) Most decisions work well with consensus decision making, except for e.g. firing. Release decisions are typical consensus decisions for my agile team. We've been delegated the full decision power. 

So, I'm all around the roles. I identify as tester. Sometimes I identify as a programmer. Sometimes I'm a UX person or a product owner. Sometimes I'm a manager talking to managers outside my team's scope. Sometimes I'm a facilitator and a catalyst for improvement. 

I used to care a lot about the identity of a tester, I wanted to be called a tester. The more of the "defining tester" arguments I see, the less I care to identify with that straightjacket. But I wanted to talk about why I think the boxing is useful.

The software industry doubles every five years. This means that half of us have less than five years of experience. I think this idea comes from Uncle Bob, even if it reached me through other people in the programming community. When we have less experience, we need a clearer box to learn to cover first, before breaking through the box and finding a bigger habitat. 

I've worked with newbie testers, who were made developers just as any others, and as newbies, they would seek their colleagues for models of what to do. They did not have senior tester colleagues, and within a year, they became programmers who don't question the customer requirements and who can't identify that the software isn't working or delivering as much value as it could. When they sought training, they took same kinds of training as the rest of the team. When they looked for idols, they never found the testing idols. They never became testers. 

I started off with a strong tester identity. I learned from Cem Kaner, James Lyndsay, Elisabeth Hendrickson, James Bach, Michael Bolton - people my programmer colleagues have never heard of. It became important to be a tester, because with that label I found hundreds of people to learn from. The tester communities are powerful. The oppressed are coming together and helping each other. Together we're strong. My programmer colleagues have never experienced the level of community I've lived through in the last 10 years. 

The community has negative aspects. I don't like the fact that we bash programmers, but the communities are often places where we let out steam to find constructive solutions to hard problems we're facing at work. That don't always feel safe for programmers to join and I'd love that to change. I'm all for diversity, testing over testers. I don't like that we're so strong in defining the right words and thoughts, but I try to dismiss that to work on something more productive - failing regularly. And some general behaviors leave people feeling unsafe, even with the tester role. 

I believe the labels are important when we start. The labels help us find our peers and communities to learn from. They bring us together. But as we grow, we need to actively break out of our boxes. 

But you do realize there is, easily, a full 20 years (and more) of intensive study on just to do great testing? It's not a thing you get in a few years. If you are everywhere with your skills, you are nowhere yet. Less than 5 years of experience for half of us - we should start from different corners, and just work together to bring the knowledge to paint a fuller picture as a group than any of us have individually.




3 comments:

  1. Yesterday I:
    * tested a feature
    * prevented a release going on a promised date due to a bug
    * ensured a new point release was created contain only the fix for the blocking bug
    * encouraged the right people to talk to each other to resolve a build issue
    * backed away from the networking manager when a live issue was obviously higher in importance than my test environment update planning, and returned later when the dust had settled.
    * tested the bugfix
    * communicated fix/build status and deployment plan amendments to the entire team as decisions were made/enacted.

    My hired role is 'tester'. Very little of yesterday was 'testing'. I'm not a release manager or a project manager. But on this team none of us are and yesterday I stepped up to take the responsibility for fix, deployment to various tech/business environments and feedback to the business about go live dates.

    It is always a team effort and like you I see absolutely no value in creating a narrow definition of my role and my place in the team. I will always do whatever is required to assist myself and my team in achieving our goals.

    ReplyDelete
  2. Thanks for writing this Maaret. I like the point you make that labels are important at the start. Without being 'labelled' as a Tester I would, as you pointed out, have been less likely to find the great testing community that we have. I have only discovered the testing community in the last year or so but during that short time my eyes have been open to so much I wasn't aware of. I'm hungry to learn more and thanks to blogs, meet ups and conferences there is plenty out there to satisfy this. During the last few years I have found myself questioning requirements, processes, informing decisions, holding workshops to educate our organisation on collaborative working. The fact that I do this doesn't mean I want to move to a role outwith testing. I see all of the tasks I do as contributing to improving the quality of not only our products, but the overall business.

    ReplyDelete
  3. Blogged my thoughts: http://www.software-testing.com.au/blog/2016/05/24/testing-does-not-prevent-defects/

    ReplyDelete