103 votes19 comments · Azure DevOps (formerly Visual Studio Team Services) » Work Item Tracking · Flag idea as inappropriate… · Admin →
As explained in this blog post (http://blogs.msdn.com/b/visualstudioalm/archive/2015/10/08/how-we-use-user-voice-to-make-a-better-product.aspx), we had updated the status of this suggestion to “Under Review” to let you know we are tracking it on our backlog. To better indicate which one we are actively working on or which ones are on our 6-month plan, we introduced the states “Started” and “Planned”. The goal is to give an update on in progress suggestions at least every 3 months. This suggestion is still on our backlog, but they are not part of the 6-month plan.
Ewald HofmanAnonymous commented
I remember during sprint planning our scrum master wrote the number of developers on the board to help us divide the remaining hours. What I always did was divided the number of developers minus 1 because that 1 did NOTHING (he later on got fired). I understand it is a team effort, but each of us gets paid individually and is supposed to carry some weight. This metric will help management carry out annual performance reviews, identify bottle necks, help reshuffle, help provide training, bonuses, etc. Very good idea, I think you should start it.
Hello again voters and reporters for this UserVoice item
Visual Studio 2017 RTW, released yesterday, contains fixes to many of the worst issues we are aware of that caused typing delays. To get the benefit, if you haven’t already done so, please download it today from https://www.visualstudio.com/downloads/
We’ve also included enhanced typing telemetry in the new release, so we can continue to focus on improving those issues that remain, and we’ll alert you via the Visual Studio Performance Center (see https://blogs.msdn.microsoft.com/visualstudio/2016/10/10/faster-visual-studio-15-startup/ for details) when an extension is slowing your typing down.
We’re not done: we intend to make further improvements to typing responsiveness in updates to Visual Studio 2017.
Mark Wilson-Thomas and Hemchander Sannidhanam
Program Manager and Engineering Manager
Visual Studio Editor TeamAnonymous supported this idea ·