Skip to main content

An Outside Chance


An idea came up in several conversations in the last few weeks: the analogy between externalities in economics and the location of activity and costs of software development. This post just dumps the thoughts I had around it.

In economics, an externality is 
an indirect cost or benefit to an uninvolved third party that arises as an effect of another party's ... activity ... Air pollution from motor vehicles is one example. The cost of air pollution to society is not paid by either the producers or users of motorized transport to the rest of society.
Externalities may be beneficial; my neighbour might buy and plant flowers that I can enjoy from my side of our shared garden fence at no cost. But the recent discussions have been more about negative externalities.

Everywhere that software is developed by more than one person there is process around the development of the software. In any given shop it will be more or less defined, refined, and front-of-mind, but it exists and has two major aims: design, create, and ship artefacts and expose, transfer, and store information.

Artefacts are straightfoward. That's the software, user documentation, change logs, and so on. Information is messier. In typical processes it might include things like

  • who wants this piece of work
  • what they want it for
  • what constraints there are on it
  • what is blocking it
  • what risks are perceived with it
  • what depends on it
  • when it's needed
  • what has been tried before
  • what was implemented this time and why
  • what was tested
  • what was found during testing
  • what wasn't tested
  • when work started
  • when work ended
  • who spent time on it
  • how much effort was spent on it
  • which work package it was part of
  • which commits were made
  • which branch commits made into
  • when the code was merged to the main branch
  • when CI first ran on it
  • what the results of the CI run were
  • which release the work went into
  • ...

In each case there are producers and consumers of the information.

Sometimes the producer will be the tooling and there will be no local consumer. We can igore this case, just like we probably ignore the raft of pointless reports and charts most process management tools generate.

More interesting are the situations where the producer and the consumer are people. For example, a company board producing goals for their product team to consume, a product owner producing a list of desired features for a development team to consume, or development teams producing documentation for an auditor to consume.

Since we are human, and busy, and tend to prefer doing over recording, we'll often skip or skimp on the information. We've all seen (and made, be honest!) drive-by one-liner tickets, empty commit messages, and lazy PRs.

But each time we do that we push a cost to someone else: the PO who has to second-guess what the board want, the development team who have to second-guess what the PO means, and the business who put all hands to the pump tidying before an audit and rectifying after it because auditors aren't paid to second-guess.

These feel like externalities and, in market economics, there are some standard approaches to tackling externalities  including taxes, regulation, and compensation.

In software development processes, taxes and compensation don't have direct analogs. Although producers are paid for their work, it seems unlikely that board members will have their salary docked if they don't take the time to communicate their needs well.

Regulation feels more familiar, perhaps in the form of reports, templates with mandatory fields, and delivery metrics. Of course, we've all seen these and we all know that it's easy to regard them as friction and it's common to want to make the minimum effort necessary to get past them and build more things.

Given all that, could this model of information flow might have some value in software development? If so, we might ask how we could give ourselves more than an outside chance of reducing negative externalities and

  • help to produce the right information at the right time
  • keep costs of production proportionate
  • have the costs paid when they are cheapest to pay
  • locate the right costs with producers
  • motivate the producers to pay the costs
  • increase positive externalities

My gut reaction includes shortening the distance between producer and consumer, working in smaller increments, minimising handovers, and asking for information when it's needed rather than pushing non-information when no-one is ready to receive it. 

It's interesting to me that these all feel like cultural aspects of process, requiring collaboration and personal responsibility. 

Your thoughts are very welcome!
Image: https://flic.kr/p/Eghfa4

Comments

  1. An interesting article - thank you. I hadn't thought of externalities where it comes to data, but had thought of user experience (blog waffle: http://randomtechthoughts.blog/2021/01/23/user-experience-ux-and-data-quality/).

    One part of the solution is, as you say, to reduce the friction or cost to produce useful information. This can be addressed by improving or creating internal tools.

    E.g. a form with a field that auto-completes with helpful (often context-sensitive) suggestions, or lets you pick from a list, rather than forcing you to type. Tools that talk to other tools behind the scenes to spare you the grunt work / find helpful suggestions for you. Or tools that create thing A by applying code to thing B, rather than a human having to create thing A and thing B separately. One example that springs to mind is things like API documentation being auto-generated by Swagger / OpenAPI from source code + comments + annotations.

    ReplyDelete

Post a Comment

Popular posts from this blog

The Ideal Test Plan

A colleague pinged me the other day, asking about an "ideal test plan" and wondering whether I could suggest something. Not without a bit more information, I said. OK, they said. Who needs the plan, for what purpose? I asked. Their response: it's for internal use, to improve documentation, and provide a standard structure. We work in a medical context and have strict compliance requirements, so I wondered aloud whether the plan is needed for audit, or to show to customers? It's not, they replied, it's just for the team. Smiling now, I stopped asking questions and delivered the good news that I had what they were looking for. Yes? they asked, in anticipation. Naturally I paused for dramatic effect and to enhance the appearance of deep wisdom, before saying: the ideal plan is one that works for you. Which is great and all that, but not heavy on practical advice. --00-- I am currently running a project at the Association for Software Testing and there is a plan for

Notes on Testing Notes

Ben Dowen pinged me and others on Twitter last week , asking for "a nice concise resource to link to for a blog post - about taking good Testing notes." I didn't have one so I thought I'd write a few words on how I'm doing it at the moment for my work at Ada Health, alongside Ben. You may have read previously that I use a script to upload Markdown-based text files to Confluence . Here's the template that I start from: # Date + Title # Mission # Summary WIP! # Notes Then I fill out what I plan to do. The Mission can be as high or low level as I want it to be. Sometimes, if deeper context might be valuable I'll add a Background subsection to it. I don't fill in the Summary section until the end. It's a high-level overview of what I did, what I found, risks identified, value provided, and so on. Between the Mission and Summary I hope that a reader can see what I initially intended and what actually

