Why big version trains are always late 15 Aug 2006
33 comments Latest by Harry Nieboer
There are many reasons why you shouldn’t smack version numbers on web applications, but the most important is to avoid a feature creep detour.
When people hear “version 2.0”, they think it’s the last call for the only feature train in a good long while. If you miss it, you’ll have to wait for the big three-oh to board. Nobody likes waiting, so they rush and they push to make this one.
Now the big version that started out with a clear vision, one or a few great ideas, suddenly gets bogged down by feature freeloaders. When the 2.0 train is already hauling those heavy weights, surely no one will notice this little thing or that little thing.
And what could have arrived in weeks turns into months. In no time short, your feature train is so overloaded that it seems like its not moving at all. Or going backwards. Certainly there is no one who can tell you when it’ll pull in.
So stop it. Don’t alias your next big feature idea “version 2.0”. Call your big idea by its name and it’ll be much easier to spot the freeloaders. Once they have to pay full scheduling fare, you’ll probably realize that they weren’t that important anyway.
That’s why we’re calling the next major revision of Backpack the “Widget Overhaul” and not Backpack 2. And that’s why we’re calling the one after that “Backpack Business” and not Backpack 3.