This changes nothing, probably
It is unavoidable, but sometimes, right before a product deployment (or just after), a patchable issue is found. Not something that merits a full version, something simple, isolated. Could be a completetly new feature, which should not impact the current user experience in any way. Right?
This is also something that QA professionals should learn to live with. You score points by not backing down, as long as it helps the company, not by insisting on a week long regression after changing a typo in the GUI.
Recent Comments