Critical Non-Functional Requirements
In addition, the enterprise is too large to assume that all the global development teams will naturally understand the various system qualities; that is, those constraints and "ilities," such as reliability, accuracy, performance, quality, and so on that are imposed on the system as a whole. Therefore, these non-functional requirements must also be known and communicated via a central repository where all teams can readily access them.
These requirements are an adjunct to the vision and feature backlog, and are every bit as critical as the functional requirements. Therefore, product managers have a major role in defining them. Your enterprise development practices may now be more lightweight and Agile, but the system still has to work when you ship it!