Visual Studio 2010 ALM Tools Overview

Ayman El-HattabMicrosoft SharePoint MVPTwitter: @AymanElHattab

Suliman Al-BattatMicrosoft Visual Studio ALM MVPTwitter: @SulimanBattat

Agenda

Introducing Application Lifecycle Management

Visual Studio 2010: The Big Picture

Team Foundation Server 2010 Deep Dive

Conclusions

What is ALM ?

What is ALM?

ALM IS a business Process.

ALM is more than the software development lifecycle (SDLC)It includes the entire time during which an organization is spending money on this asset

ALM can be viewed as having three aspects:Governance: Making decisions about the applicationDevelopment: Creating and updating the applicationOperations: Running and managing the application

Deployment End of Life

Operations

Development

Idea

Governance

Illustrating ALM

Business case development

Operations

Development

Governance

Aspects of ALM: Governance

Project approved

Application removed from service

Project Portfolio Management (PPM)

Application Portfolio Management (APM)

SDLC, v2

Maintenance

Aspects of ALM: Development

SDLC, v1

Operations

Development

Governance

Iteration 1 Iteration 2

. . .

Iteration N

ALM

Development: Iterative processes

SDLC

Requirements Requirements Requirements

Monitor the application

Deploy application updates

Deploy the application

Aspects of ALM: Operations

Operations

Development

Governance

Visual Studio 2010: The Big Picture

1990s-2000s

Team development tools

1980s-1990s

Integrated development

environments (IDEs)

Version control tools

Build tools

Testing tools

Tools for Software DevelopmentAn evolution

Reporting and tracking tools

1970s-1980s

Editors

Compilers

Shared ServerMicrosoft Team Foundation Server

Team Development Tools

Requirements

Requirements Tools

Design Documents

Architecture Tools

Version Control/

Build Mgmt

Development Tools

Test Cases

Testing Tools

Project Statistics

Reporting and Tracking Tools

Business BenefitsHandoffs between functions are simpler and fasterVisibility into the project statusTraceability

Architecture

Shared Server

Requirements

Development

Testing

Project Tracking

Bug

Bug

Test Case

Test Case

Test Case

Test Case

Task

Task

Task

Requirement X

Managing and Tracking the ProjectExample Report: Stories Overview

Userstories

Percent of work completed

Summary of current test

results

Managing and Tracking the ProjectExample Report

Microsoft Confidential

Are we making progress on running test plans?

Are we fixing bugs?

What’s the quality of our bug fixes?

How are our buildsdoing over time?

Illustrating Visual Studio 2010

Visual Studio Team Foundation

Server 2010Microsoft

Excel

Microsoft Project

SharePointWeb Browser

Expression Studio

Visual Studio Lab Management

2010Visual Studio 2010

Other Microsoft

Other Vendors and Open Source

Microsoft Test Manager 2010

Visual Studio 2010 IDE

Visual Studio Team Explorer

Everywhere 2010

Eclipse IDE

Visual Studio Team Explorer

2010

Illustrating TFSVisual Studio

Team Foundation Server 2010

Work Item Tracking

• Requirements/ User stories• Tasks• Bugs• Test cases• …

Version Control

Process Templates

Build Management

Reports and Dashboards

Test Case Management

T

T

T

T

T

T

T

T

Lab Management

VM

TEAM FOUNDATION SERVER 2010 DEEP DIVE!

Team Foundation Server Focus AreasPlan and

Manage Your Project

Work Item Tracking

Process Guidance & Automation

Understand Parallel

Development

Version Control

Branch Visualization

Build Management

No More “No Repro” Bugs

Test Case Management IntelliTrace

Microsoft Test Manager

(MTM)

Lab Management

Report on Your Portfolio Dashboards Reports

PLAN & MANAGE YOUR PROJECT

UNDERSTAND PARALLEL DEVELOPMENT

Version Control

Integrated into Work Item Tracking, BuildsMajor Capabilities

ChangesetsWorkspacesBranch And MergeShelving

Client side copy of source

checked out from

repository

Owned by one user on one

machine

Changes in workspace

create “pending changes”

Workspace Mapping = Repository

folder mapped to Local Folder

Workspaces

Branch• A branch relationship is created in TFS to avoid duplication of history and

metadata• Path-space branching• Intelligent copies

Merge• Sync a branch into another• Cherry Picking changesets (include or omit)• Ability to show changes that have not been merged

Branch And Merge

Shelving

Set aside pending changes without checkinOptionally revert to unmodified filesRestore shelved changes by “unshelving”Unshelve other user’s changes

Power of task branching with less overhead

Task switching

Peer reviews

Backup WIP

Sharing

Build Automation

Extension of MS Build • Integrated Windows Workflow

Several scenarios supported

• Continuous Integration• Scheduled• Gated / Shelveset• Ad-hoc

Provides build reporting back to TFS

• Pass / Fail• Trend data

Integrated testing • Any automated test

Workflow based build

DEMO

NO MORE “NO REPRO” BUGSRich & Actionable Bugs

Actionable Bug

Enables immediate action.Contains:

Steps to ReproduceSystem InformationScreenshots & Video CaptureIntelliTrace

REPORT ON YOUR PORTFOLIO

At a Glance - Reporting

Choose your Warehouse• Cube• Relational

Built-in Reporting• SQL Server Reporting Services• Excel

Trending, aggregate, “roll-up” reports• Dashboards

Accessible via Portal, Team Explorer, others

Out-of-the-Box Agile Support

Baked-in best practicesAgile Workbooks.

Product BacklogIteration Backlog

Simplified Reporting

Reports using SQL Server Reporting Services.

Detailed and thoroughWorkbook queries with Microsoft Office Excel.

Fast and flexible

SharePoint Dashboards

Improved SharePoint integration Powerful dashboardsEnsures transparency for all stakeholders

VISUAL STUDIO 2010 EDITIONS

Conclusions

Modern software development requires a diverse set of toolsIntegrating those tools makes sense

Visual Studio 2010 provides an integrated set of diverse development tools

For large teams, small teams, and solo developers

Thank You and have a nice open door!

© 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to

be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.