{"id":783,"date":"2023-09-09T10:51:03","date_gmt":"2023-09-09T10:51:03","guid":{"rendered":"https:\/\/www.softwaretestingstuff.com\/?p=783"},"modified":"2023-09-10T10:30:31","modified_gmt":"2023-09-10T10:30:31","slug":"when-requirements-are-changing-continuously","status":"publish","type":"post","link":"https:\/\/www.softwaretestingstuff.com\/2007\/11\/when-requirements-are-changing.html","title":{"rendered":"When requirements are changing continuously"},"content":{"rendered":"\n

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.<\/a>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.<\/p>\n\n\n\n

Below are some more points that might help:<\/strong><\/p>\n\n\n\n