On Time Delivery
When a major express mail company promises “on time delivery” I think we all know what they mean. In software, I’m not so sure.
In a previous post I talked about multitasking: when it’s appropriate and why. One of my key assumptions was that software deliverables result from tasks that are finished — completed. If so, then multitasking was not good for developers.
But let’s check that assumption. Maybe the software market is a market where
Partial results matter, and
Any late result is worthless
For example, if you’re running for a plane and lose a shoe. Better to make the plane and buy new shoes at the other end, right?
Some questions arise, though:
How partial can the initial result be and still matter?
Partial in features or partial in quality?
Is a later corrective delivery a separate, on-time delivery, or a completion of the initial delivery, thereby making it late?
How much fun is it to always be running half-barefoot for a plane?
What I do know is that when my express mail package comes damaged, missing items, or late, I demand my money back. If it happens twice, I switch carriers.
P.S. What happens when the client you were going to visit by plane is on the plane, sitting next to you?