The phrase "drive quality upstream" has been abused so badly by ALM software vendors that it has to be relegated to the platitude junk pile along with such all time favorites as "work smarter not harder," "think outside the box," and "synergistic leveraging of code reuse."  Before we drive quality anywhere, we need to give quality a seat at the table. VSTS Rosario release will do this by automatically gathering critical information about the project and code and making that data available when, where and to whom it is needed. During this discussion we will examine how Rosario impacts quality across the application lifecycle by:

• Allowing testers to provide developers with details about what the code did instead of just providing the details about what the tester did.
• Allowing development leads and architects to visualize and understand their current code (not the code they wish they had, but the code they really have) so that they can minimize the impact of changes; and
• Allowing developers to understand the impact of their changes in terms of affected tests, concurrency and bounds checking.

The Rosario release of VSTS will bring all project stakeholders together to allow richer information to be shared across every role to make software quality accessible and achievable.