Frequently Asked Questions: Contributor XP and Cycle Time
This section addresses common questions about the Contributor XP and Cycle Time feature in devActivity.com, helping you better understand and utilize this valuable analytics tool for your team's retrospectives.
Frequently asked questions
How did each team member perform in terms of XP and Cycle Time during this retrospective period?
The 'XP and Cycle Time by Contributor' table provides a row for each team member, displaying their individual Cycle Time and XP (SCORE) for the selected period.
Who demonstrated higher or lower contributions, or had longer or shorter Cycle Times?
You can visually identify this by comparing the raw Cycle Time and XP values, and more easily by observing the 'TO AVG' and 'TO PREV.PERIOD' columns, which show percentage differences.
How does an individual's current performance compare to the team average?
The 'TO AVG' column for both Cycle Time and XP (SCORE) explicitly shows the percentage difference of an individual's performance compared to the team's average for the same period.
How has an individual's performance evolved compared to their previous period?
The 'TO PREV.PERIOD' column for both Cycle Time and XP (SCORE) indicates the percentage change in an individual's performance compared to their own preceding period.
What specific performance anomalies or trends require further investigation during a retrospective?
Look for significant percentage changes (especially large positive or negative deviations) in the 'TO AVG' and 'TO PREV.PERIOD' columns, highlighted by red or green colors, to pinpoint anomalies or strong trends.
What are the potential reasons for observed performance metrics and how can they be addressed?
While devActivity provides the data, understanding the 'why' requires team discussion during retrospectives. Reasons could include project complexity, new technologies, personal learning, external factors, or process bottlenecks. Addressing them involves collaborative problem-solving and action planning.
What do 'No Pull Requests for this period' or 'No XP earned for this period' mean?
These indicators mean the contributor did not have any pull requests processed or did not earn any XP during the specific period selected for the report.
Are the percentage changes color-coded?
Yes, green typically indicates an improvement (e.g., shorter Cycle Time, higher XP), while red signifies a decline (e.g., longer Cycle Time, lower XP).
