Confirmed users
513
edits
Auto-tools/Projects/DevelopmentMetrics: Difference between revisions
Jump to navigation
Jump to search
Auto-tools/Projects/DevelopmentMetrics (view source)
Revision as of 22:19, 24 April 2017
, 24 April 2017less words
Klahnakoski (talk | contribs) (mention the reviews are broken) |
Klahnakoski (talk | contribs) (less words) |
||
| Line 21: | Line 21: | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
| style="vertical-align:top;width:300px;" | [http://people.mozilla.org/~klahnakoski/review/Review-byTop.html Top 30 Reviewers]<br><span style="color:red">Requires VPN | | style="vertical-align:top;width:300px;" | [http://people.mozilla.org/~klahnakoski/review/Review-byTop.html Top 30 Reviewers]<br><span style="color:red">Requires VPN. Allow mixed content.</span> | ||
| Shows the top reviewers from the past 6 weeks, the number of reviews they did, and the number in their queue right now. The original objective of this dashboard is to confirm some engineers have too many reviews. This dashboard is fine for identifying egregious differences, but poor for individual comparison; it seems personal style, team style, and code under review all impact the size and number of reviews done. | | Shows the top reviewers from the past 6 weeks, the number of reviews they did, and the number in their queue right now. The original objective of this dashboard is to confirm some engineers have too many reviews. This dashboard is fine for identifying egregious differences, but poor for individual comparison; it seems personal style, team style, and code under review all impact the size and number of reviews done. | ||
|- | |- | ||
| style="vertical-align:top;width:300px;" | [http://people.mozilla.org/~klahnakoski/review/ReviewIntensity_First.html Time to First Incoming Review] | | style="vertical-align:top;width:300px;" | [http://people.mozilla.org/~klahnakoski/review/ReviewIntensity_First.html Time to First Incoming Review] | ||
<br><span style="color:red">Requires VPN | <br><span style="color:red">Requires VPN. Allow mixed content.</span> | ||
| Counts review requests and review completion rates. Also breaks down aggregate review age. The first review has been shown to take the longest, probably due to people synchronization issues. Subsequent reviews were almost instantaneous, so we exclude them. This dashboard is not good for fine grained comparison of teams because the nature of the bugs, and the process used, is often too different. The response time INCLUDES WEEKENDS. | | Counts review requests and review completion rates. Also breaks down aggregate review age. The first review has been shown to take the longest, probably due to people synchronization issues. Subsequent reviews were almost instantaneous, so we exclude them. This dashboard is not good for fine grained comparison of teams because the nature of the bugs, and the process used, is often too different. The response time INCLUDES WEEKENDS. | ||
|- | |- | ||
| style="vertical-align:top;width:300px;" | [http://people.mozilla.org/~klahnakoski/review/Review-byReviewer.html Incoming Review by Individual]<br><span style="color:red">Requires VPN | | style="vertical-align:top;width:300px;" | [http://people.mozilla.org/~klahnakoski/review/Review-byReviewer.html Incoming Review by Individual]<br><span style="color:red">Requires VPN. Allow mixed content.</span> | ||
| Top reviewers, but this time with some breakdown by week and component. Interesting, but not actionable. | | Top reviewers, but this time with some breakdown by week and component. Interesting, but not actionable. | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
| [http://people.mozilla.org/~klahnakoski/review/ReviewIntensity.html Incoming Reviews] | | [http://people.mozilla.org/~klahnakoski/review/ReviewIntensity.html Incoming Reviews] | ||
<br><span style="color:red">Requires VPN | <br><span style="color:red">Requires VPN. Allow mixed content.</span> | ||
| Statistics for all reviews. Subsequent reviews of a bug happen much faster than the first. Maybe the fast review speed is an administrative anomaly; reviews are added after the fact, and marked as reviewed. Maybe, the requester and reviewer are working closely to remove the remaining nits. | | Statistics for all reviews. Subsequent reviews of a bug happen much faster than the first. Maybe the fast review speed is an administrative anomaly; reviews are added after the fact, and marked as reviewed. Maybe, the requester and reviewer are working closely to remove the remaining nits. | ||
|- | |- | ||