Many project teams complain about the large number of requirements changes. The solution involves the following simple steps:
1. Manage the requested changes using the documented Requirements Management and Scope Management processes which should include a risk analysis, cost analysis, and discussion with the sponsor about project impacts to decide if they should be included, deferred or dis-allowed.
2. Assess the reasons for the requirements changes. In many cases, they are not changes but simply the evolution of additional detail because of progressive elaboration. Your project plan should allow for this. If there are numerous requirements changes, you need to examine your project processes to determine why they weren’t identified earlier and improve your processes or the skills of your project team to do a better job of identifying requirements earlier.