Prototype Creation and Feedback

Class Plan

1. Announcements
1. Reminder of interview assignment.
2. Activity
1. Class time to finish up your prototype.
2. Prototype sharing with another team.
3. Remediation of prototype based on feedback (time allowing).
4. Prototype sharing with another team (time allowing).

Class Activity:

An in important task for a software engineering, and any professional, is the ability to provide and receive constructive feedback. Receiving constructive feedback is important for receiving information that can be used to improve the product. While not always easy, providing constructive criticism will not only help to improve the software project, but will enable the provider to consider improvements that can be made to their current and future products.

In today's activity, you will have the opportunity to provide and receive feedback regarding a prototype of your project.

Step 1: Time to complete prototype

As a team, complete your `Google Slides' prototype.

Step 2: Prototype Presentation

Using your `Google Slides' prototype, you will be paired with another team to receive feedback on your team's prototype.

1. Each team shares access/links to their prototype with the other team.
2. One team presents the general overview/idea of their application to the other team.
3. Teams then switch roles and the team that was presented to presents to the other team.
4. The testing phase then begins. Individually, each team member should silently: (5 minutes max)
• 'Test' the other team's prototype. Look for 'issues' (ambiguous steps, dead links, spelling mistakes, poor UI, etc....).
• Document observed defects.
5. Each team should designate one member to be the 'recorder' of observed defects. This document should be in a shared location, such as Google Drive - something that is accessible by all members of the team.
6. Each team will share their discovered defects with the other team. This should be done by each member providing feedback on their observations to the other team. The recorder should document these observations (5 minutes). Be sure to go slow enough to give the recorder sufficient time to properly document all discovered defects.
7. Teams will switch roles and have the team that first received feedback now provide feedback similarly with the recorder documenting all findings.

Submission Information

As a team, submit your:

• Team's prototype as a pdf (including a link to your working prototype).
• Observed defects (found by the other team).