English 360 Proposal Peer Review Sheet

Instructions: With your iFixit team, read two other teams iFixit proposals and give feedback for the
following categories. Each group member should save this document for their portfolio!
PROPOSAL:
Form: To what extent has this group . . .
Used the memo format modeled in Markel page 231?
Limited their proposal to two pages or less?
Designed their proposal (e.g., headings, bullets, timeline, etc.) logically and effectively (think
alignment and consistent font use)?
-Combine both memos (iFixits and Dr. Bruces)
-Yes, less than two pages.
-Lacking headings such as: Abstract, Introduction, etc.
-The troubleshooting URL should be WIKI

Content:
Abstract: to what extent has this group . . .
summarized its project using the exact device name?
explained why their project is important in under forty words?
-Yes, used exact device name
-Need to explain why project is important, not state the request for authorization

Introduction: to what extent has this group . . .

included background information about their device?
provided a convincing rationale for their project?
- Yes, background information is good.
- Unnecessary to include where other considerable amount of repair information can be found.

Project Description: to what extent has this group . . .

Expressed the troubleshooting topics it will cover as user experienced problems?
Described the replacement guides it plans to write for iFixit (goal should be 5 guides; e.g.,
replacing the battery, or replacing the screen).
Included all the information required by iFixit on the proposal instruction page?

-Try simplifying headings. For example, Laptop overheating due to clogged fan vents should be
Laptop overheating
-Try to relate the guides to the troubleshooting ideas.
-Yes, included all info for the proposal instruction page.

Timeline: To what extent has this group . . .

Shown iFixit when theyll achieve each of iFixits Milestones using an easy-to-read grid or
list?
-Replace bullets with Milestones

Readability: To what extent does this groups proposal . . .
Use concise language?
Use language in a way that never impedes readability?
-Yes, almost too concise. (a little vague)
- For the most part, readable but adding headings and small issues would help.

EMAIL:
To what extent does the teams email follow the eight Netiquette Guidelines described on Markel page
256-7?
One sentence is not enough to judge. Add a little more to make it more personal.

To what extent does the teams email contain all the parts shown in the sample email shown on Markel
page 256 (e.g., subject, greeting, and purpose paragraph).
No Team Tag, purpose paragraph, or subject.

PRAISE: Two things this team has done well are . . .

-Conciseness is good and also troubleshooting points.