2 ms·
> There's nothing wrong with any of that, and a lot that's quite good. There's a lot wrong with it. The problem with even these four foundational principles is
by thenanyu 3y ago
> There's nothing wrong with any of that, and a lot that's quite good.
There's a lot wrong with it. The problem with even these four foundational principles is: there are a significant % of situations where they are the exact wrong thing to do. Sometimes they are good! Sometimes they are very very bad.
There's no replacement for good management and judgement.
Individuals and interactions over processes and tools — there's a lot of value in having things done in a standard manner. Most of the time, you shouldn't try to be a special flower.
Working software over comprehensive documentation — have you ever seen a team develop themselves into a corner? Or run head first into a pit of real-life complexity? Try implementing USB without comprehensive documentation.
Customer collaboration over contract negotiation — customers will often take advantage of you. Both internal and external customers. The contract helps a lot when the customer is antagonistic.
Responding to change over following a plan — sometimes you should just stick to the plan.
- psunavy03 3y agoOnce again, someone mistakenly assumes that the Agile Manifesto favoring the items on the left magically means ignoring the items on the right. This is a strawman. "That is, while there is value in the items on the right, we value the items on the left more." It doesn't say we junk the items on the right.