OUR TEAM
Tyler Richardson: User Interface, User Research and Manager - In charge of the background and impact of the project. Responsible for acquiring test subjects and real world situations of the project. Will also be responsible to fully understand the target audience and develop a plan to test and analyze user results. Basically oversees the entire operation of the project and the impact on stakeholders.
Joe Sluis: ROS Development and Stretch Guru - In charge of understanding the nitty-gritty of ROS and the tools/techniques and is responsible to assist the rest of the group with ROS related issues. Also in charge of working closely with the Stretch Robot and troubleshooting any issues while using the simulation or live robot.
Saket Gollapudi: Hardware, Robot Planning, and Design/Fabrication - Responsible for the hands-on aspects of the project and the development of physical parts of the project, (i.e. 3D design/printing, hardware dev). Will be the person overseeing any repair or development of any apparatus or extension that is required for the project.
Atharva Kashyap: Perception - In charge of understanding, developing, and overseeing the main software for the project. Is able to understand how to process sensor data and develop programs to efficiently analyze the data.
Jaden Summerville: Documentation and Communication - In charge of all the formal tasks and the presentation of the group. Responsible for making videos, taking notes, writing blog posts, giving presentations. Is the spokesperson for the group.
In our group we envision a cohesive partnership between all group members. While we have individual roles and responsibilities, we know that each group member is capable of handling any given task regardless of their technical background and given role within the group. That being said, we envision each member to lead a unique aspect of the project that best suits their backgrounds and meet the responsibilities required for each subdivision of the project. Additionally we also envision every member to have equal responsibility in development of the software aspect of the project. For each milestone in the project we hope to divide tasks evenly among each group member with each member responsible for their given weekly task. For weekly milestones we expect each member to proactively take their section of the codebase/project and complete it while having open communication between group members and providing checkpoints of their progress. For quarterly checkpoints we expect each member to verify the aspect of the project that relates to their assigned project role is up to date. Through this division of responsibilities we envision a cohesive and efficient system between all group members.
Additionally, there will be situations where every group member must be proficient in a certain skill within the project to guarantee project completion and success. For example in this project it is paramount that all users have experience in python and must know how to use ROS packages to manipulate the robot. In order to maintain consistency and proficiency of these skills among group members, we plan to incorporate a series of guidelines to ensure all team members acquire the knowledge and skills they hope to get out of the project. We will first have everyone complete tutorials surrounding the basic tools needed for this class before delving into the main codebase and project. Once everyone has completed these tutorials and feels comfortable with their proficiency, we will start delving into the implantation of the project. If there is a new skill that pops up while working on the project that requires extra practice, then we will collectively work on gaining the new skill through tutorials and readings found online, or by asking the course instructor while working on the project concurrently. If one group member is not proficient in a given skill, as a group we will work with the group member and help them to learn said skill and provide them with some tutorials to build on their understanding to gain proficiency. Through this system we hope to hold each other accountable and gain the necessary skills required to build a fully functional project.