Once your customers see you are serious about this, you will have fewer cases of it.
Fewer cases because they might not be continuing your employment. It probably depends on the relationship.
You require the customer to sign off on what they want before you begin
Even when there is sign-off, what it means is entirely a new thing. I'm on a project right now where there is sign off on multiple levels, yet almost noone knows what is happening. The customer thinks one thing, the BAs something else, the programmers have to go through multiple revisions before they get it right (according to the team lead), and the team lead overrides the customer's stated wishes by convincing them that what they want is impractical.
What you want is right, but are you sure its practical?
In reply to Re^2: Good programming practices and changes in requirements: how to maintain good code
by chacham
in thread Good programming practices and changes in requirements: how to maintain good code
by DanBev
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |