We don't want to ignore the changes that customers want, just the opposite: we want to make more customer-requested changes, and faster. Helping QA to be as fast and easy as possible is both a vital part of achieving that, and vital to ensure that changes don't introduce new bugs.
Adopting a requested change in the most minimal and limited way will obviously and necessarily incur additional change requests (changes to the change). I don't think it's out of bounds to see your position as equavlent to, "there isn't enough time to do it right, but there's plenty of time to do it over."
Check here if you want more options
in Tools and Technology
A group blog by Secondlife in General
Posted
We don't want to ignore the changes that customers want, just the opposite: we want to make more customer-requested changes, and faster. Helping QA to be as fast and easy as possible is both a vital part of achieving that, and vital to ensure that changes don't introduce new bugs.
Adopting a requested change in the most minimal and limited way will obviously and necessarily incur additional change requests (changes to the change). I don't think it's out of bounds to see your position as equavlent to, "there isn't enough time to do it right, but there's plenty of time to do it over."