» Summary


  • "private"
  • "in-company"
  • test your development strategies in confidence

Testimonial of a Private RAD Race

[ in Dutch ]

According to all people concerned, the first "LogicaCMG Internal RAD Race" (Rapid Application Development Race - in the "private" concept) (january 2005), was a great success. Meanwhile, a 2nd and 3th edition took place in 2006 and 2007.

Nine teams took the challenge to carry out the programming assignment within a limited time frame. Topic of the race: "seeing is believing". And, as it will become clear from the results of the RAD Race: the team which "programs" less, wins.

RAD Race LCMG teams 2005

RAD Race LCMG assignment


A participating team:

"To us, the RAD race was particular learning experience"..

It forced us to make fast and calculated choices within our team and to squeeze everything from our toolset. The assignment had been thoroughly developed and went a lot further than the usual "build-a-screen demo"; where you prove in fact nothing. Quick and dirty programming was of no use since changes and extensions on the existing code were required. And then it appears that there are good, better and best methods to tackle the matter. From the comparison with other teams we learned that a lot of issues still needed improvement. Our cooperation has only become better. And we improved and broadened our toolset. The race was also quite tense. For when the revenge?"


The organizer:

"I had never thought that it was possible for an event to go that well. Literally everything was well-considered and foreseen into the smallest detail. Both the teams and the jury members were excellently coached. The statement that "...you only need to fix a date and place and organize the catering to obtain a successful game and a particular event..." is by all means true. We look back on a pleasant cooperation and plan to make it an annual event."

RAD Race LCMG jury

A jury member:

"The "private" RAD race was a primer to me. After the introduction briefing it became clear that this was not an exercise without engagement and that the participating teams had to dig terrible deep in their resources to cope with the assignment. The combination of the better analysis work, thorough and applicable knowledge of both toolset and database proved to bear fruit. The jury was also in the privileged position to monitor the evolution in the construction of the task closely. They were able so detect at once which approach really worked. Afterwards, the operationality and the depth of the used (code) frameworks has been discussed at length. These insights have further refined our development strategy. Captivating and a must!

Detailed coordinates and references can be provided on simple request.