Graham Pembery
October 2012




Application Lifecycle Management Planning
Effective Team Work
Build Process Improvements
Testing Feedback

Manage the backlog, sprints and tasks by using agile tools
◦ Define multiple teams, each of which can manage their backlog of work and plan
sprints. Prioritize work, outline dependencies and relationships. Check capacity, in
real time. Agile Planning and Iterations.

Engage stakeholders to provide feedback on pre-release software
◦ Stakeholders can record action scripts, annotations, screenshots and video or audio
recordings. Engage Stakeholders through Continuous Feedback.

Illustrate requirements with storyboards and link to work items
◦ Build a storyboard from a collection of pre-defined shapes, capture user interfaces
and link to a work item. Storyboard Backlog Items.

Manage enterprise projects using Microsoft Project and Project Server
◦ View status and resource availability across software teams. Enable Data Flow
Between Team Foundation Server and Microsoft Project Server.

Completely rewritten
◦ Rich UI actions, drag and drop
◦ Backlog and Task Board

Real-time charts
◦ Velocity and Sprint burndown
◦ Set the Start and End dates

Forecast Tool
◦ Use velocity for release planning
Dynamic web interface

Manage backlog and plan sprints using Team Web Access and the backlog
and board pages.

Track tasks and boost productivity using an enhanced interface

Work more efficiently in a version-controlled codebase

Initiate and Track Code Review Requests and Responses

Perform unit testing by using as part of your workflow

Work offline
◦ Organize upcoming, on-going and suspended work while increasing
transparency and reducing the impact of interruptions. Day in the Life of
an ALM Developer: Write New Code for a User Story.
◦ Organize your work, reduce the impact of interruptions and manage
shelvesets and changesets. Develop Your App in a Version-Controlled
Codebase.
◦ Day in the Life of an ALM Developer: Suspend Work, Fix a Bug, and
Conduct a Code Review.
◦ Running Unit Tests with Test Explorer.
◦ Work in local workspaces either inside or outside of Visual Studio. Decide
Between Using a Local or a Server Workspace.

Run, monitor and manage builds using an enhanced
interface
◦ Run, Monitor, and Manage Builds

Define gated check-in build processes that support
multiple check-ins
◦ Define a Gated Check-In Build Process to Validate Changes.

Run native and third-party framework unit tests in
your build process
◦ Run Tests in Your Build Process.

Debug your build process more easily
◦ View diagnostic logs from within the build results window.

Find duplicate code
◦ Finding Duplicate Code by using Code Clone Detection.

Conduct exploratory testing

Include multiple lines and rich text in your manual test steps

Get the status of your test plans within Microsoft Test Manager

Clone test plans for new iterations

Deploy Lab Management with only 1 agent
◦ From the Exploratory Testing window, you can run tests without being
restricted to a test script or set of predetermined steps. Performing
Exploratory Testing Using Microsoft Test Manager.
◦ Test steps can include multiple lines to consolidate related actions within
a single test step in your test cases. Microsoft Test Manager now includes
a toolbar that you can use to format the text of your test steps. You can
use various formatting options, such as bold, underline, or colour
highlighting to emphasize key points. How to: Create a Manual Test Case.
◦ This report is available to you from the Plan tab in the centre group menu
bar of Microsoft Test Manager. From there, you can view Results, which
include a report on the status of your test plan. How to: Create a Manual
Test Case.
◦ Work more easily on different releases in parallel. Copying and Cloning
Test Suites into Other Plans.

Standard In-Place Upgrade
 TFS Application Tier Will Use the Same Hardware It’s Using Right Now

Outline of Upgrade
◦ Backup TFS 2010 from TFS Admin Console
 Available once TFS 2010 Power Tools December 2011 installed
◦ Uninstall TFS 2010
◦ Install TFS 2012
◦ Run TFS Upgrade Wizard
 Excellent verification wizards

Fall-back
◦
◦
◦
◦

Uninstall TFS 2012
Install TFS 2010
Restore TFS 2010 using built in tool
Run Config Wizard
Early Adopter Experience – last 6 months
◦ Good upgrade, no significant problems


