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!

Form: To what extent has this group . . .

Used the memo format modeled in Markel page 255?

Yes. Modeled correctly

Limited their proposal to two pages or less?

Yes. a little long though

Designed their proposal (e.g., headings, bullets, timeline, etc.) logically and effectively (think

alignment and consistent font use)?

Yes.

Content:

Abstract: to what extent has this group . . .

summarized its project using the exact device name?

Yes.

explained why their project is important in under forty words?

Abstract longer than 40 words.

It would help to talk more about the scope of the proposal. Not just including what they

propose to do but also what you are not proposing to do (Markle, p.302). This can clear up

inconsistencies like whether we are supposed to disassemble or repair objects.

Introduction: to what extent has this group . . .

 included background information about their device?

Yes. However the person perspective switched between the abstract and introduction.

provided a convincing rationale for their project?

Yes. Clear and concise. could improve on justifying their claims. Markel says that Every

word you sayor dont saywill give your readers evidence on which to base their

decision (Markel, p. 301)

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

Described the five troubleshooting topics it will write about for iFixit (e.g., device wont

turn on, or touch screen unresponsive)?

Yes.

Described the five replacement guides it plans to write for iFixit (e.g., replacing the battery,

or replacing the screen).

Yes.

Included all the information required by iFixit on the proposal page?

Missing camera details at bottom of the proposal, and did not mention target audience.

Timeline: To what extent has this group . . .

Shown iFixit when theyll achieve each of iFixits Milestones using an easy-to-read grid or

list?

Yes.

They could add a list of evaluation techniques that the team will perform in order to

determine whether the proposed project is both effective and efficient (Markle, p. 307).

This could be something like adding a column to check off milestones/assignments as they

are completed.

Readability: To what extent does this groups proposal . . .

 Use concise language?

Yes. Just improve minor grammatical errors, less sentence leads and shorten abstract.

Use language in a way that never impedes readability?

7/10.