Reports are intended to answer important business questions to aid in planning and decision making. Reports are only as good as their ability to be understood by their intended audience.
One of the biggest challenges in reporting is providing the right report to the right people.
VisualScript has a large variety of reports intended for software development teams like Velocity Reports, Dependency Reports, Roadmaps, and Burnup and Burndown Charts.
However, sometimes you just need to answer a quick question on a dashboard.
- Where are our bottlenecks in the development process?
- How many stories do we have per sprint?
- How many stories do we have per team and per sprint?
- How many stories do we have per fixVersion?
VisualScript includes standard reports like pie charts, bar charts, stacked area charts, stacked bar charts, line charts, gauges, and more just to answer quick questions like the ones above.
The idea with these standard reports is to have a report for every question asked right in your dashboard.
Let's go over some of the reports you could include in your dashboard.
Stacked Area Chart for Bottlenecks
The first report is a stacked area chart that helps us understand where our bottlenecks were/are per day by status.
The report shows a 2 week time period with the number of tickets by status per day. The larger the status represented by a color is in a day,
means the more tickets there are for that status in the day. This is not necessarily a bad thing, but it can identify if there
are bottlenecks so you can then research why and if it is a cause for concern.
The expanded view shows a grid so you can see day by day and status by status the number of tickets with hyperlinks.
What tickets were causing the bottleneck? Are there any commonalities between them? Was the same team working on all of them? Is it a training issue? Is it a process issue? These are just some of the questions this one report can help answer.
Number of Issues by Sprint
Perhaps you want to see the number of issues by sprint. Using a bar chart can help with this.
The bar chart below is set to show all unresolved issues by sprint. The report will look not only at the active sprint,
but each sprint that is configured for the future.
If you want to include resolved issues to see past sprints, you can do so with a simple parameter change and your report will look like the bar chart below.
Additionally, the expanded view will show you the number of issues per sprint with hyperlink to those issues.
Number of Issues Per Sprint for Multiple Teams
If you need to report on the number of issues per sprint for multiple teams, you can use a stacked bar chart.
This report can provide a quick view of just how much work the development teams are assigned per sprint.
If you want to see resolved and unresolved issues, you just have to change a simple paramater.
Issue Count by FixVersion
If you want to see the number of issues that are resolved and unresolved in a fixVersion, you can use a pie chart in your Jira dashboard.
You can report using the fixVersion field in the field dropdown available in the parameters. This helps teams to quickly see how many issues they
completed in a previous fixVersion, and even how many they are planning for future fixVersions.
The expanded view will show the number of issues with hyperlinks to them.
Gauge Report for Issue Counts by FixVersion
VisualScript gives you the flexibility to show your data in a way that makes sense to you and your stakeholders. If you want to see the
same data shown in the pie chart in a linear gauge report, you can do that easily. It requires the same exact data entry,
but provides a completely different visual representation of the data.
Issue Counts by FixVersion in Context of Both Teams and Sprints
What if you need a report to show the issues within each fixVersion by team assignment while also showing the sprint assignments for each story?
You can use one of the VisualScript in-context standard reports. The idea behind in-context reports is to provide the ability to include the
data points needed to not only report on an individual metric, but to show many different metrics that together provide the context.
They provide a deeper look into the data to help tell the overall story.
The report below is a grid that shows the fixVersion on the y-axis, and the component field on the x-axis. I am only reporting on unresolved issues.
Each shape represents an issue, and each shape includes a hyperlink to the issue, status, summary, and sprint assignment. So this report gives you a handful of data points per issue, that can be used to help answer multiple questions.
VisualScript Helps Software Development Teams See Metrics and Answer Questions Quickly
VisualScript's standard reports provide a lot of flexibility for software development teams to report on metrics when they need questions answered quickly. Visualize your metrics easily and make better data driven decisions.