Cycle time (software)
In software engineering, cycle time is a software metric which estimates development speed in (agile) software projects.[1][2] 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."[3]
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.[4]
See also
[edit]Further reading
[edit]- What is waste? (Agile Alliance)
- Takt time - Cycle time (The Lean Thinker)
- Lead time versus Cycle Time – Untangling the confusion
Citations
[edit]- ^ "A Cycle Time Journey: 164 to 8 Days in 6 Months". Scrum.org. Retrieved 2021-02-16.
- ^ "Software Development Cycle Time - A deep dive". Hatica. 2021-11-12. Retrieved 2023-01-11.
- ^ Project Management Institute 2021, Glossary §3 Definitions.
- ^ Gunasekaran, A. (25 January 2001). Agile Manufacturing - 1st Edition. Elsevier. ISBN 978-0-08-043567-1. Retrieved 2022-08-22.
{{cite book}}:|website=ignored (help)
References
[edit]- Project Management Institute (2021). A guide to the project management body of knowledge (PMBOK guide). Project Management Institute (7th ed.). Newtown Square, PA. ISBN 978-1-62825-664-2.
{{cite book}}: CS1 maint: location missing publisher (link)
 | This software-engineering-related article is a stub. You can help Wikipedia by expanding it. |