Learn to use Visual Studio, Visual Studio Online, Application Insights and Team Foundation Server to decrease rework, increase transparency into your application and increase the rate at which you can ship high quality software throughout the application lifecycle
How often have you built the software that your users asked for, but not necessarily what they wanted? One of the determining factors between success and failure of software projects is getting the right feedback, at the right time, from the right individuals. In Microsoft Visual Studio 11, we have enabled feedback deeply throughout the product (refer to Brian Harry's blog to get the full context), such as:
In this post, we will focus on the "Feedback on working software" phase.
As the product team keeps churning out incremental "consumable modules/bits" at end of each sprint, it is critical not just to test these within the product team (Dev/QA etc), but also to involve the business stakeholders to evaluate it from business perspective. The frequency of such stakeholder reviews can vary within teams, but it is often beneficial to get feedback from stakeholders early and often, so that you can fine tune/course correct early on if there are any deviations from the business side of the house. Visual Studio 11 helps you optimize this workflow by enabling both Solicited and Unsolicited feedback workflows using Microsoft Feedback Manager.
Solicited Feedback Workflow:
Unsolicited Feedback Workflow:
The following MSDN topics go through the solicited workflow in lot more detail:
Ravi Shanker, Prinicipal Program Manager, Visual Studio ALM