Build Server is a Separate Instance
Therefore Compilation & Linking unchanged
◦ Delivered code is the same
◦ Only Build Agents updated

Post TFS 2012 Upgrade
◦ Access to existing data from team projects that you
created in previous releases unchanged.

Project Upgrade Procedure
◦ Use the Configure Features wizard to update
existing team projects created in earlier versions of
TFS to use the features made available with the TFS
Server upgrade.
◦ Test on Shadow project first – TFS Project Test.
◦ Once project updated, users can access the new
features for managing the application lifecycle.


Presentation of these slides – ½ hour + Q&A
Followed by Brian Keller’s DemoMate walkthroughs
◦ Product Management
 Agile Project Management in Team Foundation Server 2012
(5:28)
 Building the Right Software - Generating Storyboards and
Collecting Stakeholder Feedback with Visual Studio 2012 (8:27)
◦ Testing
 Diagnosing Issues in Production with IntelliTrace and Visual
Studio 2012 (2:28)
 Exploratory Testing and Other Enhancements in Microsoft Test
Manager 2012 (4:12)
◦ Programming
 Making Developers More Productive with Team Foundation
Server 2012 (11:42)
 Unit Testing with Visual Studio 2012 - MSTest, NUnit, xUnit.net,
and Code Clone (3:30)




Greatly improves Product Manager experience
Adds integrated Coding Review workflow
Integrates Response and Feedback workflow
into development
Basis for improving reporting
Productivity and Collaboration

Links
◦ What's New in the Visual Studio Team Foundation Server
11 Developer Preview
 Kathryn E
◦ What’s New in TFS 2012?- Project Management Tool
 Mohamed Radwan
◦ Update an Upgraded Team Project to Access New
Features
◦ What's New in Planning and Tracking
◦ Upgrading TFS 2010 to TFS 2012 with VSS Migration and
Process Template consolidation
 Martin Hinshelwood
◦ Upgrading from TFS 2010 to 2012





Application Lifecycle Management with Visual Studio and
Team Foundation Server
Technical Articles for Visual Studio Application Lifecycle
Management
Testing for Continuous Delivery with Visual Studio 2012
What's New in Visual Studio 2012
Visual Studio ALM Ranger Solutions

Planning the migration
◦ Refer to ALM Rangers Guidance
◦ Great link http://blog.hinshelwood.com/upgrading-tfs2010-to-tfs-2012-with-vss-migration-and-processtemplate-consolidation/
◦ TFS Downtime – 2-6 hours
 Need trial migration to snap shot existing servers
◦ Upgrading the Projects from MSF 5.0 to MSF 6.0
 http://channel9.msdn.com/Blogs/VisualStudio/Upgradingto-Team-Foundation-Server-11-Process-Templates
 http://blog.hinshelwood.com/process-template-upgrade7-overwrite-retaining-history-with-limited-migration/

Visualize code more quickly and easily

Read and edit dependency graphs more easily

Open and view linked model elements in work items

Generate C# code from UML class diagrams

Create UML class diagrams from existing code

Import XMI 2.1 files
◦ Create dependency graphs from Solution Explorer so that you can understand the
organization and relationships in code. Visualize Code Dependencies on
Dependency Graphs.
◦ Browse graphs and rearrange their items to make them easier to read and to
improve rendering performance. Edit and Customize Dependency Graphs and
Browse and Rearrange Dependency Graphs.
◦ Link Model Elements and Work Items.
◦ Start implementing your design more quickly, and customize the templates that are
used to generate code. How to: Generate Code from UML Class Diagrams.
◦ Create UML class diagrams from code so that you can communicate with others
about the design. How to: Create UML Class Diagrams from Code.
◦ Import UML class, use case, and sequence diagram model elements exported as XMI
2.1 files from other tools. For more information, see How to: Import UML Model
Elements from XMI Files.

Find duplicate code so that you can refactor
◦ Finding Duplicate Code by using Code Clone Detection.

Compare code versions by using an enhanced diff tool
◦ Compare Files.