|
|
|
|
|
by drtse4
4334 days ago
|
|
The fact that you were downvoted is extremely sad. Downvoters, good luck understanding how the next crappy project[1] you'll inherit was supposed to work without even a one-line specification describing what the reasoning behind certain choices was! Everything about methodologies should be taken with a grain of salt, what works somewhere, with a specific set of people and for some projects is not guaranteed to work anywhere. And not every aspect linked with "old" methodologies should be viewed as pure evil. Consider that many of the ideas that ended up in the agile manifesto could already be found in Peopleware from the eighties and that no methodology is the last. There was Waterfall, RUP and other clones, with the Agile wave someone defined XP (now dead) and after that Scrum. Now even Scrum is seen as something with too much overhead and people start turning to custom solution that use kanban/kaizen/etc... [1] Referring to a project that has some logic worthy of benig explained, interaction with external components, ecc... not some CRUD. |
|