microsoft alm platform overview

Microsoft Application Lifecycle Management

Steve Langesr. developer technology specialist | microsoft – denver, costevenl@microsoft.com | slange.me

a 30-minute overview

Agenda

• What is Application Lifecycle Management?

• Microsoft’s ALM Platform• Focus Areas– Implement process with minimal overhead– Plan & manage projects– Align roles across the lifecycle– Report across project boundaries

• Summary

WHAT IS ALM?

Application Lifecycle Management (ALM) is the marriage of governance, development, and operations.

Working together from idea to retirement

But first, what about you?

Version Control

Bug Tracking

Task Management

Automated Testing

Test Case Management

Build Automation

Requirements Management

Development Tool

MICROSOFT’S ALM PLATFORM

Introducing

Microsoft ALM tools work to integrate vertically, not just horizontally. Governa

nce

Development

Operations

Working Vertically

UserStories

Tasks

Tests

Check-in

Build

Build

Bug

BusinessAnalyst

Tester

Developer

ALM Platform: Focus Areas

Process with minimal overhead

Plan & manage projects

Align roles across the lifecycle

Report across project boundaries

PROCESS WITH MINIMAL OVERHEAD

ALM Platform: Focus Areas

Process Guidance & Automation

• Baked into Team Foundation Server

• Provides contextual guidance (documentation)

• Delivered via Process Templates• Use templates out of the box, or

create your own• Completely customizable

Enable predictability and repeatability across projects

Process Templates

MSF = Microsoft Solutions FrameworkCMMI = Capability Maturity Model Integration

MSF for Agile Software Development

MSF for CMMI

Visual Studio Scrum

• Product planning based on user stories and story points

• Team progresses most work by moving from active to resolved to closed

• Team is not usually required to support rigorous audits

• Product planning based on requirements and CR’s• Most work moves from proposed to active to

resolved to closed• Team is required to maintain rigorous audit trails• Team is working toward CMMI appraisal

• Development lifecycle follows Scrum framework (based on Agile principles)

PLANNING & MANAGING PROJECTS

ALM Platform: Focus Areas

Planning & Managing Projects

Organization•Classification•Assignment•Customization

Visibility•Relate artifacts, actions, intent•Parent/child relationships•Rollup & drilldown

User Comfort•Use familiar tools for role•Excel, Project, IDE, web, others..•Eases adoption

Organization

Classification of work artifacts

– Where– When

Integration organizes efforts

– Build– Collaboration

Customize to meet team needs

– Not the other way around

Visibility

Top-to-bottom traceability

Agile planning

Proactive notifications

Related information = project insight

User Comfort

• Team members work in the tools that suit them

User Comfort

• Team members work in the tools that suit them

User Comfort

• Team members work in the tools that suit them

User Comfort

• Team members work in the tools that suit them

User Comfort

• Team members work in the tools that suit them

User Comfort

• Team members work in the tools that suit them

User Comfort

• Team members work in the tools that suit them

User Comfort

• Team members work in the tools that suit them

Role-specific tools are simply front-ends for a much larger collaborative environment.

REPORT ACROSS PROJECT BOUNDARIES

ALM Platform: Focus Areas

ALM data is as complex as you think

Reporting: Not just for managers

Bug Status Trends

Reactivations

Sprint Burndown

Build Quality Indicators

Test Case Readiness

Remaining Work

Bug Status

Unplanned Work

Burndown & Burn Rate

Status on All Iterations

Build Success Over Time

Requirements Progress

Release Burndown

Stories Overview

Build Summary

DashboardsExcel

Reporting Services

SUMMARYApplication Lifecycle Management

Microsoft’s ALM Solution

Process with minimal overhead

Plan & manage projects

Align roles across the lifecycle

Report across project boundaries

Create happy teams, enabling success from idea to retirement

Questions?

Thank You

Steve Langesr. developer technology specialist | microsoftstevenl@microsoft.com | 303-918-0500 slange.me | @stevelange

Upcoming Office Hours:– 11/18 @ 9:30 AM (Pacific)– 12/2 @ 9:30 AM (Pacific)– 12/16 @ 9:30 AM (Pacific)– 12/30 @ 9:30 AM (Pacific)– 1/13 (2012) @ 9:30 AM (Pacific)

(see blog for details)

APPENDIX

Links & Resources

• Videos– Video: Proactive Project Management with Visual Studio 2010 – Improving Developer-Tester Collaboration with Microsoft Visual Studio 2

010

• Whitepapers– What is ALM?– IDC MarketScape Excerpt: IT Project and Portfolio Management

2010 Vendor Analysis – The Forrester Wave: Agile Development Management Tools, Q2 2010 – Attaining Optimal Business Value from Agile Software Development – White Paper: Reconciling the Agile Team with Enterprise Project Manag

ement – Magic Quadrant for Integrated Software Quality Suites

• Microsoft Solutions Framework– MSF for Agile homepage – MSF for CMMI homepage – Visual Studio Scrum 1.0 homepage – MSF for Agile+SDL v5.0

Links & Resources

• Articles & Product Pages–Microsoft Application Lifecycle Managem

ent– Effective Team Development– Heterogeneous Development– Product homepages• Visual Studio• Team Foundation Server• Test Professional

