January 23, 2016 Leave a comment
After yet another session of re-explaining the bleeding obvious to thunderous silence, I decided on a fresh approach.
Commonly, we Agile practitioners start by explaining that software is not like building bridges. Building bridges is expensive, labour-intensive, and there’s really only one opportunity to get it right. “Big design up front” is deemed absolutely necessary, even though it doesn’t guarantee a successful outcome. We might even show them the hilarious (but fake) picture of a bridge that doesn’t line up where it’s supposed to meet.