First of all, I have found in my experience that the problem you describe is very common – in fact most teams have this problem when they start using agile methods and it can take quite a while to overcome. Hopefully that should give you some reassurance.

However, it is important to identify and understand the underlying causes of this and take actions to solve them. The result if you can will mean completing testing earlier and ultimately being able to produce working software faster, so it’s usually well worthwhile. Even if you’re not planning to release the software live, having truly measurable progress and quality in the form of tested software, rather than piles of untested software, is of course a better measure of where you’re really at in your project.

So my advice to you as a team is to look for the underlying reasons that it wasn’t possible to complete some working (tested) software inside your iteration and start to take action actions to remedy those, resisting the temptation to just make your iterations longer. Even if it takes some time to remedy all the causes of this symptom, the point is that your short iterations are highlighting problems and you should build actions into subsequent iterations to incrementally start tackling them.

Anyway, I hope that helps, and good luck!

Kelly.

I met a problem that some of testing tasks have been postponed into next iteration due to some certain reasons, such as the env is not stable, the development is impeded.

Do you have some suggestion on how we tester do with this situation and avoid it happenning so often?

Thanks, Lily