Me and My Bestimates

As Test Manager I fit my team's work into multiple overlapping project schedules which are not under my control. The schedules have, as you might expect, multiple constraints that operate simultaneously, such as:

end dates or other milestones
dependencies on other parts of the schedule or other schedules
level of effort we are able or prepared to commit to different tasks in absolute terms (e.g. contractually) or in relative terms (e.g. based on perceived risk)
methodology; different teams in Linguamatics operate different development methodologies, and we work with non-development teams too
desired quality level (whatever that means in any given case)

Scheduling in this environment is a challenge even without the wildcard that is the unknowns; the stuff you find out as you go and the contexts that change under your feet.

To do my best to provide the service my (most often internal) clients want - which generally includes some kind of estimate, even if there is little at times to base it on or anchor it to - I think I need a few things, including some model of:

the resources that I have or will have available
the status of the projects that are ongoing
the relative importance of projects to one another

To best provide a framework for my team I think I need a few more things, including:

transparency of decision-making
clarity of current priorities
visibility of actions aimed at improvement

In an attempt to achieve these ends (amongst others) I maintain a spreadsheet that records pieces of work over a certain granularity. The definition of granularity isn't very scientific: if a project feels "worth tracking" then it gets in; if a tester feels they'd like it tracked then it gets in; if it has the feeling of something that might blow up then it gets in. I update and publish this to an internally public location every week, with a short summary of significant changes and various charts showing how we're spending time in various dimensions which I use to analyse how we're working and what changes we might experiment with. (I am a practitioner of and believer in Open Notebook Testing and openness and responsiveness generally.)

