2 ms·
In Wardley's model, almost no software development should take place in the "six sigma" zone. Consider figure 1 here: http://blog.gardeviance.org/2015/10/agile
by wpietri 10y ago
In Wardley's model, almost no software development should take place in the "six sigma" zone. Consider figure 1 here:
http://blog.gardeviance.org/2015/10/agile-vs-lean-vs-six-sigma.html http://blog.gardeviance.org/2015/10/agile-vs-lean-vs-six-sig...
It says "Six Sigma/Outsource" for a reason. The product is "ordered, known, measured, standard, obvious, low margin". If at all possible, this should be an off-the-shelf choice. Previously, that would have meant packaged software; now it mostly means getting something as a library or service.
Six Sigma is fine for manufacturing low-margin items, because you are trying to get high repeatability in the world of atoms. If you have one widget and need to make one million more, you use Six Sigma. But with bits, we already have near-perfect repeatability. If I have one integer and need a million more integers, the computer will do that at a reliability level well beyond six sigmas.
If software is being made in the Six Sigma/Outsource zone, it mostly means that one is reinventing the wheel. Sometimes that's necessary for historical reasons. E.g., if I'm working in a new language but need a library that doesn't exist yet, sometimes I really can just take the old spec and implement it anew. Or if I want developers to use my cloud service, maybe I need to just reimplement chunks of the AWS API, because Amazon won't give me that code.
But the great majority of software development should take place in the higher-novelty zones, where reliable project-scale estimation is somewhere between impossible and nonsensical.
(As an aside, casting people you disagree with as children is insulting.)
- _Codemonkeyism 10y agoYes you're right in principle and I agree. Though some of my clients create software for others duplicating and modifying existing products with high certainty.
- wpietri 10y agoIf 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.