What can be done if requirements are changing continuously?
change, so that alternate test plans and strategies can be worked out in advance.
It is helpful if the application's initial design allows for some adaptability, so that
later changes do not require redoing the application from scratch. Additionally, try
to...
changes easier for the developers.
Ø Use rapid prototyping whenever possible; this will help customers feel
sure of their requirements and minimize changes.
Ø In the project's initial schedule, allow for some extra time to
commensurate with probable changes.
the original requirements for the 'Phase 1' version.
project; move more difficult, new requirements into future versions of the application.
inherent risks and costs of significant requirements changes. Then let
management or the customers decide if the changes are warranted; after all, that's their job.
Ø Design some flexibility into test cases; this is not easily done; the best
bet is to minimize the detail in the test cases, or set up only higher-level
generic-type test plans;
Ø Focus less on detailed test plans and test cases and more on ad-hoc
testing with an understanding of the added risk this entails