Which of these scenarios will make you a rock star tester? Which will make your job more interesting? Which provides the most flexible way for your team to handle turbulence?
SCENARIO 1
Programmer: We need to refactor something this iteration. It was an oversight and we didn’t think we would have to.
Tester: Can’t this wait until next iteration? If it ain’t broke, don’t fix it.
BA: The users really can’t wait until next iteration for FeatureA. I would like to add FeatureA to the current iteration.
Tester: Okay, which feature would you like to swap it out for?
Programmer: I won’t finish coding this until the last day of the iteration.
Tester: Then we’ll have to move it to a future iteration, I’m not going to have time to test it.
SCENARIO 2
Programmer: We need to refactor something this iteration. It was an oversight and we didn’t think we would have to.
Tester: Yes, I can test it. I’ll need your help, though.
BA: The users really can’t wait until next iteration for FeatureA. I would like to add FeatureA to the current iteration.
Tester: Yes, I can test it. However, these are the only tests I’ll have time to do.
Programmer: I won’t finish coding this until the last day of the iteration.
Tester: Yes, I can test it…as long as we’re okay releasing it with these risks.
RSS
I agree in general that Scenario 2 and the "can do" attitude while setting expectations for the given situation/constraints is preferred from a tester.
However, what's interesting is if you replace "Tester" with maybe a "Manger" saying almost the same lines I'd have to say "Scenario 1" would probably be preferred in most cases from a good manager to minimize risk. And only if there was pressure to get it in would they then fall back to Scenario 2 setting up expectations for any risks entailed in taking on more work.
I would prefer the first scenario and will ask for more time to complete testing.
But than as usual, the final decision is on client side. Even after my perfect explanation, client won't be agree than I would go for second scenario but providing them RISKs list for my safer side.
Will go with scenario 2, only if it would be fine for users to release it known risk.
I will prefer scenario 1 since even Scenario 2 sounds much better but actually can not give a complete picture on project progress
I wouldn't make any commitments until talking with the PM, and then with my team, about FeatureA and its LOE.