Ir al contenido

Translations:Revisión por pares/2/en

De Scrum Manager BoK

Peer review also serves as an enabler for spreading knowledge across the team: reviewers learn about parts of the system they may not have known, and those whose work is reviewed learn about alternatives and good practices.

Origin

Although this technique comes from scientific publishing, where it has been an integral part of the publication process since the mid-20th century, it has taken root in software development. References to it can be found in CMMI guides (in the Verification Process Area) and in Eric S. Raymond's book The Cathedral and the Bazaar.

Basic considerations

It is advisable to keep the following basic considerations in mind when introducing this technique in a development team:

  • Peer reviews aim at the early identification of errors, so they should be carried out incrementally as stages of development are completed: several small reviews are better than a single review at the end of development.
  • The focus of peer reviews must always be the code, not the person who wrote it.