Case Studies• Flextronics - Visual Studio 2010 helps Flextronics’ developers and QA

teams work together• Wintellect - Wintellect uses the testing tools in Visual Studio to speed up

debugging• AccessIT - Visual Studio 2010 helps Access IT give its customers better

team collaboration• Sogeti - Sogeti better understands legacy systems with Visual Studio 2010• EPiServer - EPiServer tests software more effectively and efficiently with

Visual Studio 2010• Equiniti - Share Registrar Cuts Testing Time and Improves Application

Lifecycle Management • ICONICS - ICONICS is cutting cost and increasing productivity with Visual

Studio 2010• Penn National Insurance - Penn National Insurance boosted productivity

and reduced testing time using Visual Studio 2010• Readify - Using Visual Studio 2010, Readify saves time and money with

virtual testing• Länsförsäkringar AB - Swedish insurance company expects to cut software

development time and costs by 20 percent• 3M - Eliminating “no repro” bugs helps 3M accelerate delivery of products

into the marketplace• Mitchell - Unified ALM enables Mitchell International to gain agility in a

diverse development environment

TFS

Bu

ild

Arch

itectu

re

Code

Lab Management

Pro

ject P

lan

Req

Task

Microsoft’s ALM Solution

DevTest

Test Case

Rich Bug TFS Web Access

Help TicketsProd Issues

Feature Requests

IntelliTrace

Code AnalysisCode Metrics

Code Profiler

Dep. Graph Auto

Test

Unit

Web & Load

Database

User Interface

Data

base

Version

Gen Test DataDeploy

Compare Test Impact

Design

Validate

Compile

Deploy App/DB

Validate Arch

Execute Tests

Analyze Impact

Needs Work

Test

Manager

Design

Plan/OrganizeExecute TestsFast Forward

PreProd

Stage

TFS

Source

Gated Check-in

Shelve

Branch

Visualize

Merge

ProdReady

Bug Status Report• Is the team fixing bugs

quickly enough to finish on time?

• Is the team fixing high priority bugs first?

• What is the distribution of bugs by priority and severity?

• How many bugs are assigned to each team member?

back

Bug Trends Report• How many bugs is the

team reporting, resolving, and closing per day?

• What is the overall trend at which the team is processing bugs?

• Are bug activation and resolution rates declining toward the end of the iteration as expected?

back

Reactivations Report• How many bugs are

being reactivated? • How many user stories

are being reactivated? • Is the team resolving and

closing reactivated bugs at an acceptable rate?

back

Build Quality Indicators Report• What is the quality of the

software?• How often are tests

passing, and how much of the code is being tested?

• Based on the code and test metrics, is the team likely to meet target goals?

back

Build Success Over Time Report• What parts of the project have produced software that is ready to be

tested?• What parts of the project are having trouble with regressions or bad

checkins?• How well is the team testing the code?

back

Build Summary Report• What is the status of all builds over time?• Which builds succeeded? • Which builds have a significant number of changes to the code? • How much of the code was executed by the tests?• Which builds are ready to install?

back

Burndown and Burn Rate Report• Is the team likely to finish

the iteration on time? • Will the team complete

the required work, based on the current burn rate?

• How much work does each team member have?

back

Remaining Work Report• What is the cumulative flow

of work?• Is the team likely to finish

the iteration on time? • Is the amount of work or

number of work items in the iteration growing?

• Does the team have too much work in progress?

• How is the team doing in estimating work for the iteration?

Hours of Work# of Work Items

back

Status on All Iterations Report• Is steady progress being made across all iterations?

• How many stories did the team complete for each iteration? • How many hours did the team work for each iteration? • For each iteration, how many bugs did the team find, resolve, or close?

back

Stories Overview Report (Agile)• How much work does each story require?

• How much work has the team completed for each story? • Are the tests for each story passing? • How many active bugs does each story have?

back

Stories Progress Report (Agile)• How much progress has the team made toward completing the work for

each story? • How much work must the team still perform to implement each user

story? • How much work did the team perform in the last calendar period?

back

Requirements Progress Report (CMMI)• How much progress has the team made toward completing the work for

each requirement? • How much work must the team still perform to implement each

requirement? • How much work did the team perform in the last calendar period?

back

Requirements Overview Report (CMMI)• How much work does each Requirement require?

• How much work has the team completed for each Requirement? • Are the tests for each Requirement passing? • How many active bugs does each Requirement have?

back

Release Burndown (Scrum)• How much work remains in the release?• How quickly is your team working through the product backlog?

back

Sprint Burndown (Scrum)• How much work remains in the sprint? • Is your team on track to finish all work for the sprint?• When will your team finish all work for the sprint?• How much work for the sprint is in progress?

back

Unplanned Work Report• How much work

was added after the iteration started?

• Is too much work being added during the iteration?

back

Test Case Readiness Report• When will all the test cases be ready to run? • Will all the test cases be ready to run by the end of the iteration? • How many test cases must the team still write and review? • How many test cases are ready to be run?

back

Test Plan Progress Report• How much testing has

the team completed?• Is the team likely to

finish the testing on time?

• How many tests are left to be run?

• How many tests are passing?

• How many tests are failing?

• How many tests are blocked?

back