Project: LIBCLOUD

Introduction

This report provides an analysis of how regularly a team uses the Jira tool. Any tool usage, for example such as opening or closing a story or task, changing a value associated with a bug, or commenting on an epic, is counted when determining Jira usage regularity.

This report examines activities between 2015-06-24 and 2019-06-06.

Based on parameters selected when this report was generated, the analysis was done with the expectation that the team regularly used Jira at least every week. Of course, no team’s actions are performed in a perfect mechanical cadence. To reflect that a team’s actions are not mechanically perfect and some variation is reasonable, this report features two values:

Results:

  • The team is typically using Jira:
    • On average, every 0.53 weeks,
    • 50% of entries are made at a time interval of less than 0.32 weeks and 50% at a greater time interval,
    • The largest time interval between team entries into Jira is 4 weeks made on 2018-07-31.
  • The team’s Jira usage is meeting expectations, on average.
  • The team’s process performance index is Ppk = 0.55. This indicates that the team should work to improve how regularly it uses Jira. Note: ppk indicates the team’s potential for meeting expectations on a consistent basis, not whether it met expectations at a particular point in time.
A run chart of team Jira activities (rounded to the week-level)

  1. The process performance index, denoted Ppk, indicates if the team’s process is generally capable of meeting tool usage performance expectations, regardless of if the team meets the expectations or not on any specific day. In this report, a one-sided upper bound Ppu is used. The equation is \[P_{pu} = \displaystyle \frac{(USL - \overline{x})}{\hat{s}}\] where USL = week, \(\overline{x}\) is the mean of the data point values, and \(\hat{s}\) is the \(99.7^{th}\) quantile of the exponential distribution with \(\lambda = \frac{1}{\overline{x}}\).↩︎