How can you tell if your organization overemphasizes functional requirements?
If your organization bothers to document requirements (whether in an MRD or other document), examine them. If you find any of the following statements apply, then your organization probably is overemphasizing functional requirements:
- Is there a laundry list of product features?
- Are there more use cases than constraints on the use cases?
- Is there a multi-page section labeled "functional requirements"?
UPDATE: See the follow-up entry and this clarification. The problem is that so-called functional requirements are sometimes functional design specifications masquerading as requirements.