This blog post delineates some common mistakes that are generally made at the time of requirement gathering.

1. Common Mistakes To Avoid In
Requirements Management

2. 1) Induction – Lack of Correct Communication
In the commencement of the project management initial we want to collect the need. At this point, we have a tendency to face this language
barriers, wrong assumptions, unclearly outlined vocabulary, and excessive use of skilled language that may result in misunderstandings
between stakeholders and a business analyst.
The best thanks to avoid such style of state of affairs is to speak typically and establish two-way communication.Producethe Document for
each demand gathered and send them for review and feedback to multiple subject material specialists, produce and share a wordbook of
terms, and continuously verify assumptions.
https://erpsolutions.oodles.io/developer-blogs/Common-Mistakes-To-Avoid-In-
Requirements-Management/

3. 2) Unsupported Processes
In several organizations there's typically no or poor documentation offered regarding existing processes.Duringthis state of affairs, needs
gathering becomes a ballroom dancing method. Firstly, back-engineering of existing method, and so distinctive areas for improvement
andoptimization.
To ensure needs area unit full and proper, it's vital to spot key stakeholders and subject material specialists and have interaction with them
directly. This helps eliminate any assumptions and provides a full image. Drawing business method maps and visualizing workflows area unit
effective techniques that may be employed in this case.
In the on top of example, our mechanical team would flag that demand and if it were changed or modified, they'd get notified.All-timelow line
is to form certain that you just have a technique in situ to trace the shared or complementary functions as communication lapses will happen.