Sweetr Docs home page
Search...
⌘K
Login
Get Started
Get Started
Search...
Navigation
Team Insights
Time to first review
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
Team Insights
Time to first review
Time elapsed between ready to review and first review.
Demo
Insights
This chart can help you measure and answer questions like:
Are Pull Requests reviewed promptly?
Are code reviews a bottleneck?
Are the recent process changes effective?
Are there any recurring patterns or periodic fluctuations?
What good looks like
Ideally, most small Pull Requests should be reviewed within hours of its creation. Team members should prioritize moving together as a team over their own individual work.
How to improve
There are some strategies that can help your team’s time to first review.
Visit this data during retrospectives and discuss options with the team.
Strive for smaller Pull Requests.
Automate the process as much as you can.
Make it clear to the team that reviewing code is a priority.
Simplify your reviewer assigning process.
Ready to unlock continuous improvement in your team?
Try now
Cycle time
Time to approve
Assistant
Responses are generated using AI and may contain mistakes.