Record the effort your team expends on requirements development and management activities. Use this data to assess whether the planned requirements activities are being performed as intended and to better plan the resources needed for future projects. In addition, monitor the effect that your requirements engineering activities have on the project. This will help you judge the return on your investment in requirements engineering.

The scope and quality of the system you produce should be specified as part of that system's requirements. Make Quality a Requirements Issue Often you'll be in situations where trade-offs are involved. Surprisingly, many users would rather use software with some rough edges today than wait a year for the multimedia version. Many IT departments with tight budgets would agree. Great software today is often preferable to perfect software tomorrow. If you give your users something to play with early, their feedback will often lead you to a better eventual solution