[Collapse]Collaborator 10
 [Expand]General Information/viewarticle/80040/
 [Expand]Getting Started/viewarticle/80359/
 [Expand]Collaborator Server/viewarticle/80060/
 [Expand]Web Client/viewarticle/80107/
 [Expand]Desktop Clients/viewarticle/80151/
 [Expand]Version Control Integration/viewarticle/80048/
 [Expand]External Integrations/viewarticle/80340/
 [Collapse]Techniques & Best Practices/viewarticle/80403/
   Invite A Colleague/viewarticle/80083/
   Review Pools/viewarticle/80092/
   Multiple Change Changelists/viewarticle/80307/
   Optimal Review Size/viewarticle/80404/
   Metrics: Definitions/viewarticle/80338/
   Metrics: Analysis/viewarticle/80407/
   Tips and Tricks/viewarticle/80402/
   Improving Performance/viewarticle/80121/
Updated: 12/23/2016 Applies To: Collaborator 10 Rating: GoodGoodGoodGoodGood 1 vote(s) Click to rate: PoorNot badAverageGoodExcellent

Techniques & Best Practices

Top |Previous |Next

Optimal Review Size

We sometimes get asked by customers how large their reviews should be. It is a difficult question to answer because it depends a lot on the review culture of the team and the nature of the content being reviewed. Opinions vary widely on what the optimal size should be.

Creating many tiny reviews is not optimal because of there is some static overhead for each review (setting up participants and metadata, and so forth). There is also a mental penalty for "context switching" when a reviewer changes their attention between two different reviews.

Creating a few giant reviews is not optimal because there is a limited amount of time a reviewer can truly concentrate on a review. Our studies have shown the maximum time to be about 90 minutes. If the review is too large to process in 90 minutes then the review is less effective - defects will be missed and time will be wasted as the reviewer's attention wanders.

Based on our research we recommend the following Optimal Size for reviews, with the understanding that one size does not fit all:

3 participants
15 files, 3 versions each (3 changelists)
2 overall defects, 5 file defects
30 file conversations
8 comments per conversation

Collaborator is designed to give the best experience at this size. However we do try to support a wide range of sizes so that customers can do what works best for them. Note though that reviews that are more than an order of magnitude larger than this Optimal Size will start to perform sluggishly.

See also

Best practices for peer code review - a web site article that describes a successful peer review strategy.

© 2020 SmartBear Software. All rights reserved.
Email Send feedback on this document