Guide: Analyzing Cycle Time by Contributors in devActivity

The Cycle Time by Contributors chart in devActivity provides critical insights into your team's development workflow. This guide will walk you through how to access, interpret, and leverage this powerful analytics tool to identify bottlenecks and drive efficiency.

Getting Started with Cycle Time by Contributors

1. Navigate to Analytics: From your devActivity dashboard, go to the 'Analytics' section.
2. Select Work Quality: In the sub-level menu, choose 'Work Quality'.
3. Locate the Chart: Find and click on the 'Cycle Time by Contributors' widget.
4. Understand the Visuals: The chart displays individual contributors, each with an avatar and a horizontal bar. This bar is segmented to show the duration a pull request spends in 'Coding' (light blue), 'Pickup' (medium blue), and 'Review' (dark blue) phases. Durations are displayed for each segment and as a total for the entire Cycle Time for each contributor.
5. Apply Filters for Deeper Insights: Use the available filters (e.g., time period, specific employees, teams, repositories, and pull request labels like 'feature', 'bug', 'improvement') to segment data. This helps you understand how different factors impact cycle times.
6. Compare and Identify Patterns: Compare Cycle Times and phase durations across contributors to identify patterns, strengths, and areas needing improvement. Look for contributors with exceptionally high 'Pickup' or 'Review' times, which might indicate bottlenecks.
7. Export Data: Utilize the 'Download' icon to export chart data (e.g., to CSV) for further analysis or reporting outside devActivity.
8. Access AI Insights (Premium): For premium users, click the 'AI Insights' (sparkles icon) for automated analysis and recommendations based on your data. This can highlight key trends and suggest actionable improvements.

Key Insights & Actions to Take

By analyzing this chart, you can:

• Pinpoint Bottlenecks: Identify slow code pickup or lengthy review times, indicating areas for process optimization.
• Evaluate Code Review Efficiency: Determine if you have enough reviewers or if the review process itself needs streamlining.
• Guide 1-2-1 Coaching: Use individual Cycle Time data to inform coaching sessions, focusing on supporting contributors with below-average performance or negative trends.
• Optimize Team Iterations: Identify contributors who need to optimize their Cycle Time to ensure faster overall team delivery speed and iteration cycles.
• Inform Retrospectives: Bring data-backed insights to team retrospectives to discuss workflow improvements and celebrate successes.
• Set Goals and Alerts: Utilize Challenge thresholds to set appropriate goals and actualize Alert thresholds for instant notifications about activity bottlenecks.