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.
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.
Jira API: Intro and authentication
I’m the primary author of the jirametrics tool that extracts data from Jira and generates reports. This tool evolved to satisfy my own pain of not being able to get useful data out of Jira with the built-in reports and along the way, I’ve learned more about Jira internals than I ever wanted to know.
Data Accuracy
We have a tendency to believe that anything we see in a chart is 100% accurate, although that’s often not true. To understand the accuracy of the chart, we have to understand a couple of things:
- How accurate the initial data was.
- How much of the original data set was used in the chart.
- How good the chart is at communicating the right message.
Autonomy
I’ve spoken to a number of people recently who have complained about a lack of autonomy at work. They talk about being micro-managed by their bosses. About being given solutions to implement, rather than problems to solve. About restrictions on what they can and cannot do in the environment.
Team working agreements with LEGO
Team working agreements (sometimes called team norms) are all about how we are going to work together as a group of people. To do this effectively, we need fairly deep and honest conversations, and yet we see many working agreement sessions stay fairly superficial. The approach in this article uses LEGO® Serious Play® for the core discussions to get those more meaningful conversations.