As we come across many projects, below given are common problems faced during requirement analysis:
Customers Do Not Know What They Actually Want
This is true many a times because customer is not really aware of the system development being undertaken, in terms of web design, goals and objectives of the project. When it comes to complex, large scale software projects, customers are not always affected by requirements, it focuses on back-end processes and system interfaces.
What should be done is we can communicate to one person from each group, such as stakeholders who are going to get affected by requirements. These stakeholders can attend requirement analysis meeting as a representative of the group.
Requirements May Change During Development
Change is a basic nature of requirements, hence, as situation changes, they are bound to change. If there is not proper Change Management process in place, project is going to get affected. To avoid it, it’s better to make stakeholders aware of the same and follow change management process with approval hierarchy in place.
Clear timeline has to be defined when the project is being initiated. It’s important to have clarity about time duration required to complete it, keeping stakeholders informed. This will avoid hurting company’s reputation.
Communication Gap Between Teams And Stakeholders
There has to be proper communication channels established among the teams. This helps to keep everyone on same page, and chances of leaving any requirements unattended are lessened. If any requirement is left, it will cost more to fi it in later stage of the project.