Peer review

At the end of iteration 3, each team should conduct a review of the work performed by another team, covering the following points:

• Code review. Pull the code from the source code repository, build it and analyze the source code. List the bugs you found, design issues, antipatterns, inefficient code, etc.
• Installation test. From the source code, get the application up and running in your environment. Describe the problems you faced and propose solutions to ease the installation.
• Acceptance test. Taking requirements into account, check the functionality of the application and verify whether it corresponds to the requirements. Make sure what features are supposed to work in the version you are conducting tests upon, you might need to communicate with the reviewed team for this.

If your project has been reviewed by another team, take time to analyze the issues raised, determine if any action needs to be taken, and if necessary, create the tasks in your issue tracker to address the most important issues identified during the peer-review. At the end of iteration 4, you need to submit a "Peer-review response" explaining which of the issues raised in the peer-review of your project has been addressed, and why you have not decided not to address the remaining issues.

You start by picking a project you like to review and announce your selection as a reply to the peer-review kickoff message. If a project has already been picked, you cannot select this project again. You need to pick another project. The idea is that every team should prepare a review for another team AND should hopefully receive a review from another team as well.

Your peer-review and your response must be accessible from your Wiki's front page.

If your project collaboration infrastructure is private, you need to give access to it to the student(s) who will peer-review you... If your customer does not want anyone besides your team members to access the project, please let your mentor know this so that we can find an alternative approach.

The deadline for the peer-review is marked in the Deadlines page. The deadline for entering your "response" to the peer-review you received is the deadline of Iteration 4.