Cycle time (software)

{{Short description|Measure of software development speed}}

In software engineering, cycle time is a software metric which estimates development speed in (agile) software projects.{{Cite web|title=A Cycle Time Journey: 164 to 8 Days in 6 Months|url=https://www.scrum.org/resources/cycle-time-journey-164-8-days-6-months|access-date=2021-02-16|website=Scrum.org|language=en}}{{Cite web|date=2021-11-12|title=Software Development Cycle Time - A deep dive|url=https://www.hatica.io/blog/cycle-time/|access-date=2023-01-11|website=Hatica|language=en-US}} The cycle time measures how long it takes to process a given job - whether it's a client request, an order,  or a defined production process stage. The crucial aspect of measuring the cycle time is considering only the active, operating processing time and discarding any idle, waiting, or service times occurring mid-process.

According to the PMBOK (7th edition) by the Project Management Institute (PMI), cycle time is the "total elapsed time from the start of a particular activity or work item to its completion."{{sfn|Project Management Institute|2021|loc=Glossary §3 Definitions}}

In contrast to lead time, which measures the time that the customer waits for their request to be realized, cycle time only counts the time the team spends actively working on the request. The core use of cycle times is to identify the average development times for specific teams or given request types. This lets the software engineering manager predict team engagements and better schedule work.{{Cite book |title=Agile Manufacturing - 1st Edition |url=https://www.elsevier.com/books/T/A/9780080435671 |access-date=2022-08-22 |website=www.elsevier.com|date=25 January 2001 |isbn=978-0-08-043567-1 |last1=Gunasekaran |first1=A. |publisher=Elsevier }}