How ConnectALL Calculates Lead Time and why measuring Cycle Time is important

Lead Time was borrowed from Lean Manufacturing principles. In software development, Lead Time is the time elapsed between the identification of a software requirement and delivery to the customer. When calculating lead time for work items, such as user stories, flowing between multiple Agile Planning tools - it is important to focus on the overall time elapsed between the status changes of the focus requirement. In this short discussion and demo, we will focus our attention on how lead time was calculated for a particular change requested from our Product Owner to an existing application. I will show you the progression of that User Story through multiple tools and how ConnectALL recognizes the time elapsed from initiation to fulfillment. Many practitioners make a clear distinction between Lead Time vs. Cycle Time as it relates to Software Development. Lead Time is often defined & measured from a "user's point of view" whereas the latter is often defined from a "developer's point of view". ConnectALL calculates lead time from the moment a request is submitted (from the customer) to when it is fulfilled. Our indicator to track the elapsed time is the status and timestamps of the work items flowing through an organization's value stream. On the other hand, cycle time is measured from the moment a work item (e.g., a user story) is started (e.g., in progress). In this discussion and demonstration, we will show you how ConnectALL detects and measures both metrics across multiple Agile Planning tools.