Post 21: Team Reflection

Overall, we thought our teamwork went pretty well in our project. We generally split up our tasks well between all of us at the beginning so that each of us could focus on the things that we wanted to get out of this class. Along the way, we ended up naturally splitting up the parts of tasks belonging to specific roles to balance out workload and optimize our individual strengths, such as the Documentation and Communication role. The responsibilities belonging to some roles that we didn't really think too much about at the beginning were naturally taken up such as Manager and User Feedback Researcher since we didn't explicitly assign those along the way.

The two main department structure for vision and pathfinding worked well, but because of the split, integration between these two parts was left until the end which did cause us some trouble as we were rushing to finish the project. Ideally, a less clear divide between the two teams might have lessened this issue. However, as originally predicted, the split made it easier for us to work on the project while providing us enough flexibility to continue to succeed in other classes.  The Discord group chat was really helpful in allowing us to communicate and view updates in a quick simplistic manner. 

In the end, we followed the plan pretty well and worked on our assigned technical roles. Our goal of maintaining good communication, flexibility, and a positive mindset really made working with the team an enjoyable experience. We worked well as a team to achieve what each of us said we would do and if the quarter was longer, we could have implemented our more ambitious stretch goals. An improvement to the team would have been more regular team meeting outside of lab/lecture hours because that would have allowed us to start on the actual implementation of the system earlier since most lab/lecture hours involved running through the ROS labs. We are proud of the work, effort, and results we put in and achieved for our Stretch Robot project.