Formula One Racing Team Speeds to Agile Development
Lotus F1's IT team made a technology pit stop and changed from a traditional application development strategy to an agile approach. Why shift gears? The pit crew and car designer wanted better data faster -- and IT wasn't about to pass on the opportunity.
Mon, May 07, 2012
CIO — You hear a lot about organizations that must make split-second decisions or risk losing to competitors. Split-seconds? That's usually an exaggeration, unless you're talking about Formula One racing.
During the 90 to 120 seconds it takes to run a lap in Formula One, engineers in the pit crew use telemetry and business analytics tools to find adjustments to make on a car racing at speeds of more than 185 mph. Every fraction of a second does count, says Graeme Hackland, IT director for Lotus F1, a three-driver team co-sponsored by Lotus Cars and Renault. At a recent race in Bahrain, a Lotus F1 driver lost first place by just three seconds.
Racing to Agile Development
Lotus F1 recently ditched traditional application development methods for agile development, including scrum and visualization. The goal is to produce better tools faster for both pit crew and car designers. Hackland says he also wanted to erase the perception that sometimes IT doesn't understand everything about how the pit crew and car designers like to work. "They wanted us to deliver more right the first time," he says.
The continuous communication between developers and users under agile development can clarify how the end product should look, feel and work much earlier in the process, says Margo Visitacion, an analyst at Forrester Research. But organizations underestimate the culture shock of going agile. "Collaboration is a lot different from taking requirements, throwing them over a wall and expecting perfection many months later," she says.