G'day
Thinking about this redefinition issue for possible future changes made me think.
What reasons can you oppose to those who insist on blowing projects because "they may want to use it somewhere else at some stage in the future"?
In the same way, what do you do when people take requirements and then come back with a bloated design with lots of extra “bells and whistles” that you didn't ask for?
I can understand how to expand a design when you know that it makes sense for requirements or possible applications that exist either right now or in the near future. And I am not a supporter of simply recklessly accepting the list of requirements and implementing it explicitly, without providing any feedback on what, in your opinion, may be missing.
I'm talking about what to do when people insist on adding or having extraneous functions so that "can we use it somewhere else at some point in the future?"
source
share