As the Visual Studio family of products (Visual Studio, TFS, Test Professional) nears its 2012 release, I thought I’d bring some short hits – tidbits, if you will – to my blog. Some of these are pretty obvious (well-documented, or much-discussed), but some may be less obvious than you’d think. Either way, it’s always good to make sure the word is getting out there. Hope you enjoy!
One of the “new” new features of TFS 2012 is the addition of the Microsoft Feedback Client for collecting feedback from stakeholders, end users, etc. This tool integrates with TFS to provide a mechanism to engage those stakeholders and more seamlessly include their insights in the lifecycle.
Several of my customers however, perhaps with brains overloaded with the possibilities of this capability, have asked me, “So when exactly do I use this? When do I request feedback?”
Well, the answer, as it often times is, is “it depends.”
First, if you aren’t aware of the two ways to use the Microsoft Feedback Client, check out (shameless plug) my previous post covering this.
The more I play around with this tool and talk about it with customers, the more scenarios I find in which this new 2012 capability adds value.
Now back to that “it depends” answer.. The key thing to remember for using the feedback capability is that there is no hard and fast rule for when you should use it. But here are three main scenarios:
From MSDN, “Planning and Tracking Projects”:
What other scenarios can you think of where you could leverage the new feedback capabilities in VS 2012?
Nice post, thanks