Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Visual Studio 2013 Cookbook

You're reading from   Visual Studio 2013 Cookbook Understanding the latest features of Visual Studio can speed up and streamline your projects. And there's no better learning tool than this collection of focused recipes that gives you the fast, hands-on experience you need.

Arrow left icon
Product type Paperback
Published in Mar 2014
Publisher Packt
ISBN-13 9781782171966
Length 332 pages
Edition Edition
Languages
Arrow right icon
Toc

Table of Contents (17) Chapters Close

Visual Studio 2013 Cookbook
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
1. Discovering Visual Studio 2013 2. Getting Started with Windows Store Applications FREE CHAPTER 3. Web Development – ASP.NET, HTML5, CSS, and JavaScript 4. .NET Framework 4.5.1 Development 5. Debugging Your .NET Application 6. Asynchrony in .NET 7. Unwrapping C++ Development 8. Working with Team Foundation Server 2013 9. Languages Visual Studio Medley Index

Getting feedback from your users


When working on a product, one of the most valuable things you can do is get feedback from your users as to whether the software you have built meets their requirements or not, and what their opinions of it are. You will notice that in TFS terminology, the word "stakeholder" is used over "user"—representing the diverse sources of feedback that exist. Besides traditional users, several groups want their voice heard—including design, QA, and the product owner's funding development.

Even if you have a process that defines clear acceptance criteria for requirements, and you have a clear definition of what it means to be "done" with a piece of work, you still want feedback from these stakeholders to determine whether there are any other points that may have been missed when the requirement was first discussed, or if new ideas have occurred now that they have seen the software running.

A normal feedback process involves telling your users that the software is available...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime