What you'll learn:
- Figure out what you want to change.
- Place to manage requirements.
- Recording the method and implementation of change
- Logging requests for changes against products and documentation
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.