Re:My 20-Year Experience of Software Development Methodologies
by fapjacks on Sunday October 15, 2017 @08:16AM
(#15476821)
What the parent means is: Can you point to any other (faddish) methodology that didn't come about in that way? Also, waterfall was provided in the original paper as a minimally-viable methodology of software development which was specifically recommended against. A kind of "If it comes down to using waterfall or using nothing, I guess use waterfall" type of thing.
[ Parent
| on HN ]
Re:My 20-Year Experience of Software Development Methodologies
by walshemj on Sunday October 15, 2017 @09:35AM
(#15477039)
ask the USA and UK MotorBike and Car industry about the "faddish" methodology the Japanese companies used to hand them their ass
Re:My 20-Year Experience of Software Development Methodologies
by fapjacks on Sunday October 15, 2017 @06:05PM
(#15479595)
But we're not talking about "the USA and UK MotorBike and Car industry" now are we? Or, you know, really anything but software development methodologies?
Re:My 20-Year Experience of Software Development Methodologies
by Nomentatus on Sunday October 15, 2017 @11:41PM
(#15480685)
Actually, I'd say the statistical methods used by the Japanese (mostly to zero in on sub-par team members by shuffling them through teams and measuring the results) do have some similarity to test driven development, and even the sort of frequent (rough) measurement that Agile allows.