Help

analytics

How to Analyze Contributor XP and Cycle Time for Retrospectives

The 'XP and Cycle Time by Contributor' table on devActivity.com's Retrospective Insights Details page is a powerful tool for understanding individual developer performance. Follow these steps to effectively analyze the data and prepare for insightful retrospective discussions.

Screenshot of devActivity's Contributor XP and Cycle Time table
Quickly identify performance trends and outliers for each contributor.

Steps to Analyze Contributor XP and Cycle Time

  1. Navigate to Retrospective Insights

    First, log in to devActivity.com. From the main navigation, go to the Analytics section, then select the Retrospective Insights - Details page. The 'XP and Cycle Time by Contributor' table will automatically load, displaying data for your selected period.

  2. Review Contributor Metrics

    The table lists each CONTRIBUTOR, showing their specific CYCLE TIME and XP (SCORE) for the selected period. Cycle Time indicates the duration taken to complete work, while XP (SCORE) represents experience points earned. Note that if a contributor had no activity, you might see indicators like 'No Pull Requests for this period' or 'No XP earned for this period'.

  3. Compare to Team Average and Previous Performance

    Crucially, examine the 'TO AVG' and 'TO PREV.PERIOD' columns for both Cycle Time and XP. These columns show the percentage differences:

    • TO AVG: How the contributor's metric compares to the team's average for the current period.
    • TO PREV.PERIOD: How the contributor's metric compares to their own performance in the preceding period.
  4. Identify Trends with Color-Coded Indicators

    Observe the color-coded percentage changes for quick insights:

    • Green: Generally indicates an improvement or positive change (e.g., shorter Cycle Time, increased XP score).
    • Red: Generally signifies a decline or negative change (e.g., longer Cycle Time, decreased XP score).

    For example, a green '-100%' for Cycle Time 'TO AVG' means a significant improvement (much shorter cycle time relative to the average), while a red '+100%' for Cycle Time 'TO PREV.PERIOD' means a considerable increase (longer cycle time) compared to their previous performance.

  5. Utilize Data for Retrospective Discussions

    Use the visual data and comparative metrics to identify performance anomalies and discuss potential root causes during a retrospective. This data empowers you to formulate actionable strategies for improvement in subsequent development periods, understand individual growth, and address areas needing support.

Frequently asked questions

Where can I find this table?

Navigate to the Retrospective Insights - Details page within devActivity.com's Analytics section.

How do I compare individual performance?

Review the 'TO AVG' and 'TO PREV.PERIOD' columns for both Cycle Time and XP to see percentage differences compared to the team average and the individual's previous performance.

What do the colors mean?

Green indicates a positive change or improvement (e.g., shorter Cycle Time, increased XP), while red signifies a negative change or decline (e.g., longer Cycle Time, decreased XP).

What if a contributor has no activity?

The table will display 'No Pull Requests for this period' or 'No XP earned for this period' for contributors with no relevant activity.

How can I use this data in a retrospective?

Use the visual data and comparative metrics to identify performance anomalies, discuss potential root causes, and formulate actionable strategies for improvement.

Track, Analyze and Optimize Your Software DeveEx!

Effortlessly implement gamification, pre-generated performance reviews and retrospective, work quality analytics, alerts on top of your code repository activity

 Install GitHub App to Start
devActivity Screenshot