Customized Pivot Tables for In-Depth Data Analysis

Pivot tables are a powerful tool for data analysis that offers flexibility, efficiency, and insights, enabling users to make informed decisions and drive business outcomes effectively.

They allow you to analyze data, find correlations, and identify trends deeply. You may not need it and are satisfied with the usual simple reports. There have been situations where you would like to dig deeper and understand specific indicators in more detail, but the reluctance to look for tools for this stopped you. Or you need to learn how to use pivot tables in your workflow.

Let's analyze a few case studies where pivot tables become an indispensable assistant and guide to the world of insights.

giphy.gif

Pivots table view in Time in Status app

To illustrate the use cases, we use the Time in Status for Jira app by the SaaSJet.

In the app, you can customize tables for your needs using the following options: 

  • Track the duration of status changes across various issue fields or their combinations, such as assignee time per status and time spent in status by Epics, and compare status durations for your team.
  • Manipulate data by math functions (Average, Min/Max, Count, Sum).
  • Display data in numerical or % view.
  • Sorting and Filtering according to your needs.
  • Three types of Layouts.
  • The export option is available.

pivot 1.png

Calculating time in status for linked issues across projects

For example, you need to display the time in the status for interrelated tasks. That is when changing the status of a task in one project requires changing the status of a linked task in another project.

Unfortunately, it is not possible to display this information using only the built-in functions of Jira. However, we can generate the desired report with the assistance of the pivot table view in Time in Status for Jira.

So, we have the following initial data:

  1. The team manages two Jira Service Management (JSM) projects.
  2. Tasks within both projects are interconnected (one task is linked to another).

In the given context, involving multiple JSM projects and dependencies on linked issues with distinct workflows, computing the time spent in status or duration offered significant insights into the efficiency and efficacy of support and service resolution workflows.

Following a straightforward process and employing a JQL query, users can generate a tailored report detailing the time spent in status for linked tasks across various JSM projects.

pivot 2.pngpivot 3.png

Using this report, the user can now measure and learn end-to-end resolution duration, resolution time for supporting issues, comprehensive-time evaluation, issue-specific performance metrics, etc. 

Estimate Time and Story Points in Pivot Table

By analyzing time and story point estimation in a pivot table, you can gain valuable insights into developer performance, sprint progress, and resource utilization, helping to optimize workflow efficiency and achieve project objectives effectively. 

  1. Choose the Time in Status report and the required Sprint.
  2. Next, on the Field tab, select the following settings:pivot 4.png
  3. Click on the gear icon to filter statuses while assignees are actively working on issues, following your workflow, and proceeding to apply the filter. For illustration, let's consider "In Progress" as a representative example.pivot 5.png
  4. You can uncheck issues with blank and 0 estimations to get only the evaluated ones.pivot 6.png

As a result, you will get the time in progress and story points for each assignee.

pivot 7.png

With such a report, you can get answers to important questions and insights about your workflow that will help you optimize it or allocate resources better.

 For instance: 

  • Which developer completed the highest number of story points compared to the original estimate?
  • How does each developer's performance compare in terms of story points completed?
  • Are there any trends or outliers regarding the time spent on ongoing issues?
  • Which developer efficiently utilizes their time to close the most story points?
  • Is there a correlation between time spent in progress and the number of story points closed?
  • How effectively is the development team progressing towards completing the sprint goals?
  • Are there any areas where developers may need additional support or resources?
  • How consistent is each developer in meeting their estimated story points?

Determine the duration spent by each assignee in each status

By analyzing the duration spent by each assignee in each status, you can gain valuable insights into workflow efficiency, identify potential bottlenecks, and make data-driven decisions to optimize processes and improve overall project performance. 

  1. Choose the Time in Status report and the required Sprint or Project
  2. Next, on the Field tab, select the following settings:pivot 8.png

As a result, you will get the Assignee Time per Status.

pivot 9.png

By determining the duration spent by each assignee in each status, you can gain insights into several aspects of your project workflow, including: 

  • Which assignees tend to spend more or less time in specific statuses?
  • Are there patterns indicating efficient or inefficient use of time by certain assignees?
  • Are there statuses where assignees consistently spend more time than expected?
  • Do certain statuses tend to delay overall progress in the workflow?
  • Are there areas where workflow automation or process improvements could be implemented to reduce time spent in certain statuses?
  • Are all assignees evenly distributed across different statuses, or are there instances of workload imbalances?
  • Can you identify assignees needing additional support or training to improve efficiency in certain statuses?
  • How does the time spent by each assignee in various statuses compare to expectations or benchmarks?
  • Are there assignees who consistently perform well regarding time management and adherence to workflow statuses?

Takeaway 

To summarize, everyone needs deep data analysis. When you look at a project/sprint in general, you only sometimes have the opportunity to see the details. And as you know, the devil is in the details. Even a tiny nuance can introduce an imbalance in the workflow and significantly reduce team productivity. 

To help you break down your data into small pieces and analyze it qualitatively, we offer you a 30-day trial. Also, we will be happy to meet you on a demo call and tell you more about Time in Status for Jira app and how you can implement it in your workflow.

See you at SaaSJet! 🙂

0 comments

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events