Lots of developers using Jira Software have a tendency to keep their heads down, focusing on minutiae and execution, hardly ever looking at strategy and results. Okay, sure, getting things done and out the door is one of the core principles of the Agile Manifesto. But then again, so is this:
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Reflecting on how to become more effective comes through reporting. You need to be concerned not just with what you’re doing but how you’re doing. Many of the Jira Software teams we encounter aren’t doing nearly enough reporting and it may be because they don’t quite understand the importance of it.
Well, there’s the importance. In black and white. Right there in the Agile Manifesto, aka the software dev’s bible. So if your reporting isn’t up to scratch, you’re missing out on some serious agile-shaped value.
We’ve put together a handy reporting checklist for software teams who may not be reporting like they should…
1. Are you reporting regularly and consistently?
If you’re using Scrum or another agile methodology that involves sprints, you want to be reporting before, during, and after each sprint. If you’re using Kanban, you can be reporting at any time, and as often as you need to, to ensure that work is being delivered on schedule.
In general, though, every team and organization are different and the level of reporting is often dictated by the stakeholders you’re having to report to, as well as the reports you’re having to prepare. For example, Jira Burndown Charts require multiple daily inputs whereas a Jira Velocity Chart is only reviewed once per sprint. The types of reports you’re preparing can help set your reporting schedule.
What’s important is that once you’ve established the frequency level of your reporting, stick to it. Irregular report timing can cause teams to continue making the same mistakes.
2. Do you understand why you’re reporting?
Reporting in Jira Software stops being useful as soon as you forget what it’s for. If you’re reporting just for the sake of documentation or formality, then you won’t be able to pinpoint any actionable outcomes. Also, if you use a Jira Velocity Chart inaccurately to compare effectiveness between teams, you risk hampering team morale.
The overarching purpose of all reporting is to help teams stay on track with their work and deliver what and when they say they will. If there are scope changes and bottlenecks, reports help you see them, identify them, and manage them, whether by reallocating resources, retraining team members, or changing the delivery timeline. You also need a single source of truth to communicate team progress and results to other team members as well as higher-ups, which reports provide.
3. Do you understand what you’re reporting?
Singling out report-worthy data can be tricky, particularly when it seems like all data must be important.
The thing is, in this age of information, businesses churn out dizzying volumes of data – more than any human could know what to do with. To avoid getting lost, focus on agile metrics and build your reports around those. Agile metrics enable teams to monitor their progress, pinpoint impediments, and reflect on performance.
Here are some reports that Jira Software teams ought to be using to measure the most relevant and commonly used agile metrics:
- Jira Cumulative Flow Diagrams to identify your bottlenecks
- Jira Sprint Reports to track scope creep and team velocity
- Jira Version Reports to track release progress
- Jira Workload Reports to make sure your team members aren’t overwhelmed
- Jira Dashboards to look at the bigger picture, more than just your team/product
You might also want to have a look at Atlassian’s most commonly used agile metrics, too. (Although we would recommend you ignore the section about Control Charts; we’re not fans.)
4. Are your reports helping you stay on top of things?
If your delivery and/or quality are inconsistent, you’re taking too long to deliver value, or your backlog is growing faster than you’re burning it down, then it means you’re not doing enough reporting. And if you are doing a lot of reporting, it means you’re not doing it in the best way.
The true value of any report lies in the questions you’re asking it. So if your reports aren’t working, perhaps you need to refine your questions. Skip back to point 3 and check what it is you’re measuring, or maybe back to point 2 to ask why you’re measuring it.
In our article about the basics of Jira reporting, we listed the most likely questions that most teams will be asking, grouped under relevant headings. For clarity let’s repeat them here:
How much work is being completed per sprint?
How much of our planned work was completed?
What’s our variability/consistency?
How well can we plan?
Are we on track to complete our sprint goal?
Are we delivering what and when we say we will?
Is our backlog growing or are we burning it down?
Are we addressing enough bugs versus stories in each sprint?
How long does it take us to deliver value?
Where are our bottlenecks?
How well are we managing our work-in-progress?
5. Have you thought about data visualization?
Once you’ve decided what reports you’re building, you need to consider how you want the data to be displayed. This is key. A report is basically useless if the data presented isn’t clear, engaging, or memorable. So think about how you’re visualizing the data, i.e. what chart or graph you’re using, how it looks, and whether it communicates the message of the report in an easily digestible way.
Unfortunately, the out-of-the-box reports that come with Jira Software aren’t the most visually appealing, and the lack of customization that’s available doesn’t let you make them more so. Sure, they’re easy to build, but they might not be the right chart for your purposes, or be the right colors, or show the right amount of data.
It means you should invest in some better tools. Tools that give you more control over the way your data is presented. Custom Charts for Jira is one such tool – an Atlassian add-on that allows you to replace a number of the native reports in Jira Software with more visual and customizable ones.
For example, your only visualization option for workload reporting in native Jira is a pie chart. But pie charts aren’t the clearest, particularly if there are only small differences in workload between the assignees. In Custom Charts for Jira, you could visualize the workload as a bar chart instead, and adapt it to display custom names, percentages, different colors etc. Also, while a pie chart will show how much work an assignee has, what you may want to show is how many tickets they have in a specific status. In this case, a stacked/grouped bar chart might be more appropriate. There’s no way of creating a stacked bar chart in native Jira, but in Custom Charts, there is.
Many Jira Software teams also want to track the average age of unresolved issues in order to see how well they are moving through their backlog. However, the built-in bar chart is limited. We have recently added new calculate functionality to Custom Charts for Jira that now allows users to build a much more visual, colorful, and dynamic Custom Charts version of the Average Age report.
For more information about the importance of visualization in Jira, check out this article.
Dev teams that are always concerned with what they’re doing and never how they’re doing may miss opportunities for improvement that are fundamental to being agile. If you move through the checklist above and take full advantage of the reporting functionality in Jira Software, you will be able to extract significant business value from the work that you do. So before you embark on another reporting cycle, ask yourself these five questions and make sure that your reports are as meaningful and purposeful as they should be.
Remember, the need for good reporting is spelled out in the Agile Manifesto. And they say that what gets measured gets managed, so if you want to be a team that delivers, you have to measure what and how you’re delivering. At the end of the day, doing the work only matters if you’re doing it right.
Christopher is a self-confessed nerd who’d probably take the cake on Mastermind if Star Trek: Voyager was his specialist subject. He writes fiction about time travel, conspiracies and aliens; loves roller coasters, hiking and Christmas; and hates carpet, rom-coms and anything with chilli in it. He’s written extensively for technology companies and Atlassian partners and specializes in translating complicated technical concepts, specs and jargon into readable, benefits-driven copy that casual readers will understand.