Last month, during TechEd North America, we were introduced to some of the new features that were coming in the next version of Visual Studio, specifically in the area of Application Lifecycle Management (ALM). Susan was at TechEd and blogged about some of those details. If you weren’t able to get out to TechEd and haven’t yet watched sessions on-demand that talk about Visual Studio vNext, you absolutely must.

TechEd2011Keynote_220_ch9[1]

Tech·Ed North America 2011 Keynote Address
Jason Zander, Robert Wahbe

If you fast forward to 1:01:15 in the video of the Keynote address, you can watch Jason Zander, Corporate VP, Visual Studio talk about what to expect from Visual Studio vNext.

   
FDN03[1]

The Future of Microsoft Visual Studio Application Lifecycle Management
Cameron Skinner

This demo-heavy session offers early insights into the future of Application Lifecycle Management and agile development that are incorporated in the next release of Visual Studio.

And if those two sessions were not enough to get you excited, our friends at TechNet Edge captured some great conversations on the ground at TechEd, specifically, this conversation between Richard Campbell and Jason Zander about the upcoming ALM features. 

clip_image002

Jason Zander on ALM

Jason Zander talks to Richard Campbell about Visual Studio v.Next, specifically the upcoming ALM features. Jason talks about the next generation of ALM and how it brings stakeholders, developers and IT Pros closer together with new tooling.

Want to dive deeper and find out more? Download the Visual Studio vNext whitepaper. It’ll provide you with additional contexts and outlines of the problems that Visual Studio vNext is working to solve, how they relate to problems that are faced as an industry, and how Visual Studio vNext will improve the effectiveness of ALM.

So what’s next? Stay tuned! As more information because available, we’ll make sure that you hear about it here. In the meantime, join me in this LinkedIn conversation around the features announced in these sessions, share your thoughts, and perhaps recommend a feature or two that you would like to see in Visual Studio vNext.