The purpose for the Fall Quarter Peer Reviews is to share your project’s background, scope, and deliverables with your fellow students and to assess the feasibility of your project’s goals and objectives. Your team will have an opportunity to deliver a 10 min powerpoint presentation with 3 min for questions and answers. Your presentation will be recorded to give you feedback and to help improve your presentation skills. There is no specific structure for your presentation but it must include the following:
- Title and tagline – provide the title and tagline for the project
- Project Picture – original content that graphically depicts your project or element(s) of your project
- Background – provide introduction and context for the project
- Goal and Objectives – describe the purpose (what are you’re trying to achieve). List objectives that support the goal
- Specification – showing that you understand the design requirements
- Timeline – show a simple straightforward schedule with major milestones
- Progress – what have you done, what are you doing, and will you be doing?
- Budget – provide the budget estimate for the project
- Resources – team members and advisors, number of units taken and the total hours committed to the project this quarter
- Subsystem Breakdown – for larger teams, show how your project is divided
Frequently Asked Questions (FAQs)
Rubric
Your peers will score your presentation based on the rubric below. The rubric will be weighted in accordance to the aforementioned purpose. The scores for all projects will be posted for comparison purposes.
| Project Definition | Exemplary 4 | Proficient 3 | Apprentice 2 | Novice 1 |
| 1. Background | Detailed background, previous work, prerequisites, and motivation were highlighted to show project significance. | Project background, previous work, and motivation were discussed. | Incomplete discussion of the background and motivation. | Background and motivation were not discussed. |
| 2. Goal and Objectives | Well-defined goal. In-depth objectives are aligned to achieve goal. | Defined goal with objectives to support it. | Weak goal with incomplete objectives. | Inconsistent goal and objectives. |
| Project Management | ||||
| 3. Organization | Functional responsibilities of all project members are aligned to a work breakdown structure. | Functional responsibilities of each member are clear. | Functional responsibilities of some members are not clear. | No functional responsibilities were identified. |
| 4. Timeline | Detailed timeline consistent with work breakdown structure showing, milestones, deadlines, and deliverables. | Timeline shown with milestones, deadlines, and deliverables. | Timeline is too general or unclear. | No timeline presented. |
| 5. Progress | Excellent progress. Task management is clearly shown. Team members are actively working on tasks and delivering results to ensure project success. | Good progress. Evidence of task management albeit with less structure. | Some progress. The team can benefit from task management. | Little progress shown. |
| Technical Approach | ||||
| 6. Specification | Superior understanding of the design requirements. Demonstrated the ability to create a comprehensive specification. | Design requirements were understood and a specification was produced. | Mismatch between design requirements and specification. | Did not understand the design requirements. |
| Realistic Constraints | ||||
| 7. Budget | Detailed budget that is well thought out. | Budget presented and is complete. | Budget presented but is questionable. | No budget presented. |
| 8. Feasibility | Objective(s), scope, and approach are feasible and can be completed in agreed time frame. Your peers will score your presentation based on the rubric below. The rubric will be weighted in accordance to the aforementioned purpose. The scores for all projects will be posted for comparison purposes. | Objective(s), scope, and approach seem feasible, but may take longer than originally projected. | Objective(s), scope, and approach need to be reworked. | Objective(s), scope, and approach are not feasible. |
| Presentation | ||||
| 9. Visual Communication | Excellent, relevant, compelling visual aids depicting the project and/or the elements of the project. | Clear visual aids depicting the project and/or the elements of the project. | The visual aids are unclear. | The visual aids were not useful. |
| 10. Delivery | Clear, polished, confident. | Understandable and comfortable. | Understandable yet tentative. | Delivery detracts. |