“It’s exactly what I asked for, but it’s not what I want. Change it.”
Changing requirements was a problem, it is still a problem and it will continue to be a problem. This is actually a real-world issue that most major companies in the world have to deal with. Stakeholders change their minds. That’s how it works. They always do, always will. And it’s not about to change. This can occur because of one or more of the following reasons:
1. The Scope of the Project was not negotiated properly.
2. The requirements were elicited from the wrong stakeholder (source).
3. The requirements were ambiguous
4. The requirements were incomplete.
5. The requirements were not documented.
6. The requirements were not verified and validated.
7. The Business Analyst (BA) was incompetent. (i.e. BA Malpractice)
8. A stakeholder deliberately provides the Analyst with the wrong information. (i.e. Political sabotage)
If requirements are frequently changing, then the project cost, schedule and/or scope will be impacted.
‘An ounce of prevention is worth a pound of cure’
To prevent changing requirements it is important the we ensure that the project scope is properly defined. The right stakeholders are involved. The requirements are unambiguous and complete. The requirements are verified and validated. The BA must understand his/her role and apply professionalism and existing science to the collection and refinement of requirements. Remember, it is better to try to prevent problems in the first place, rather than trying to fix them once they arise.