69.3%, OK?

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 ,  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 percentage of our test cases are automated?" There's a lot wrapped up in that question, particularly when it's a metric for monitoring the state of testing. It's not the first time I've been asked either. In my

Why Do They Test Software?

My friend Rachel Kibler asked me the other day "do you have a blog post about why we test software?" and I was surprised to find that, despite having touched on the topic many times, I haven't. So then I thought I'd write one. And then I thought it might be fun to crowdsource so I asked in the Association for Software Testing member's Slack, on LinkedIn , and on Twitter for reasons, one sentence each. And it was fun!  Here are the varied answers, a couple lightly edited, with thanks to everyone who contributed. Edit: I did a bit of analysis of the responses in Reasons to be Cheerful, Part 2 . --00-- Software is complicated, and the people that use it are even worse. — Andy Hird Because there is what software does, what people say it does, and what other people want it to do, and those are often not the same. — Andy Hird Because someone asked/told us to — Lee Hawkins To learn, and identify risks — Louise Perold sometimes: reducing the risk of harming people —

Testing is Knowledge Work

  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 ,  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-- "We need some productivity metrics from testers" OK. I'd like to help you meet your need if I can but to do that I'll need to ask a few questions. Let's start with these: Who needs the metrics? Is there a particular pr

My Favourite Tool

Last week I did a presentation to a software testing course at EC Utbildning in Sweden titled Exploring with Automation where I demoed ways in which I use software tools to help me to test. Following up later, one of the students asked whether I had a favourite tool. A favourite tool? Wow, so simple but sooo deep!  Asking for a favourite tool could make a great interview question, to understand the breadth and depth of a candidate's knowledge about tools, how they think about an apparently basic request with deep complexity beneath (favourite for what task, on what basis, in what contexts, over what timescale?  what is a tool anyway?) and how they formulate a response to take all of that into account. I could truthfully but unhelpfully answer this question with a curt Yes or No. Or I could try and give something more nuanced. I went for the latter. At an extremely meta level I would echo Jerry Weinberg in Perfect Software : The number one te

The Future of Testing? GRRrrr!

I really enjoy lean coffee conversations. I am energised by the rapid-fire topic switches and love it when I get exposure to multiple perspectives. The time-boxed aspect of the activity is a turn-off for some, keeping things relatively shallow, but it's one of the great advantages of the format for me: I know that I'm only investing a certain amount of my time, and it's usually small enough that the return is worth it. All of which is background context for my experience at the first Cambridge Tester Meetup event for over a year , an online lean coffee, this week. I died a little inside when I saw The Future of Testing ticket placed on the board. I felt the pain of internal necrosis spreading as it was voted up. I winced while my pre-frontal cortex withered into a tiny blackened stump at the precise second that Devops, automation, and quality champions were tossed into the discussion. The? Future? Of? Testing? GRRrrr! For as long as we are build

Trying to be CEWT

I attend, enjoy, hopefully contribute to, and get a lot from, the local tester meetups and Lean Coffee  in Cambridge. But I'd had the thought kicking around for a long time that I'd like to try a peer workshop inspired by MEWT , DEWT , LEWT and the like. I finally asked a few others, including the local meetup organisers, and got mostly positive noises, so I decided to give it a go. I wrote a short statement to frame the idea, based on LEWT's: CEWT ( Cambirdge Exploratory Workshop on Testing ) is an exploratory peer workshop. We take the view that discussions are more interesting than lectures. We enjoy diverse ideas, and limit some activities in order to work with more ideas. and proposed a mission for an initial attempt to validate it locally on a small scale. Other local testers helped to refine the details in usual the testing ways - you know: criticism, questions, thought experiments, challenges, comparisons, mockery and the rest - and a list of potential at

Fail Here or Fail There

The First Law of Systems-Survival, according to John Gall, is this: A SYSTEM THAT IGNORES FEEDBACK HAS ALREADY BEGUN THE PROCESS OF TERMINAL INSTABILITY Laws are all-caps in Systemantics . Not just laws, but also theorems, axioms, and corollaries. There are many of them so here's another (location 2393-2394): JUST CALLING IT “FEEDBACK” DOESN’T MEAN THAT IT HAS ACTUALLY FED BACK There was a point when I realised, as the capitalised aphorisms rolled by, that I was sinking into the warm and sweetly-scented comforting foamy bathwater of confirmatory bias. Seen, seen, seen! Tick, tick, tick! I took the opportunity to let myself know that I'd been caught in the act, and that I needed to get out of the tub and start to challenge the content.  Intervening at that moment was congruent: I was in a context where I would accept it and prepared to change because of it. Of course, I enjoyed the deep irony of nodding along with Gall when he talked about

Be a Quality Detector

  I've just finished reading Thinking in Systems: A Primer by Donella Meadows. It's not a new book but I'd managed to be unaware of it until recently when Marianne Bellotti mentioned it on her podcast, Marianne Writes a Programming Language .  Bellotti is writing a programming language (duh!) for modelling system behaviour using the concepts of stocks and flows, inspired by Meadows' book. The image at the top gives an idea of how such models can work, notably making explicit the feedback relationships for resources in the system, and allowing modellers to reason about the system state under different conditions over time. I have been aware of systems models similar to this since I first saw Diagrams of Effects in in Quality Systems Management Volume 1: Systems Thinking by Jerry Weinberg. Weinberg's book, and other reading I was doing early in my career as a tester, inspired me to look deeply at the systemic context in which the software I'm working on sits and