Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
I completely agree that a single backlog for 'functional' and 'non-functional' requirements is key here. Also important is to have the budget-holder (or product owner) responsible for the operational effectiveness of the product. Several people have found this blog post I wrote useful: Let's Talk About Operational Features, not Non-Functional Requirements: blog.softwareoperability.com/2013/04/08/…
