ScrumDo's aging reports expose a number of different dimensions related to how long work spends in certain states. Dimensions can be established within Report Profiles (i.e. - positions on your board) or based on tags assigned to your work cards.

Aging reports can help answer questions like:

  • When a card is marked as Blocked, how long does it usually stay like that?
  • Which step in the process takes the longest to complete?
  • What impediments cause the most delay?

Time in State Histogram

The Time in State Histogram lets you look at a single step or tag and see the distribution of how long cards spent in that step.

In the example below, we are looking at cards that were in the Developing step. We can see that 18 cards spent 0 days in this step (they were moved in and out the same day) , 3 cards spent 4 days, and one card spent a 7 days.

Aging Breakdown

The aging breakdown report allows you to analyze multiple states or tags and compare how long cards spent in these steps. 

In this example, we are looking at cards that were in the Developing and Testing steps:

Relative Time

The Relative Time chart lets you see the relative amount of time cards spent in steps or tags. 

In this example, we've generated a report to better understand our testing and development states, and can easily see the total time work spends in development is a bit more than the total time it spends in testing for this project / workspace.

How we calculate

This report counts all time that a card is in the given state (either tagged or in a report profile step). If you apply filters to the report, those filters are only considered for when the card enters the target state as of that time.

NOTE: When a card is moved to the backlog or archive, it has no report profile step but it does retain it’s tags.

Some tips

When reporting by tag, it only really makes sense to choose tags that are transitory in nature. For instance, if you regularly mark cards as #blocked when they have an external dependency, and then remove that tag when it is no longer true.

Planning out how you use tags can help you get a lot more information out of these reports. For instance, if you want to be able to figure out which impediments are taking the most amount of time, you might want to consistently use tags like:

  • blocked-dba
  • blocked-client
  • blocked-ops

These tags will allow you to run reports that differentiate between reasons why a card was blocked.

Note on Tags Data:

The tag based aging report only includes history after June 4th, 2015 as that is the day we began tracking data at the detail required to build the report.

Did this answer your question?