Question: Sometimes a customer requests a requirement you know is impossible to implement. Should you agree to put the requirement in the definition and specification documents
Sometimes a customer requests a requirement you know is impossible to implement. Should you agree to put the requirement in the definition and specification documents anyways, thinking you may come up with a novel way to meet it or there may be a possibility the customer will drop the requirement? Discuss the ethical implications of promising what you know you cannot deliver.
Step by Step Solution
There are 3 Steps involved in it
Get step-by-step solutions from verified subject matter experts
