THE PROBLEM WITH REQUIREMENT SPECIFICATION DOCUMENTS
The creation of the PRD (Process Requirement Document) is not wrong in itself, but the bigger issue is when it is created and how extensive it is. Traditionally, the Requirement specification documents were created as part of waterfall projects. Assigned project managers or technical leads would write a long document pinning all details or requirements for the product that will be worked upon in the short to mid-term future. This is followed by putting detailed design in place, then coding, integration, testing, deployment… We know where that leads to, right?