Requirements change management is a tedious task. Requirements change keeps pouring in if you do not freeze the requirements for a milestone. The reason that requirements keep on changing is that the application owner or the client would be missed out a requirement or they could have identified a bug in the existing system of late.

______________________________________________________________________________

It is important to involve the stakeholder while gathering the requirements, because they themselves might not be sure of what they need. Short iterations on the requirement gathering would help you finally. The other reason for getting a new requirement would be that a competitor would have come out with a product that has more features than you are planning now. New legislation would demand new features in your application. Hence it is also not advisable to freeze the requirements at an early stage. This would lead to a product that does not meet the customer’s requirement when you release it.

The requirements that you get are prioritized. You should also involve the stakeholders in prioritizing the requirements since they know which is required immediately. They have the responsibility to provide you timely information. However make sure that only one person is prioritizing the requirements. This person might vary from project to project.

Involve the developers in estimating the effort required for completing the tasks since they know what time it takes to complete the task. However in many cases it is not possible to involve them since they are not good in estimation.

You have to follow this approach in dealing with the requirements, since the stakeholders would be happy and know that they are going to get. Feedback on a regular basis is also given to the stakeholders and they have control over the scope, schedule, and budget. Of course there are challenges that you have to face like; cost factor is not clear in this approach since the requirements change.