Skip to main content

Managing to Test


Earlier in the year Lena Wiberg posted an interesting challenge on Twitter: 

I would like to pair up with other writers and do a series of pair blog posts. So we agree on a topic, we both write a post on our own blogs and publish at the same time. 2 perspectives for 1 topic! Any takers?

Swaps are fun, so I signed up and Lena asked me for a topic. After some consideration I proposed "testing skills I use in management" for the selfish reasons that I'm interested to hear what she has to say on it and also to collect thoughts that I've had over the years into one place. 

--00--

I spent quite some time early in my managerial career observing how I went about my work, finding what I liked and what I didn't, and deciding what my guiding management principles appeared to be and should be. This is what I came up with:
  • Be clear and present
  • Be congruent 
  • Provide motivation, organisation, information, and the occasional jiggle.

To gloss these a little, I want to:
  • be open about what I think, what I will do, and why; be available, approachable, and responsive (see e.g. Clear and Present Manager)
  • in any situation, take into account the interests of the people involved, myself, and the wider context (see e.g. What Did You Say? in Book Notes)
  • try to find ways of working that suit the team and the task (see e.g. Naomi Karten's MOI paper)

When I cast it this way, management skills and testing skills don't seem so far apart. In both cases I want to gather data and understand something about where it came from, when, how, and so on. I then want to integrate it with other data I have from other sources and decide where I should go next. I want to think about how I'm working, be transparent about why, and open to suggestions for change. I want to be prepared to explain the reason for actions I've taken, and to take those actions in a balanced way.

Let's look at an example. As a manager, I am regularly criticised by members of my team. Amongst other things I'm sometimes accused of being overly logical or too analytical. The subjective nature of "overly" and "too" give me leeway to dismiss this assessment as a matter of degree, viewed from a jaundiced perspective, should I choose to. But I don't choose to; instead I regard it as data. (And, yes, I am aware of the potential irony there.)

It's valuable information when someone on the team is feeling sufficiently strongly to tell me to my face that I have the wrong take on an issue. (Aside: finding out that someone is saying it to others but not me is also valuable, but different.) I will always by default respect it as given honestly with good motivation. 

For me, this is data from a known source in a particular context and is to be integrated with other data from other known sources in their particular contexts. Other sources include me and the team and the company, and other contexts include mine and the team's and the company's. 

I am likely to want to ask questions to try to understand what is beneath an observation which is critical of me. (The data question, due to Jerry Weinberg e.g. Perfect Software is "What did you see or hear ... that led you to that interpretation?") I think that, over the years, I have got better at doing it in a way that is both non-judgemental and non-defensive and, crucially, comes across that way too.

On any given issue, I will want to give individual pieces of data different weights depending on the context they come from and the problem at hand.

But, and this is a big one, the kind of data gathered this way is rarely quantifiable. It's usually messy and incomplete and it's often tangled up with other issues in complex and non-visible ways. We are human, after all. 

This feels a lot like testing to me.

In testing, I find, data comes from all sorts of disparate sources with different motivations, including the stated requirements, the market conditions that make these requirements relevant now, the level of understanding of the problem we're solving for the customer, the informal conversations with stakeholders, the developer's personal opinions on the approach requested and their personal preferences, the technology stack's prejudices, what the software tells you when you engage with it, and so on and so on.

How do I, as a tester, balance this data? I use critical thinking and heuristics based on experience and social interaction and investigation and research and modelling and empathy and pragmatism and numerous other skills. My overriding aim is that of pursuing relevant incongruity, by which I mean helping the project to be the best that it can be within the known constraints that it has, by targeting my efforts and finding issues and potential issues that threaten it. 

And as a manager? Well, in all honesty, this is how I approach management problems too. 

So where is the difference between being a manager and a (cough) individual contributor? For me, I think it's in the degree of responsibility for people and wide-scope decisions. As a manager there are many bucks that stop with me which intimately involve other people whose happiness, career, and actions I'm responsible for.  As a tester I'm generally only responsible for my own decisions and actions.  

See also:
--00--

Testing Skills I Use in Management is Lena's post on the same topic over at her blog. We agreed to swap comments too, so you can find mine with her piece, and her thoughts on what I said here:

I did what I shouldn’t and instinctively messaged James after reading with: “So interesting! Completely different takes!” Funny enough, he thought we had come  to very similar conclusions. Which of course had me read his comment before writing this, thus influencing me. So, I cannot write a completely unbiased comment. But  on the other hand I can now try to analyse why I felt we had so different takes while James felt we ended up so alike.

First of all, I haven’t known James long. And I’ve mostly gotten to know him through his blog posts, his twitter and through our work on board for the Association for Software Testing. My view of  him has been that he is very calm, methodical, well spoken (and written) and with a great sense of humour. I have gotten a lot of inspiration from his blog posts in my own writing and I have very much appreciated our discussions both in real life and online. 

When I read his post my gut reaction was that ours were completely different but analysing it a bit more I can see why James feels we ended up in the same place. Because we did, just by different routes. I write a lot about feelings, James writes a lot about data - our conclusion however seems the same: A lot of skills from testing are definitely transferable to managing. Reading our posts it is clear to me that the way we used to approach testing probably spilled over to how we chose to approach management.  I can see that we have the same goal, we care about the same things but the road we would choose would probably look completely different. Thank you so much James for giving me your perspective!

Comments

Popular posts from this blog

Can Code, Can't Code, Is Useful

The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "If testers can’t code, they’re of no use to us" My first reaction is to wonder what you expect from your testers. I am immediately interested in your working context and the way

Meet Me Halfway?

  The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "Stop answering my questions with questions." Sure, I can do that. In return, please stop asking me questions so open to interpretation that any answer would be almost meaningless and certa

Not Strictly for the Birds

  One of my chores takes me outside early in the morning and, if I time it right, I get to hear a charming chorus of birdsong from the trees in the gardens down our road, a relaxing layered soundscape of tuneful calls, chatter, and chirrupping. Interestingly, although I can tell from the number and variety of trills that there must be a large number of birds around, they are tricky to spot. I have found that by staring loosely at something, such as the silhouette of a tree's crown against the slowly brightening sky, I see more birds out of the corner of my eye than if I scan to look for them. The reason seems to be that my peripheral vision picks up movement against the wider background that direct inspection can miss. An optometrist I am not, but I do find myself staring at data a great deal, seeking relationships, patterns, or gaps. I idly wondered whether, if I filled my visual field with data, I might be able to exploit my peripheral vision in that quest. I have a wide monito

Postman Curlections

My team has been building a new service over the last few months. Until recently all the data it needs has been ingested at startup and our focus has been on the logic that processes the data, architecture, and infrastructure. This week we introduced a couple of new endpoints that enable the creation (through an HTTP POST) and update (PUT) of the fundamental data type (we call it a definition ) that the service operates on. I picked up the task of smoke testing the first implementations. I started out by asking the system under test to show me what it can do by using Postman to submit requests and inspecting the results. It was the kinds of things you'd imagine, including: submit some definitions (of various structure, size, intent, name, identifiers, etc) resubmit the same definitions (identical, sharing keys, with variations, etc) retrieve the submitted definitions (using whatever endpoints exist to show some view of them) compare definitions I submitted fro

Testers are Gate-Crashers

  The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "Testers are the gatekeepers of quality" Instinctively I don't like the sound of that, but I wonder what you mean by it. Perhaps one or more of these? Testers set the quality sta

Vanilla Flavour Testing

I have been pairing with a new developer colleague recently. In our last session he asked me "is this normal testing?" saying that he'd never seen anything like it anywhere else that he'd worked. We finished the task we were on and then chatted about his question for a few minutes. This is a short summary of what I said. I would describe myself as context-driven . I don't take the same approach to testing every time, except in a meta way. I try to understand the important questions, who they are important to, and what the constraints on the work are. With that knowledge I look for productive, pragmatic, ways to explore whatever we're looking at to uncover valuable information or find a way to move on. I write test notes as I work in a format that I have found to be useful to me, colleagues, and stakeholders. For me, the notes should clearly state the mission and give a tl;dr summary of the findings and I like them to be public while I'm working not just w

Build Quality

  The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "When the build is green, the product is of sufficient quality to release" An interesting take, and one I wouldn't agree with in general. That surprises you? Well, ho

Make, Fix, and Test

A few weeks ago, in A Good Tester is All Over the Place , Joep Schuurkes described a model of testing work based on three axes: do testing yourself or support testing by others be embedded in a team or be part of a separate team do your job or improve the system It resonated with me and the other testers I shared it with at work, and it resurfaced in my mind while I was reflecting on some of the tasks I've picked up recently and what they have involved, at least in the way I've chosen to address them. Here's three examples: Documentation Generation We have an internal tool that generates documentation in Confluence by extracting and combining images and text from a handful of sources. Although useful, it ran very slowly or not at all so one of the developers performed major surgery on it. Up to that point, I had never taken much interest in the tool and I could have safely ignored this piece of work too because it would have been tested by

The Best Laid Test Plans

The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "What's the best format for a test plan?" I'll side-step the conversation about what a test plan is and just say that the format you should use is one that works for you, your coll

Test Now

The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "When is the best time to test?" Twenty posts in , I hope you're not expecting an answer without nuance? You are? Well, I'll do my best. For me, the best time to test is when there