Team

Team Responsibilities

• Aidan Rudd - Software Lead

  • Creates original code and leads in modifying existing Arduino code

  • Performs Sensor Tests

• Matthew Bairstow - Hardware Lead

  • Researches and compares sensors and the tools and architecture around them

  • Developed testing rig design

• Jeffrey Tharakan - Tester 

  • Maintains website

  • Designs belt hardware components

  • Records system tests

• Jett Tinik - Tester

  • Records meeting documentation

  • Performs tests and records testing results

• Philip Mascaro - Tester

  • Builds test rig and collects data during tests

  • Purchases components and brings in hardware

Team Assessments

Our team meets twice a week on Tuesdays and Thursdays during class time to collectively work on the Personal Guide Belt and discuss our progress. The team adheres to the established schedule consistently and has always been flexible for moving locations if a new environment was preferred for different tasks. All team members have maintained excellent attendance, and in instances of absences, they gave generous notification and diligently made up for any missed work asynchronously. Delegation of roles within the team has been executed with precision.

While the team consistently maintains efficient meeting minutes, it has been noted that documentation on testing days could be more comprehensive, as the focus tends to prioritize testing and problem-solving activities. Team maintains appropriate and effective communications inside and outside of class. All team members are focused on task during meeting times, and jobs that aren't finished in class time are either handled outside meeting time as homework or are given set times to work on during meeting times. During meetings, we would discuss what components we should purchase, and we would purchase it within two days. We would also discuss a week ahead of time if we wanted to do an extensive physical test of the system, so that we could make sure to bring all larger test materials.