Peer code review makes your improves the quality of your software and improves the productivity of your developers. So if you’re going to do it, you’ve got to do it right.
But how do you know which approaches are right for your team? Fortunately, there are proven methods of peer code review that will help you achieve your goals easily, economically and efficiently. This white paper discusses 11 best practices for effective, lightweight peer code review.
Using these best practices optimizes your code reviews, improves your code and makes the most of your developers’ time. They have been proven effective via scientific study and SmartBear’s extensive field experience.
Among the best practices you’ll learn are:
- How many lines of code you should review at a time
- What LOC/hour inspection rate is most efficient
- Establishing quantifiable goals and capture metrics to improve processes
- Fostering a good code review culture for positive morale
- Lightweight-style code reviews that are efficient, practical and highly effective
In this White Paper you will learn how defect density dramatically decreases when the number of lines of inspection goes above 200, and is almost zero after 400.