> For the complete documentation index, see [llms.txt](https://x.ancorasir.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://x.ancorasir.com/me303-311/2020-autumn/project-work/peer-review.md). # Peer Review Adapted from Source: The peer review contributes to a [significant portion of your individual grade](https://x.ancorasir.com/me303-311/2020-autumn/course-overview/grading). Performance reviews are commonplace in the industry. Here, the goal of having anonymous reviews is to provide direct, peer feedback on your performance and contributions. This will help you improve over the course of the term. Additionally, we hope that during the review process you will also reflect upon your own contributions and thus gain experience in critically assessing your own efforts. Peer reviews are conducted using online forms, and four peer reviews are scheduled throughout the term. The first peer review is early in the term to provide initial feedback on performance within your section. The results of this survey are provided to students only. Instructors will not see the results. The second peer review is roughly 1/2 way through the term (after the mockup review) and is also intended to provide feedback to section members. The results of the survey are provided to both students and instructors, but they are not used for grading. Information is provided to instructors in the event that there are problems that may need assistance to be resolved. The third peer review is approximately 3/4 through the term and 1/2 way through the final prototyping stage. This review provides feedback from the entire team, not just your section. Again, instructors will also receive the information but it will not be used for grading. The 4th peer review is completed after the final presentation. This review is used for grading purposes, and to provide your team-members feedback. Before completing an online review, you will need to **read the** [**detailed peer review**](https://x.ancorasir.com/me303-311/2020-autumn/project-work/peer-review-instructions) **instructions.** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://x.ancorasir.com/me303-311/2020-autumn/project-work/peer-review.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.