Auto-tools/Projects/DevelopmentMetrics: Difference between revisions

remove vpn indicator
(Add neglected oranges)
(remove vpn indicator)
Line 22: Line 22:
| 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]<br><span style="color:red">Requires VPN</span>
| style="vertical-align:top;width:300px;" | [http://people.mozilla.org/~klahnakoski/review/ReviewIntensity_First.html Time to First Incoming Review]
| 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.
|-  
|-  
Line 28: Line 28:
| 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]<br><span style="color:red">Requires VPN</span>
| [http://people.mozilla.org/~klahnakoski/review/ReviewIntensity.html Incoming Reviews]
| 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.
|-
|-
| style="vertical-align:top;width:300px;" | [http://people.mozilla.org/~klahnakoski/review/Reviews_Pending_18.html Reviews Requested in the Past 18 weeks]<br><span style="color:red">Requires VPN</span>
| style="vertical-align:top;width:300px;" | [http://people.mozilla.org/~klahnakoski/review/Reviews_Pending_18.html Reviews Requested in the Past 18 weeks]
| An attempt to better understand the aggregate response time; while treating "old" reviews (those over 18weeks), as something else entirely.
| An attempt to better understand the aggregate response time; while treating "old" reviews (those over 18weeks), as something else entirely.
|}
|}
Confirmed users
513

edits