This is part three of a ten-part series on Application Life Cycle Management (ALM) using Visual Studio 2012 and Visual Studio Team Foundation Server 2012. If you missed my previous posts, you may want to read those before continuing (series overview; part one: Teams without Barriers; and part two: TFS Online).
In my post today I will give an overall picture about what tools you can use in order to better adapt proven practices to manage your application’s lifecycle and then dig deeper in my upcoming posts.
By using various tools that are available in Visual Studio 2012, and by combining those with Visual Studio Team Foundation Server 2012, you can apply proven practices to manage your application’s lifecycle, from the time you start understanding your very own customer needs through code design and implementation to deployment. The entire suite of tools available in Visual Studio 2012 will ensure you have success throughout the entire application lifecycle. They will help you trace requirements to checked-in code, builds, and test results. All of these practices can help your team create software that is valued by your customers, faster, and more reliable. You can use these tools to achieve the following results:
Now let’s look into how you can adopt these tools to improve and manage your application’s lifecycle.
You and your team can incrementally adopt Visual Studio as the solution for Application Lifecycle Management (ALM) and can see how to get started with your team setup quickly and start using Visual Studio ALM activities at different points in the process. Your team can adopt Visual Studio features for ALM in any sequence, except where one feature depends on another.
In my next post we will dive deeper to see how different tools provided by Visual Studio 2012 and Team Foundation Server 2012 can help you better manage your application lifecycle. So get ready, take a deep breath, relax, and enjoy the ride.
Dramatically increase agility and velocity with Microsoft Solutions