A major source of conflict is between usesr who are unable to describe their wants and programmers who unable to understand users needs. While static requirements are not very good, it can create some stability in a project.
One position I had, the requirements were literally changing everyday. It was impossible to make any progress because we were always going back and fixing the code we just worked on. Requirements were finally required to be written down as it was the only way developers were able to make any progress. The users still kept changing their requirements, but at least the developers had a fall back point on why things were done a certain way.
The moral of the story, "There are some people who cannot figure out what will make themselves happy".
In reply to Re^3: The dangers of perfection, and why you should stick with good enough
by Herkum
in thread The dangers of perfection, and why you should stick with good enough
by redhotpenguin
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |