Skip to main content
System StatusContact Support
VersionOne Community

Workitem Cycle Time Report

Editions

This feature is available in Catalyst, Enterprise, and Ultimate editions.

editions-ceu.png

NOverview

The Workitem Cycle Time By Status report indicates the average amount of time workitems (backlog items, defects, or testsets) spend in a range of selected status values.

Use this report to see the flow rate of items through the cycle.  This information provides visibility into past performance, helps to anticipate future delivery, and drives continuous process improvement.

WorkitemCycleTimeByPriority.png

Cycle Time is a Lean metric used to measure the time it takes for an item in the backlog to flow through the development process. It is similar to Velocity reporting, but typically has no emphasis on sprints. 

Accessing This Report

  1. On the main menu, select one of the following options:

    • Reports > Iteration Reports section > Workitem Cycle Time

    • Iteration/Sprint Tracking > Storyboard > Workitem Cycle Time (from the Reports drop-down menu)

  2. Select the report filters (described below), and then click Go.

Report Filters/Parameters

  • Duration: The number of days, weeks, or months to display.

    • For project-based reports, the default duration is the number of weeks from
      the project's start date to today.

    • For sprint/iteration-based reports, the default duration is the number of days in the
      sprint/iteration.

    • For member-based reports, the default duration is 13 weeks.

    • The report ends at the current date, so if the selected start date and duration
      extend past the current date, no data displays after the current date.

  • Team: Shows Team-specific data for the project or program. The default value is "All" or "Blank".
Start Cycle:
The cycle from which you want the report to start.

End Cycle: The cycle on which you want the report to end.

X Axis:
The current or final value on the workitem for the selected axis.

Technical Details

For each work item represented in this report:

  • The Start Cycle and End Cycle values are selected when configuring the board.  Please refer to the Story Board page for additional information. 

  • The query considers work items that are meet the selected Project, Program, Team, and that are in, or past, the End Cycle value in the duration selected

  • Cycle time is based on the work item's history and is not editable.

  • Cycle time counting is suspended if a work item is closed in the defined cycle range or if the work item is moved to a value outside of the defined range.  If the work item is re-opened or moved back into the defined cycle range, counting resumes where it left off. 

  • Counting continues when a work item is moved backwards in the defined cycle range. 

  • Any work item that skips the defined cycle range is not considered when calculating the average.  To skip the defined cycle, a work item is never assigned a value in the defined cycle range, but is assigned the End Cycle value or another value that is past the End Cycle value.

  • Any work item that enters the defined range, but skips the End Cycle value, is considered when calculating the average.  To skip the End Cycle value a work items is assigned a value in the list past the End Cycle value.

  • Any work item that is closed in the defined cycle range is not considered in the average because it never completed the cycle.  If this work item is subsequently re-opened, counting resumes where it left off.

  • Any work item that is deleted in the defined cycle range is not considered in the average because it never completed the cycle.  If this work item is subsequently un-deleted, counting resumes where it left off.

  • Counting does not stop when a work item with a values in the defined range is moved out of the selected Project context. 

  • Counting is not reset when a work item with a value in the defined range is moved into the selected Project context.

  • Unestimated items  are calculated as if the estimate value is zero.

  • The cycle time calculation considers calendar days.  Therefore weekends are always considered

  • The cycle time calculation does not consider Effective Asset state. 

  • Is a work item is copied, the new work item has it's own cycle time,