I am a lead developer working for the IT department of an organization. Recently I have been assigned a new project. Initially, the business analyst responsible for the project sent me developer requirements. After I reviewed those documents, I noticed that there were lot of gaps and that clarity was missing, which I brought back to the business analyst. Similarly, other team members also come up with clarification questions related their part of development work. It took a month and a half to clear up this confusion on the requirements. However the problem isn't all these requirement clarifications, but instead it's in the fact that not all of these changes are documented in any central location and aren't updated in the original project specializations. As a result, the gap between the initially specified requirements in the requirement document and the finalized requirements is so high.
Thus, not everyone involved in the project is on the same page, and every time I need to explain the history of how the initial requirements changed to current one. I feel it is not productive and is tedious.
Here My primary problem is all the latest changes are not updated in requirement docs. Due to this I am facing issues like other colleagues asking too many questions about requirements. Hence the root cause is not updating all the updates about requirements in the original document, I am asking question about that only. Hence my question would become
How to deal with too many requirement changes and not updated/documented in single place?