2 ms·
If they're duplicating, I agree high certainty can be had. But once modifications happen, I think you're headed back to the other end of the Wardley spectrum.
by wpietri 10y ago
If they're duplicating, I agree high certainty can be had.
But once modifications happen, I think you're headed back to the other end of the Wardley spectrum. Do the modifications meet user goals? Do they meet business goals?
In those circumstances, the only way you can return to high certainty is by creating very firm specs and resisting change orders. From the perspective of a contract development shop, I'm sure that's fine. But for the people actually paying for the software, that's a process smell.
The commercial and practical validity of modifications can only be fully evaluated by shipping. But large specs require long release cycles. This creates a long period where learning is deferred. Estimates only become manageable because the project is saving up trouble for later. A period of artificially high predictability will be followed by a period of artificially low predictability.
And even in the pure duplication case, what comes after that? I can't think of many successful pieces of software that stopped at 1.0. Once the duplicate is released, most businesses will need to respond to their customers, doing novel and innovative things specifically for them. So at best, you're back in the fast-cycle end of the spectrum. But at worst, you have executives who are attached to specs and estimates and long timelines, which are the wrong tools for innovation. You have development processes that match. And you probably have a code base that's not set up for flexibility.
Given that, even if I were, say, making that AWS competitor, I'd still use all my tools from the fast-cycle innovation end of the spectrum. Because even a pure duplicate assumes that a) there is nothing left to learn, and that b) the context of sale/use is not changing. Estimation is always a bet that you won't learn anything important between the start and the end. Given how smart my colleagues are, that's a bet I'm rarely willing to make.