At my job, management wants the QA team to be the "keepers" of all the requirements for the system. This is because when we write the tests and uncover changes to requirements or code, the Feature Design and Implementation docs are never updated to reflect the "actual" functionality, because in an Agile world, those teams are on to the next sprint. So it's QA's job to keep these tests as living breathing documents and organize and make available to all worker teams this requirement repository. We are also updating the requirements (per our tests) as a feature is enhanced is subsequent sprint. Thus, it is now our jobs to manage these requirements. I believe the designers and product teams should be managing this repository. What do you think?