15 minute rule

If you have a problem, if no-one else can help, and if you can find them, maybe you can hire the A-Team.

For those of us that are not so lucky to find the A-team, we need another solution. A nice rule I saw implemented in my Lviv team is the 15 minute rule. If you run into a problem and don’t see how to fix it withing 15 minutes…. ask one of your colleagues to assist.

This leads to faster problem solving and more knowledge sharing!

(And it’s always nice referring to the A-team ;))


Update Feb. 11 2011:  Part of the solution is explaining your problem to somebody else in your own words. By explaining it, often you already find the solution.



A week or two ago we started with some Componence colleagues with Robocode. Robocode is a game where robots fight each other. The can shoot, scan for other robots, drive, etc. The funny thing about Robocode is that you program your own robot in java. And you can start out really easy, with the absolute minimum of java coding. So it’s a nice way of learning java, practising coding, but also really seeing direct results!

Rutger was really inspired, so he has the best robot for now. But it looks like maybe this week John will beat him… we will see tomorrow. Inspired by the Tour de France Rutger decided that the robot who scores most points in a big match with all robots earns the red jersey (meaning the robot should be completely red). The robot with the most kills in one-on-one fights get the yellow jersey. Of course all other robots are not allowed to use these colors.

After the first week our PM people were winning from our programmers. Strange? I don’t think so. We were focusing on fast results, getting the robot to drive, turn, shoot. The experienced programmers… they are building complete classes, working out the robot in every detail.

I guess next Friday will be the turning point when well build, lot’s of code, robots will beat the just-try-something-robots.