Team Contract Assessment

Description

The team contract assessment assignment is a question-based assignment describing whether the obligations set out in the team contract were met. Project groups should individually complete the questionnaire available on Canvas. Here are some of the grounds using which you should formulate your answers:

Project Goals: This section should begin with a short description of what you planned on building at the start of the semester. What were the goals of your project? You should elaborate on whether these goals were met.

Expectations: This section should address whether the expectations set in the “Expectations” section in your team contract were met. Essentially, were the ground rules your team set out at the start of the semester followed?
Roles: At the beginning of the course, your team outlined roles as part of the team contract. Please describe what your roles are now and–if your roles changed–how they evolved as the semester progressed. Did you assign a leader? Were pieces of the project tackled as a group or individually? Why?
Agenda: How did your team make decisions about the project? How were goals set? When an issue with the project came up, how did your team plan to fix it?
Team Issues: This section should cover team-related issues that your group encountered during the course. What sort of problems did you run into? How were they dealt with? Was the process set out in the team contract followed? In hindsight could you have done things differently to have a better team experience?

Requirements

Each section should report adequate depth and completeness when addressing all relevant questions.

Submission and Deadlines

The team contract assessment document is a group assignment and should be submitted on canvas before the deadline listed on the Calendar.

Featured Project

The idea of this project would be to improve upon the 395 project ‘Smart Frisbee’ done by a group that included James Younce. The improvements would be to create a wristband with low power / short range RF capabilities that would be able to transmit a user ID to the frisbee, allowing the frisbee to know what player is holding it. Furthermore, the PCB from the 395 course would be used as a point of reference, but significantly redesigned in order to introduce the transceiver, a high accuracy GPS module, and any other parts that could be modified to decrease power consumption. The frisbee’s current sensors are a GPS module, and an MPU 6050, which houses an accelerometer and gyroscope.

The software of the system on the frisbee would be redesigned and optimized to record various statistics as well as improve gameplay tracking features for teams and individual players. These statistics could be player specific events such as the number of throws, number of catches, longest throw, fastest throw, most goals, etc.

The new hardware would improve the frisbee’s ability to properly moderate gameplay and improve “housekeeping”, such as ensuring that an interception by the other team in the end zone would not be counted as a score. Further improvements would be seen on the software side, as the frisbee in it’s current iteration will score as long as the frisbee was thrown over the endzone, and the only way to eliminate false goals is to press a button within a 10 second window after the goal.