Confirmed or Busted: Are the Mythbusters Agile?

First published in The Agile Zone and Javalobby, 7 May 2013

In 2009 IBM invited a couple of well-known TV personalities to appear as keynote speakers at an international event. They were interviewed by Scott Ambler, who many will recognize as the driving force behind initiatives such as agility@scale and Disciplined Agile Delivery. That event was the IBM Rational Software Conference, and the two guests were Adam Savage and Jamie Hyneman. The show for which they were famous? The Discovery Channel's Mythbusters.

This series is enormously popular with technical types, and it's fair to say that it has earned something of a hallowed position in nerd culture. It's certainly a common topic at the water cooler for many in the IT business. I reckon that most of you will have seen an episode at one time or another, and a significant proportion of you are likely to be addicts. I don't even own a TV, but I've caught the show in hotel rooms when I've been on the road and found it to be similarly compelling. So for the uninitiated, here's the low-down on what it's about. In each episode the team will set out to prove - or to debunk - certain myths and urban legends. For example, in one episode they tested the myth that if a bullet is fired horizontally while another is dropped vertically at the same time and from the same height, they would hit the ground simultaneously (result: myth confirmed). They followed that up by testing the idea that it is actually possible for someone to be "knocked out of their socks" (result: myth busted). With backgrounds in the special effects business, and most likely a nod to Wile E. Coyote, the Mythbusters use plumbing, joinery, metalwork, explosives, electric circuits and a battered crash test dummy to build Rube Goldberg contraptions that put oddball claims to the test.

So where is the connection between this "seat-of-the-pants" engineering and agile methods? Why is this show so popular amongst agile developers, even to the point that Adam and Jamie appeared at the IBM Rational Software Conference keynote with Scott Ambler? Is there something in their approach to busting myths that resonates with modern software development practice? Or to cut to the quick: is there any truth in the assumption that the Mythbusters are somehow "agile" themselves? That's the myth that I decided to investigate. Will it be confirmed or busted?

A Seat of the Pants Investigation

For this evaluation, I watched some re-runs that were showing on my hotel TV. I sat in front of it with my laptop, and with no clear idea of method, but before long I found myself typing notes about the things I was seeing. Here's what I came up with.

Conclusion

So then, what does this brief examination of a handful of episodes say about the Mythbusters being agile? Does it take us any closer towards explaining their appeal to developers, and why they would be invited to appear as keynote speakers at a software conference? Before I started this cursory investigation I thought I could guess the answer. I thought the show was popular with developers not because the Mythbusters are "agile", but because uncool nerds want to associate themselves with cool dudes doing cool things, and which seemingly validate non-prescriptive, bare-to-the-metal practices. And to be honest I still think there's an element of truth in that. Yet the whole truth isn't so simple, and it seems to run deeper than I first suspected.

The show is pitched as a way of getting people interested in science, and the application of scientific method does appear to be a recurring theme. Agile practice is a reflex of scientific management and it too makes extensive use of observable results to facilitate the inspection and adaptation of a process. As such, the scientific approach taken by the Mythbusters cannot in itself be used as evidence of agility. There is also no evidence of regular time-boxing either for the elicitation of metrics or for the control of scope. The management of technical debt is erratic even though the principles and risks seem to be generally understood by the team. There is however very good evidence of team collaboration, and for the controlled inspection and adaptation of the myth testing process. In one case a "pivot" was done that echoes the market-driven agility of the Lean Startup movement (in their conference appearance Adam & Jamie mentioned rapid course changes by cast and crew when prompted by Scott Ambler to discuss their work in the context of agile practice). In most episodes there is a clear hacker ethic that underpins their methodology, and they rarely use prescriptive approaches to evaluate myths. The only exception that I saw was the debunking of the "faked moon landing" allegations, but this discrepancy may be explainable by context.

So are the Mythbusters agile? I'd really need to make a more detailed examination of the series to state an opinion. However from what I've seen so far, and as the team themselves would probably say...myth plausible.