5 ms·
I am ambivalent about "the difficulty lies not in defining [useful software methodologies], but in convincing others to follow [them]." Currently, I see too mu
by mannykannot 9y ago
I am ambivalent about "the difficulty lies not in defining [useful software methodologies], but in convincing others to follow [them]."
Currently, I see too much faith being put in methods of dubious utility. I see techniques, that may be effective when applied judiciously in some circumstances, being promoted to universal principles. In particular, I see the failure of waterfall being taken to mean that any attempt to think ahead is counterproductive.
On the other hand, ten years before the scope of this article, Barry Boehm took on the waterfall model with an iterative one that emphasized frequent reevaluation of where you are, where you are going, and what impediments you face [1]. The fact that this article begins with waterfall supports the notion that adoption is the problem. Perhaps Boehm's model was largely overlooked precisely because it was not dogmatic enough to promote zealotry?
[1] https://en.wikipedia.org/wiki/Spiral_model https://en.wikipedia.org/wiki/Spiral_model
- snarf21 9y agoVery true. I've found at every company that I've worked at that a "bad" process followed consistently by everyone always outperforms the "perfect" process followed haphazardly. This reminds me of the recent threads about people using Excel instead of "real" software. At the end of the day, you are trying to add value. As long as you aren't adding technical debt or other risks, the how matters much less.
- specialist 9y agoMethodologies are just virtue signals. Project management is just the self soothing that people do to pretend we’re not all just a bunch of howler monkeys fighting over whatever kibble is left over after the job creators take their share.