In many application development projects it is a recurring problem: The application is documented both functionally and technically inadequate. As a result, the software is difficult to transfer and maintain. Modern development tools try to prevent this problem by keeping software and documentation together in one environment.

Read more: Reduce Transfer Problems with Self-documented Applications

How to make testing in projects with a non-waterfall approach as smooth as possible? In these projects, I first found it difficult to time my testing activities – start too early and retest a lot, or start too late and run out of time.

The difficulty by testing in scrum projects is that testing takes place while development is still in progress. So, how do we ensure that we do not have to test everything (again) when development (thinks to be) finished? Below, I will distinguish between 5 testing aspects and their timing. For each of these aspects there are certain criteria, which help to decide when to start testing.

Read more: Testing in Scrum: Don’t Forget The Timing

Page 4 of 4