Our actual timeline reveals a skewed workload, where a lot of work was done post week 6. Because our robot ended up having many moving parts (drive train, catapult, winch, latch, load), our time allotted for getting these parts actuated was not nearly enough.
Another thing that we failed to consider was that each part, especially where a motor is involved, has to be tuned and appropriate. If our initial motors were adequate for the function they were ordered for, we would have saved lots of time. Determining the appropriate motors and mechanisms should come under the design phase.
Overall we needed to allot more time to debugging and fixing issues as they come up. Because our assumption for the time required to debug was shorter than necessary, we ended up continually behind schedule (as parts or mechanisms fail our expectation, we can't move on because we need to fix the failed component first).
Week 2: Order necessary parts, decide on a design for the group.
Week 3: Build base and assemble hardware.
Week 4: Build prototype with hardware and electrical components.
Week 5: Finish prototype with basic/little logic. (Initial Prototype)
Week 6: Implement sensors, robot-control communication
Week 7: Implement robot commands and actions
Week 10: Testing, Tuning, improvements as necessary.
Week Final: Final testing and performance.
Catapult:
Hopper
Wheels