When requirements are changing continuously


Lot of times I've been asked from various stack holders about what to do when requirements are changing continuously. Here, I'm going to describe some basic things that we need to take care when requirements are changing continuously.
Work with end users and management early on to understand how requirements might 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 re-doing the whole work from scratch.

Below are some more points that might help:
  • Devote appropriate effort to risk analysis of changes, in order to minimize regression-testing needs.
  • In the project's initial stages, allow for some extra time to commensurate with probable changes.
  • Balance the effort put into setting up automated testing with the expected effort required to redo them to deal with changes.
  • 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.
  • Try to design some flexibility into automated test scripts.
  • Focus initial automated testing on application aspects that are most likely to remain unchanged.
  • Ensure management and client understand scheduling impacts, inherent risks and costs of significant requirements changes. Then let management or the customers decide if the changes are acceptable.
Also See:

No comments:

Post a Comment