| || |
Can anyone suggest best practice for defining subsequent releases of projects.
In the first release, we have had a definite set of requirements and we have used optimal trace to define it.
In the subsequent maintenance release, we have a bunch of CRs and Defect fixes.
How do we put this in as requirements for the next release. We will then create new test cases for each one of them.
How to go about defining them? We want to run the subsequent releases as projects. We have all these defects included in the release scope.
Does anyone have suggestions?