Start small. The biggest problem I have seen with efforts to do review in development is that the review itself ends up being overly complex and too large. For large projects with history, a review will naturally increase in size; for small projects, it should start small and grow as needed.
The second biggest problem I have seen is that too many times the peer review process is created and driven by someone who doesn't understand development processes well enough to grasp what a review should do, or can do. They use it instead to try to enforce quality, which doesn't work. By its nature a review will enhance quality over time, but it is not and should not be viewed as an enforcement tool.
- Keyboard Shortcuts:
Keep Up with TechRepublic