How does Time In Process (TiP) differ from ALM's Cycle Time reports in CA Agile Central Insights?

Products

• Rally SaaS

Issue/Introduction

How does Time In Process (TiP) differ from ALM's Cycle Time reports?

 

Environment

Release:
Component: ACSAAS

Resolution

ALM's cycle time reports calculate story TiP as the difference between that last time the story went In Progress and when it was Accepted. Transitions back to In Progress, such as In Progress -> Defined -> In Progress, will reset the calculation.

Insight's story and defect TiP uses a more sophisticated TiP calculation that includes all the time the story or defect spends In Progress, and takes into consideration workdays and holidays. Insight's TiP charts do not include stories and defects that spend no time in process, such as stories or defects that move directly from Defined -> Accepted or Released.

Feature TiP is calculated slightly different from story and defect TiP. Feature TiP is the the time between when the first story parented to the feature moves to In Progress and when the feature reaches 100% complete by story count. If an In Progress story is reparented to a feature, the timing begins at the time of the reparenting. Feature TiP also takes into account work days and holidays.

Additional Information

P50 is not the average, P50 is the 50th percentile, i.e. a value which is less than exactly 50% of the items in the list.

So, given TiP values for a group of stories as 9.5, 6.13, 4.63, 4.00, 3.63 and 0.00

Since there are an even number of items in the list, it chooses the midpoint between the two middlemost values, 4.63 and 4.00. (4.63 + 4.00) / 2 = 4.315.