Microsoft to Focus on Collaboration, ALM in Visual Studio vNext
title=The Need for Better Collaboration} Sander's post delves into the issue of ALM and the need for collaboration. He said: "Our vision for ALM can be broken down into three main themes:
- Building on the momentum of Visual Studio 2010. If you haven't tried out Visual Studio 2010, you can take it out for a test drive.
- Collaboration - focus on the flow of value between team members no matter what role.
- Actionable Feedback - when feedback is required between team members, it should be in a form which is directly applicable to solving the problem at hand. For example when a tester communicates a defect to development it should include videos, screen shots, configuration information, and even an IntelliTrace log making it easier to find and fix the root problem.
- Diverse Work Styles - provide the best possible tool for each team member whether that is the Visual Studio IDE, the web browser, SharePoint, Office, or dedicated tooling.
- Transparent Agile Processes - Enable all of the above to work on a "single source of truth" from engineering tasks through project status. TFS provides this core that brings together all team members and their tools."
- Agile Planning Tools - create transparency across the planning process and full team participation through solutions like the new backlog and task board.
- Lightweight Requirements - a natural way to capture and receive feedback on requirements early in the process.
- Stakeholder Feedback - working code which matches the expectations of stakeholders.
- Continuous Testing - unit test coverage ensures quality in the final product.
- Agile Quality Assurance - increased code quality with code review support, enhanced unit testing frameworks and new exploratory testing support.
- Enhanced User Experience - more time -in the zone', through improved experiences for day-to-day tasks.
- Aligning Development with Operations - increased connections and insight between the operations and development teams lowering the time it takes to fix a bug in production.