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:

  1. How accurate the initial data was.
  2. How much of the original data set was used in the chart.
  3. 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.

My people aren’t participating

I frequently hear “my people won’t speak up during standup” or “they aren’t participating in retro” or other activities. Unfortunately, there are many different reasons why this might be so it’s not a simple problem to fix. Step one is to figure out why this might be happening.

Stalled work

As I talked about in this earlier video on standups, the work on our board can loosely be grouped into three categories. It’s either active, blocked, or stalled. We tend to spend a lot of time talking about the active and blocked work and have a tendency to forget about the rest, which results in stalled work aging unnecessarily. That in turn will make the overall system less effective and less predictable.

Warning levels

Over my career, I’ve noticed that a significant number of programmers ignore compiler and linter warnings. They either turn the warning levels down or just ignore the output. I’ve worked with teams using SonarQube that would have tens of thousands of warnings that they wouldn’t even look at.

“This is a safe space”

I’m seeing more and more situations where someone will say “this is a safe space” in a meeting invite or at the beginning of a session. While I appreciate that the person saying the words really wants that to be true, the fact they feel the need to say it, highlights the fact that it probably isn’t. If it really were safe, we would already know that.