For most projects that we decide to track, the tester or testers on a project, and/or me, will pick some initial budget. (There are some exceptions which I'll touch on later.) The budget is based on all sorts of factors, such as those mentioned above and those summarised by George Dinwiddie in Estimating in Comparison to Past Experience and attempts to take uncertainties into account.

I view the budget as a kind of "top-down" number. It (a) fits into and influences the global scheduling and (b) provides implicit guidance to the testers about the time they have available to test given what we know now. It is part of the project context for them, and should constrain testing in the way that other aspects of that context do.

As work proceeds, testers report the time spent on each project along with their current estimate for the remaining work. I view this as a "bottom-up" number. It (a) invites the tester to think at a level higher than immediate action, to step back, to defocus, to prioritise and (b) provides feedback to me and the bigger scheduling headache.

Some projects are more top-down: for example a piece of work which is set up in a time-box. Some projects are open-ended and bottom-up: for example an investigation into a live support issue. Most projects sit somewhere in between. Projects which are entirely bottom-up will often start with a phase where no explicit budget is set and no estimate is made; instead we'll just record time spent. At some point we'll either reach the end of the investigation, the end of the availability of the tester (in which cases work stops) or some point where we feel we understand enough to set a budget.

Because many of our projects tend to be more schedule-bound, our default position tends to be to assume that project work consumes the budget and then stops and that the tester will reprioritise based on this as necessary. However, frequently something happens on a project that affects the tester's estimate - the feature turns out to be more solid or less complex than we expected; we were able to do more work in unit testing than we anticipated; there's some horrible interaction with another piece of our application that no-one expected. In this case, we will talk about the current budget and the differences between it and the new estimate and what impacts there would be of changing the budget, or not. Some for-instances:

the tester discovers that there's some area we didn't think needed testing but actually does and increases their estimate to accommodate it. I might decide, on a schedule basis, that more time is not available, so the budget does not change, and the question becomes one of balancing risk inside the existing budget. Future estimates for this project will need to take this decision into account.
the tester discovers that the implementation is missing some behaviour that the company deems is critical. It will require investigation and retest so they increase their estimate to accommodate that work. I agree that this is important and we increase the budget to provide more time. (And I deal with the global scheduling impact.)
I find that there is more time in the schedule, perhaps because something else got cancelled. I tell a tester who previously wanted time for some piece of work that is it now available and increase the remaining budget for that work.
I am told that we need to complete work on some project earlier than previously understood and I reduce the budget on it, prompting a discussion about how best to proceed (with the usual iron triangle to constrain us).

What's crucial here is that the discussion can be opened at any point, by either side, should circumstances make that necessary or desirable or even just a sensible precaution. And any negotiation can and does include other stakeholders.

The budget and and estimates mutually constrain one another and contribute uncertainties at their different granularities. They mix science and instinct, planning and gut; known and unknown; they're guesstimates. They go well together, they bounce off each other, they influence one another and reflect one another, they're like best mates; they're bestimates you might say, although I never do.

In some sense I think of them as a simple interface between the complexities at the test level and complexities at the management level. Compressed down into a single number they naturally lose information but, when more information doesn't need to be shared (essentially we are on-track relative to the most recent conversation), that is sufficient and indeed efficient. Having a communication channel open for when more needs to be shared is, as I've just said, crucial. And I'll say it again: available channels of communication are absolutely crucial.
Image: https://flic.kr/p/6my3Gn

Notes

The approach described is a high-level sketch of the process that has evolved over time to try to manage competing constraints and requirements of the kinds that I mentioned at the top. And it continues to evolve to meet new constraints or ideas. If it stops meeting my needs, I'll stop using it.

We use the same spreadsheet and reporting mechanism to record time spent on ongoing team-level tasks which we then use to project future levels of effort, or identify trends or that there may be a problem we need to look into.

What I've written here leaves out a lot of detail in and around what we do, including how we decide what work to do in any given case, the existence of peer review (so there are other eyes on the work), the help I get from my team in spotting bugs in what I've done, questioning why I do it - which is how this particular post came about - or suggesting improvements, the importance of trust on both sides, and the importance of testers being empowered and supported in their work.

Edit: David Hansson of Basecamp covered some similar ground in Drive Development With Budgets Not Estimates.

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 answ...

How do I Test AI?

Recently a few people have asked me how I test AI. I'm happy to share my experiences, but I frame the question more broadly, perhaps something like this: what kinds of things do I consider when testing systems with artificial intelligence components . I freestyled liberally the first time I answered but when the question came up again I thought I'd write a few bullets to help me remember key things. This post is the latest iteration of that list. Caveats: I'm not an expert; what you see below is a reminder of things to pick up on during conversations so it's quite minimal; it's also messy; it's absolutely not a guide or a set of best practices; each point should be applied in context; the categories are very rough; it's certainly not complete. Also note that I work with teams who really know what they're doing on the domain, tech, and medical safety fronts and some of the things listed here are things they'd typically do some or all of. Testing ...

The Best Programmer Dan Knows

I was pairing with my friend Vernon at work last week, on a tool I've been developing. He was smiling broadly as I talked him through what I'd done because we've been here before. The tool facilitates a task that's time-consuming, inefficient, error-prone, tiresome, and important to get right. Vern knows that those kinds of factors trigger me to change or build something, and that's why he was struggling not to laugh out loud. He held himself together and asked a bunch of sensible questions about the need, the desired outcome, and the approach I'd taken. Then he mentioned a talk by Daniel Terhorst-North, called The Best Programmer I Know, and said that much of it paralleled what he sees me doing. It was my turn to laugh then, because I am not a good programmer, and I thought he knew that already. What I do accept, though, is that I am focussed on the value that programs can give, and getting some of that value as early as possible. He sent me a link to the ta...

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...

On Herding Cats

Last night I was at the Cambridge Tester meetup for a workshop on leadership. It was a two-parter with Drew Pontikis facilitating conversation about workplace scenarios followed by an AMA with a group of experienced managers. I can't come to work this week, my cat died. Drew opened by asking us what our first thoughts would be as managers on seeing that sentence. Naturally, sadness and sympathy, followed by a week ? for a cat ? and I only got a day for my gran! Then practicalities such as maybe there's company policy that covers that , and then the acknowledgement that it's contextual: perhaps this was a long-time emotional support animal . Having established that management decisions are a mixture of emotion, logic, and contingency Drew noted that most of us don't get training in management or leadership then split us into small groups and confronted us with three situations to talk through: Setting personal development goals for others. Dropping a clange...

Reasonable Doubt

In Your job is to deliver code you have proven to work Simon Willison writes: As software engineers we ... need to deliver code that works — and we need to include proof that it works as well. He is coming at this from the perspective of LLM-assisted coding, but most of what he says applies in general. I think this is a reasonable consise summary of his requirements for developers: Manual happy paths: get the system into an initial state, exercise the code, check that it has the desired effect on the state. Manual edge cases: no advice given, just a note that skill here is a sign of a senior engineer. Automated tests: should demonstrate the change like Manual happy paths but also fail if the change is reverted. He notes that, even though LLM tooling can write automated tests, it's humans who are accountable for the code and it's on us to "include evidence that it works as it should." Coincidentally, just the week before I read his post I told one of my...

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...

Why Test, Test What, Then How?

There was a time when testing was all about the mnemonics . Well, we had no AI back then so thinking about our human craft and how to share what we had learned using our human intelligence with other engaged humans for later recall in their human heads seemed important. But this post isn't about dumping on AI. It isn't about mnemonics either even if WTTWTH does look like something that'd fit well into that ancient world. No, this post is just a snappier version of what I said to my team this week when I was walking through some testing I'd done the day before. It was concerned with a change to a particular turn in the dialog system we're building where multiple variables are in play, some populated by an external call to an LLM service. I wanted to make the point that the bulk of the testing work was done in the research I did and the spreadsheet I made, not in the interaction with our product. That spreadsheet was the result of me looking in our service's cod...

Open Your Mind

Jerome Groopman, in How Doctors Think , reviews ways in which doctors can make poor choices, identifies potential causes, and suggests some practices, for both doctor and patient, that can help to prevent them. I find this interesting for a couple of reasons: first, I work in the health space, although not in a therapeutic area and, second, I like to reflect on my own thought processes. I'll take three broad themes from Groopman's analysis: the business of healthcare and how that impacts a physician's ability to practice; the doctor-patient relationship and how that impacts the experience of both sides; and the cognitive failings that impact a correct and timely diagnosis for any given patient. Naturally, these overlap. The book is written from the perspective of the notoriously commercialised American medical system and is around 20 years old, so doubtless some of the details are different outside of the US and have changed since pu...

Better Isolate Than Never

How do you test a product with distributed logic and non-deterministic components? Well, it depends on the product and when the question is asked. This post is one answer, for now. A service I work on exposes an API for internal and external clients and calls multiple other services. It orchestrates a reasonably complex journey for a user, with their inputs and the responses of the services determining each step. Our customers can configure the service to provide a variant of the standard journey for their users. This gives them choices on the available steps, the order of the steps, and, importantly, some of the logic for taking particular steps. This configuration lives in a different repository to the service, not owned by us, and it can be changed and deployed independently from the service. As you can imagine, we test our service in multiple ways at different granularities using the usual tooling, including unit tests fo...

Hiccupps

Search This Blog