Improve bottlenecks in your software development lifecycle
You can use Cortex MCP to quickly identify bottlenecks that are slowing your teams down, and use these insights to take action and track progress with Custom Dashboards.
Step 1: Use Cortex MCP to identify bottlenecks
First, you can use Cortex MCP to quickly identify bottlenecks in your version control metrics across the organization.
Use a prompt such as What are the bottlenecks in my version control metrics org-wide?. The MCP will respond with an analysis of version control bottlenecks. Review the bottlenecks to understand what areas you should focus on.

In our example, the MCP flags the following:
Review pickup is the primary bottleneck.
Cycle time being lower than any single stage of review latency signals heavy overlap and/or outlier effects. Improvement should focus on accelerating reviewer response.
Some teams have much longer wait times for first review.
Another metric to watch is open PR count per team or repo.
Follow the MCP's recommended next steps
The MCP will also generate a list of suggestions to take action on the identified bottlenecks.
In our example, the MCP made the following recommendations:
Set and enforce review SLAs on time to first review.
Use Cortex Metrics Explorer to drill further by repository and reviewer to pinpoint which repos feed the extreme outliers.
Close abandoned PRs.
Step 2: Create a Custom Dashboard to track progress
In Cortex, create a Custom Dashboard to visualize the bottleneck. Add modules to the dashboard based on what was flagged by Cortex MCP.
Last updated
Was this helpful?



