Using LinearB Insights

All Categories

You've got the data. What do you do now?

7 articles by 1 author

How to - Handle Large Pull Request

How to - Handle Large Pull Request. Why Is It a Problem? Small and digestible pull requests, helps developers to "cap" the risk of introducing new bugs or "break" production. When the pull requests d…

How to Address Hanging Review Requests and Long Reviews

Reviews are important "team" task. Reviews affect both quality of code and delivery. Hanging reviews slows down the cycl…

How to Address High Risk Work

How to Address High-Risk Work. What is high-risk work? LinearB classifies high-risk work as branches with more than 100 code changes, and also over 50% of these changes are rework or refactor work. W…

How to Address Pull Request Merged w/o Review or with Basic Review

How to Address Pull Request Merged w/o Review or with Basic Review. Why Is It a Problem? Even the best developers can make mistakes or miss things. After coding for a period of time and self-testing,…

Strategies to Identify and Reduce High Pickup Time

Continuous improvement thrives when your team responds quickly to pull requests (PRs) and keeps the review process moving smoothly. High pickup time can hinder your team's efficiency, as PRs that rem…

Using Team Iteration Summary in Pulse

The Team Iteration Summary in Pulse provides a concise, AI-generated overview of your team’s performance across a completed iteration. It highlights key accomplishments, delivery insights, and missed…

What do I do if my review time is high?

It's integral to a continuously developing team to be reviewing code as close to real-time as possible. Here are some ways to reduce review time.