ABSTRACT
This chapter argues that the costs associated with a release may be postponed to next release by shifting requirements. By postponing functionality and costs to the next release new benefits may be discovered, like the ability to group sets of similar changes. The chapter discusses the general phases of a test process and balancing business value and risks as guidelines for test depth. It explores the translating business value and the technical solutions to test types. The chapter also looks at mapping discovered issues to impact on the system and the translation of a mixture of the activities using examples from own experience. In the preparation phase testers focus on collecting information about the test objects. This is essential, preparatory work performed before test execution. By considering the costs per activity per phase it may become evident that under certain conditions it may be worth postponing parts of the solution to the following release.
