Visual Studio 11 ALM Advances

Happy new year.

Over the last several months since //BUILD/, I’ve published multiple blog posts outlining advancements made in Visual Studio 11, from languages to the .NET Framework to IDE productivity to platform-specific tooling.  I’m concluding this five-post series with a look at some of the work that’s gone into making Visual Studio 11 a premier system for Application Lifecycle Management (ALM).  Since many of these features were first announced at TechEd North America 2011, many individuals from my division have spoken and blogged quite eloquently about the new capabilities, so I’ll use this opportunity simply to highlight a few of these new features and to point you to the other resources they’ve created to describe them in more depth.

The ALM offering in Visual Studio 11 was designed to enable improved collaboration amongst team members, accelerate the adoption of agile processes, and improve the cycle that links development and operations.  I’ll take a look at a few examples of how Visual Studio 11 achieves this.


A good example how Visual Studio 11 improves collaboration between developers is the new code review support.  Visual Studio 11 includes a significantly overhauled Team Explorer tool window, which includes the new My Work pane that provides a central location for you to see what work you currently have in progress and what other work is assigned to you.  As part of this experience, developers are able to request code reviews from teammates (easily shelving the current state of their work), respond to others’ requests, dialog with teammates about reviews, annotate “diffs” for requested code reviews within the Visual Studio editor, and much more.

Collaboration isn’t just about communications between developers, of course.  There are many other roles in a software team, and Visual Studio supports collaboration with and between all of those roles. For example, Visual Studio 11 includes a new exploratory testing experience.  With formal testing practices, you author your test cases up front and then execute them against your iterative builds. Sometimes, however, you can find additional problems while going “off road” with unscripted testing, problems for which you wouldn’t necessarily have thought to write test cases. In those instances, you still want to be able to capture rich, actionable bug reports – possibly featuring video, audio annotations, screenshots, and the like. And when you do find a bug, you want to be able to automatically turn the repro steps into a test case so that you can formally test it moving forward.  This is at the heart of the exploratory testing experience.

Agile Processes

This exploratory testing example also serves as a glimpse into the aforementioned work we’ve done to better enable agile processes in Visual Studio 11.  Another such area of investment is our work to improve agile project management.  This has been a big focus for Visual Studio 11, and in particular for Team Foundation Server 11.  Some of the experiences that are enabled include:

  • Managing your product backlog

  • Engaging in sprint planning

  • Driving your daily stand-ups

Work in Visual Studio on agile processes goes beyond product management and testing; support has also been added to improve requirements and feedback gathering.  For example, the new PowerPoint Storyboarding tool helps you to quickly prototype interfaces:

And the new feedback client makes it easy to get critical input from your stakeholders on your iterative builds:

What’s Next

As I mentioned at the beginning of this post, I’ve only scratched the surface of what is coming in Visual Studio 11 for ALM, and there’s a whole slew of advancements I’ve not touched on, such as support for IntelliTrace use in production, support for continuous testing, and of course the Windows Azure-based Visual Studio Team Foundation Service. I’ve simply highlighted a few features that are more fully explored in other posts, articles, and videos.  Here are a few I recommend:

Of course, all of this discussion, and in general everything I’ve covered in this series, is based on the Visual Studio 11 Developer Preview.  Since the Developer Preview release at //BUILD/, we’ve been working on further improvements to Visual Studio 11 that we hope to share with you in the near future.


Comments (12)

  1. Eric Demeter says:

    Dev11 looks interesting, but will we finally be able to rename TFS team projects? It's the number 1 TFS suggestion on Uservoice and it's been a pain point for years.


    Connect Suggestion from 2010/2008/2005:…/cant-rename-a-team-project-in-tfs-2010

  2. Soundararajan says:

    I hope some of this should be part of pro edition

  3. Ashith Raj says:

    Can't wait to work with windows 8 beta and vs2011 beta.. Bring it on

  4. Dean says:

    What about advancements in just the basics of source control…there's some pain points in just the basics.

  5. matt says:

    DV11 looks little bit difficult but looks interesting.

  6. Justin says:

    nice explanation with the snap shots man.

  7. Can you please check the design of this blog over right hand side panel. Button of the search bar is wrongly aligned.

    (My intention is not to point out the things but to stop the others to do the same)

  8. toub says:

    Revelly, thanks for letting us know about the search wrapping.  It's now been fixed.

  9. toub says:

    Dean, thanks for your feedback on the basic source control experience.  What are the key pain points you're experiencing?  It's probably easiest for all if you share your requests/feedback on the Visual Studio UserVoice site at…/30925-team-foundation-server, if you haven't already.

  10. toub says:

    Soundararajan, thanks for the request.

  11. gs says:

    Soma – will .net 4.5 rtm support XP?thx  

  12. toub says:

    gs, the operating systems officially supported by .NET 4.5 when it RTMs have not yet been announced.

Skip to main content