Cycle time refers to the total time taken for a pull request to move from being opened to being merged. It is composed of three parts: first response time, rework time, and merge time. First response time is the duration until the first review comment. Rework time is the period until first approval after the initial review. Merge time is how long it takes for an approved pull request to finally be merged into the codebase. The document also defines rework cycles as periods where a developer addresses review feedback and resubmits the pull request.

1. Middleware Glossary
Cycle Time
Cycle time is the time taken by a Pull Request(PR) from Open to Merge. As stated in the diagram below.
Please note: The time is measured from the PR Opened​time and not from the time of first commit.
Cycle time is composed of 3 times:
1. First Response Time
2. Rework Time
3. Merge Time
​
​
Cycle Time

2. First Response Time
The time in which the PR got the first response - whether a comment/change request/approval. This is calculated as the time between
First Review(or comment) and PR Open time
Rework Time
Time taken for a PR to get an approval. This is calculated as the time between First Review​and First Approval​
. Further approvals do
not hamper this metric.
PS: PRs who get direct approval have 0 (Zero) rework time.
Rework Cycles

3. A rework cycle is defined as the activity where a developer works on the requested changes on the PR. A PR can have multiple rounds of
reviews and hence multiple rework cycles
Merge Time
Time taken for an approved PR to get merged. This is calculated as the time between PR Merge​and First Approval​
​
​
Rework cycle