All of this content used to be spread over three different blogs at three different domains and it's now been merged into one. Why was it ever three? Because at the time it seemed reasonable that each of them was for a different audiences, and yet over time I've found that the lines between topic areas got blurrier and tended to overlap. So now they're all together in one place.

If you encounter things that seem broken, please let me know and I'll get them fixed.

Browse by topic area:

There's a lot here and if you're not sure where to start, here are some popular starting points. From these, you'll find crosslinks to even more topics. Enjoy!

How often do we run our tests?

Today, automated tests1 are fairly ubiquitous in software projects. That is, almost every project has a large number of automated tests and that they tend to get run by some continuous integration (CI) server.

  1. More precisely, what we’re talking about are automated checks, not tests, but the agile community has never adjusted to using the more precise language so I’m going to keep calling them tests here. ↩

Improvements in CSS: Dark mode and CSS variables

Ryan and I started working on dark mode support for jirametrics and have discovered that CSS now has much better support for this sort of thing than it’s ever had in the past. Specifically, the latest versions of all the main browsers, now support dark mode directly, as well as CSS variables, which simplifies much of the configuration.

Ladder of Leadership

Sometimes our people aren’t taking initiative in the way we hope they will. This could be due to an issue of motivation or a lack of safety or more generally a system that discourages that initiative in some way. Whatever the reason might be, we need a way to change the conditions to get the result we want.

Jirametrics 2.0

Jirametrics version 2.0 has been released. What is it? A tool for extracting metrics, and generating reports from Jira.

Jira API: Board details

Next we’ll look at the API to get information about a board. Boards are fundamentally broken, in my opinion, because they aren’t a real thing in Jira. They’re a view into issues at a point in time, which means that they don’t show up anywhere in the history. You can’t tell what board an issue was on when a status change happened, and you can’t assign an issue to a board.

Dopamine and Learning

In order for us to learn something new, we need to store it in long term memory. If we’re unable to save it there, then we’ll immediately lose that learning the moment we focus our working memory on something new. Working memory is quite limited1 so we need to save those memories quickly if we’re going to.

  1. The research indicates that the typical person can hold 7±2 chunks of information in their working memory at once. There are reports of people who can store as many as 80 chunks of information but these people are extreme outliers. ↩

Jira API: Statuses

The issue history gives us both the name and id of any statuses that the ticket has moved through. Sometimes that’s enough but often we then need to know more about that status, such as what status category it belongs to and for that, we need to call a different API.

Reference class forecasting

Weather predictions are probabilistic, not deterministic. That means there isn’t a single right answer that we can calculate. We can’t say it will rain at 11:05 but we can say that there’s an 80% chance of rain today. Forecasting when we’ll be done is also probabilistic, in exactly the same way. We can say based on past throughput data that we have an 85% chance of being done on or before May 12.

Jira API: Issue history

If you want metrics out of Jira, the single most important thing you need to access is the issue history and it’s not obvious how to get that. Just about all the metrics you’ll want to collect will need data from the history - you might need to know when an item started or when it entered a certain priority or when the flag was set or cleared.