Every year, the complexity of projects increases. The average requirements document is over 100 pages and changes 20 times during the development process. It’s brutal. That means as a Business Analyst or Project Manager, you likely spend hours circulating, editing and tracking changes to a hefty requirements document with the hope that your team actually stays engaged and reads it. Wishful thinking, right?
The old way takes crazy heroics and is a nightmare to manage using Word, Excel and email. Your time is more valuable than that.
The problem isn’t the requirements document itself. The problem is in using the document as the place to manage requirements. If you’re hoping to set expectations, communicate project details, and track changes throughout the process with documents – good luck. You’ll need it.