Sweetr Docs home page
Search...
⌘K
Login
Get Started
Get Started
Search...
Navigation
Team Insights
Time to approve
Documentation
Repository
Give Feedback
Welcome
Intro
Get Started
Features
Alerts
Digests
Work Log
Pull Requests
Work In Progress
Teams
People
Code Reviews
Team Insights
Intro
Code review distribution
PR size distribution
Cycle time
Time to first review
Time to approve
Time to merge
Automations
Integrations
About Us
Principles
Open Source
Data-privacy & Security
Roadmap
On this page
Demo
Insights
What good looks like
How to improve
Bad practices
Team Insights
Time to approve
Time elapsed between ready to review and approval.
Demo
Insights
This chart can help you measure and answer questions like:
Are code reviews a bottleneck?
Is the defect rate related to the review process?
Are the recent process changes effective?
Are there any recurring patterns or periodic fluctuations?
What good looks like
Ideally, most Pull Requests should be approved within hours of its creation, but it can vary significantly depending on the context, such as the complexity of the project and the size of the Pull Request.
How to improve
There are some strategies that can help your team’s time to approve.
Visit this data during retrospectives and discuss options with the team.
Outline requirements well in tickets.
Keep Pull Requests small.
Keep process lightweight.
Automate as much as you can.
Leave code styling for Linters. Focus on business logic and architecture.
Encourage the team to communicate and ask questions early.
Encourage the team to review their own work before requesting reviews.
A even better way to understand how to improve is to go through
the pull requests
and assess the common causes for delay:
blocked due to nitpicks.
missing requirements.
code quality issues.
delay on first review.
too many changes.
Bad practices
It’s very important to know how this data should
not
be used.
Do not
obsess over improving this metric.
Strive for a good balance of code quality vs speed instead.
Ready to unlock continuous improvement in your team?
Try now
Time to first review
Time to merge
Assistant
Responses are generated using AI and may contain mistakes.