Skip to main content
All CollectionsAnalytics
Work Quality Analytics
Work Quality Analytics
Updated over 4 months ago

Permissions

Org Admin

Team Manager (for assigned team)

Org Contributor

External Contributor

View

View

View

No access

Cycle Time

devActivity's Work Quality Analytics provides a powerful tool for understanding your team's performance and identifying areas for improvement. This section delves into key metrics like Coding Time, Pickup Time, and Review Time, offering insights and actionable recommendations to optimize your development process.

Coding Time

Get Answers to These Questions

  • What type of contribution is dominating for a specific team/contributor? Are certain team members or teams primarily focused on code commits, while others are heavily involved in pull requests?

  • Do you need to rebalance the attention of contributors to other types of contributions? Is there an imbalance in the types of contributions, potentially leading to bottlenecks or missed opportunities?

  • Do you have enough team members to perform Code Review efficiently? Is the workload for code reviews distributed fairly, or are certain individuals overloaded?

  • Are commits and pull requests balanced? Or do you need to correct the work chunks teams are operating? Are teams committing too much code at once, leading to longer review times and potential issues?

  • Is there a known reason for someone strongly ahead or behind the rest of the team? Are there factors like vacation, onboarding, or specific project assignments influencing individual performance?

Recommended Actions

  • Discuss the insights on retrospective. Bring these insights to your team's retrospective meetings to foster open discussions and identify areas for improvement.

  • Make sure all team members are familiar with the analytics. Encourage team members to explore the analytics themselves to gain a better understanding of their individual and team performance.

  • Ask for the reasons and proposals from contributors strongly below average. Provide a safe space for contributors to share their challenges and propose solutions.

  • Use team and individual Challenge thresholds to set appropriate goals and forward attention to necessary types of contributions. Adjust challenge goals to encourage a more balanced distribution of contributions.

  • Make sure alert thresholds are actualized to get the instant notification and make corrections right away, not at the end of the period. Set up alerts to trigger notifications when specific metrics exceed thresholds, enabling immediate action and preventing potential bottlenecks.

Pickup Time

Get Answers to These Questions

  • What days are likely to be more/less active? Are there specific days of the week where pickup times are longer, indicating potential scheduling conflicts or team availability issues?

  • What period likely was a vacation period? Do you notice a significant drop in activity during specific periods that coincide with known vacation times?

  • How does the team structure impact the activity over a longer period? Do you observe any trends in pickup times related to team size, skill set distribution, or project phases?

Recommended Actions

  • Consider the meetings list for the less active days of the week. Ensure that important meetings are scheduled strategically to avoid overlapping with peak activity periods.

  • Plan the vacation schedule ahead. Coordinate vacation schedules to minimize disruptions and ensure adequate coverage during peak periods.

Review Time

Get Answers to These Questions

  • What days are likely to be more/less active? Are there specific days of the week where review times are longer, indicating potential scheduling conflicts or team availability issues?

  • What period likely was a vacation period? Do you notice a significant drop in activity during specific periods that coincide with known vacation times?

  • How does the team structure impact the activity over a longer period? Do you observe any trends in review times related to team size, skill set distribution, or project phases?

Recommended Actions

  • Consider the meetings list for the less active days of the week. Ensure that important meetings are scheduled strategically to avoid overlapping with peak activity periods.

  • Plan the vacation schedule ahead. Coordinate vacation schedules to minimize disruptions and ensure adequate coverage during peak periods.

Deploy Time (Coming Soon)

Get Answers to These Questions

  • What days are likely to be more/less active? Are there specific days of the week where deploy times are longer, indicating potential scheduling conflicts or team availability issues?

  • What period likely was a vacation period? Do you notice a significant drop in activity during specific periods that coincide with known vacation times?

  • How does the team structure impact the activity over a longer period? Do you observe any trends in deploy times related to team size, skill set distribution, or project phases?

Recommended Actions

  • Consider the meetings list for the less active days of the week. Ensure that important meetings are scheduled strategically to avoid overlapping with peak activity periods.

  • Plan the vacation schedule ahead. Coordinate vacation schedules to minimize disruptions and ensure adequate coverage during peak periods.

Recommendations

  • Use filters by repository and label to identify work quality metrics for specific segments of your project. Focus on specific areas of your project to gain deeper insights and tailor your actions accordingly.

  • Consider challenges related to cycle time and review time to impact metrics. Set up challenges that encourage faster code reviews and shorter cycle times, driving improvements in work quality.

By leveraging devActivity's Work Quality Analytics, you can gain valuable insights into your team's performance, identify areas for improvement, and optimize your development process for greater efficiency and productivity.

Questions, Ideas, Improvements

Did this answer your question?