Risks
Changing Requirements
Given that "management" has a propensity to change deliverable requirements in the few days proceeding said deadline, our team has been in the position where we do not understand (or know) what we should be working on. We've had success dealing with this risk in the past with the use of our JiT (Just-in-Time) business model.
Communication and Collaboration
Given that we are not a business, but rather a class, all group members have different schedules and other outside requirements. Thus, a fair division of work and agreements on meeting times have caused some problems in the past. Additionally, we've had problems finding a meeting time with group 13, especially to deal with last-minute changes and additions (see the first risk).
Final Requirements Not Known
While we know week-by-week what we should be working on and the basic requirements for the robot system, we have no idea what the final "robot games" will consist of, meaning that we're working on a product whose use is not known. This will inevitably lead to changes in the requirements document and other specifications and several long nights toward the end of the semester when we should all really be studying for finals.
Problems & Changes — Communications Protocol
We need to discuss the format of strings passed over the socket connection and how to encode/decode them into our information, image, and control packets.
Problems & Changes — Requirements Document
We didn't identify any problems during pre-lab.