> 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-instructions.md). # Peer Review Instructions Adapted from Source: ## **Preparation** Before completing the peer review, it is highly recommended that you familiarize yourself with your teammates’ efforts. A good approach is to review the design notebook highlights that have been posted on your team page. * [Team Red](https://maindl.ancorasir.com/?page_id=69) / [Team Green](https://maindl.ancorasir.com/?page_id=78) / [Team Blue](https://maindl.ancorasir.com/?page_id=87) / [Team Yellow](https://maindl.ancorasir.com/?page_id=95) * **To complete your peer review of the week, each student will need to submit this form for \[3 times] during the week of peer review.** ## **Scenario** You are in charge of dispensing compensation for your team. Your budget is ~~1000~~ 5 bonus points per team member and you are free to distribute this reward in any way that you see fit. You are being asked to make a general decision on the performance of your peers. In addition to the bonus allocation, your comments are extremely important for adjusting team member behavior, so please spend some time and be constructive. ## **The online form** The online form is intended to make the review process easy and discreet. Each of your task force or team members should be listed with a box for the amount you wish to give as his/her bonus (integer bonus points please). There is also a space for comments: what they should do less of, what they should keep the same, and what they should do more of. ![image.png](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fliz72SG2VHq4ab4qMVYb%2Fuploads%2FexMf8uU9lO79yhrsgAlp%2Fimage.png?alt=media\&token=ef50553e-0f51-4578-9f53-9ad7f3c95e5e) Be sure to evaluate your own performance and allocate some of the bonuses to yourself. ## **Review etiquette** Making thoughtful, honest comments is a very important contribution to your team’s performance. You must make an award to each team member (including yourself) and if there is a reason to enter a very large or small number, please make sure to include appropriate comments… a zero with no comment is just mean, not constructive. The form will only allow submission when the bonuses total 1000x the number of members on your team. If you get an error message just adjust the numbers so they add up and try again. [View Fullscreen](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fliz72SG2VHq4ab4qMVYb%2Fuploads%2FxXsAE1OVwC1Sb5S5eohk%2F13_biasInFeedback.pdf?alt=media\&token=beecfaf2-9543-42f9-8f7d-4e31b70589e0) [13\_biasInFeedback.pdf](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fliz72SG2VHq4ab4qMVYb%2Fuploads%2FxXsAE1OVwC1Sb5S5eohk%2F13_biasInFeedback.pdf?alt=media\&token=beecfaf2-9543-42f9-8f7d-4e31b70589e0) ## **Submission and distribution** Once you successfully submit your peer review, the results are automatically sorted and distributed accordingly, depending on which of the [4 peer reviews](http://web.mit.edu/2.009/www/assignments/PeerReviewAssignment.html) is being conducted. You always receive only the reviews that pertain to yourself. **Peer reviews are anonymous, your identity will never be revealed to those you are reviewing.** I’m ready to[**complete a peer review now**](https://x.ancorasir.com/me303-311/2020-autumn/project-work/me303-peer-review-of-design-notebook)! --- # 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-instructions.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.