How to reduce user story reopen count in Scrum development?

A user story (US) is reopened for reworking due to shortcomings from four major fronts- business analyst (BA), developer, quality analyst (QA) and environmental issues. BA is responsible for capturing requirements and documenting the requirements in the form of user stories; developer is responsible for the implementation of the user story; and the QA is responsible for testing of US. Now if any of three does not perform his job accurately then the probability of reopening of US increases. So we can reduce the probability of reopening of US by improving on shortcoming from three ends BA, developer and QA. As for as environmental issues, are concerned, they can be controlled by QA, developer and BA. The aim of the paper is to identify different areas from BA, Developer and QA´s end to reduce the probability of reopening of a US and thereby reducing the user story reopen count in the Scrum development.