Sunday, October 18, 2009

Robot Building

This week in class we did something a little bit different. We divided into groups and were each given a box which contained the parts necessary to contract a robot. We had 3 hours to complete 3 tasks:

  1. Build the robot to specification
  2. Make the robot move forward until it hit an object, then pick it up
  3. Make the robot complete a lap of the circuit, navigating around an object
Each team had a bag of poker chips which represented the groups budget. Every 15 minutes the group would lose a chip if they hadn't reached the pre-appointed target on time. Martin Hughes acted as a concultant who could be called in, but at a cost. He also informed us beforehand that 1 piece was missing from each kit and that if the group guessed in the first 15 minutes, they would get it free. After that, it would cost a chip.

As we had a group of 4, we divided into 2 teams of 2 in order to complete the construction of the robot. This worked well and we were able to complete the robot in a relatively quick time and run the demo, which worked fine. With the next two tasks, we were not as successful, however. In order to program the robot to performt the afore-mentioned tasks, we had to use the software that was provided with the set. This proved more difficult than we imagined, and we had basically no success with either task. All the while we were losing chips until our kitty was empty. Soon after, time ran out.

After the exercise, Martin explained that he had been trying to teach us that in business, there are always problems that you dont consider. He removed one piece from the set to distract us, which it did. Also, when he was going round taking chips, he was stealing 1 or 2 extra each time. He also made us aware of the fact that we should have used the chips to call him in, and then consult with other groups. Finally, he told us that we should have broken into 2 teams from the outset - 1 for harware, 1 for software.

All in all, I found the exercise to be an enjoyable experience but also a harsh lesson in project management.

No comments:

Post a Comment