Being Agile with Any Process Template in TFS 2012

Preview:

DESCRIPTION

Using an Agile template does not MAKE you Agile. Using a CMMI template does not PREVENT you from being agile. In this talk, I compare and contrast the TFS process templates available out of the box, and relate the process template artifacts and features to the types of methodologies and practices they support.

Citation preview

Angela Dugan

ALM Practice Manager

Polaris Solutions

Angela.Dugan@PolarisSolutions.com

Angela Dugan

Mobile Solutions

Project Leadership

.NET Solutions

Application Lifecycle Management

Quick Review of Agile

SCRUM = Agile Agile <> Scrum

Activities Artifacts DeliverablesSizing Product Backlog* Working Software*

Pre-Planning User Stories*

Planning* Burn-down*

Daily Standup Definition of Done*

Sprints/Iterations* Sprint Backlog*

Sprint Review/Demo

Retrospective

Visual Studio ALM Ecosystem

E X T E N S I B L E A P I s

Version Control

Build Automation

CustomizableProcesses

RequirementsManagement

Test CaseManagement

ProjectManagement

End-to-EndTraceability

Lab ManagementAnalytics

TFS Process TemplatesScrum

Agile

CMMI

PBIs, Bugs

Task, Test Case, & Bug

Managing your product backlog

as PBIs (and Bugs)

PBIs are broken down into

specific tasks

Bugs are tracked during the

iteration, added to backlog

Pla

nn

ing

Exe

cutio

n

Epics & Themes

User Story

Task, Test Case, & Bug

Managing your product backlog

as User Stories

As a <> I want to <> so that I can

<>.

Stories are broken down into

specific tasks

Bugs are tracked during the

iteration

Pla

nn

ing

Exe

cutio

n

Business

Objective

Feature

Change

Request

Task

Test Case, & Bug

Requirements are created at

many levels and tracked as a

hierarchy

Tracking changes to features.

Work during execution

Implementation verification

Pla

nn

ing

Exe

cutio

n

Process area Visual Studio Scrum MSF for Agile MSF for CMMI

Bug backlog management Bug (Scrum) • Bug (Agile)

• Triage Workbook

• Bug (CMMI)

• Triage Workbook

Project management Impediment (Scrum)• Issue (Agile)

• Issues Workbook

• Issue (CMMI)

• Risk (CMMI)

• Review (CMMI)

• Issues Workbook

Test management• Test Case

• Shared Steps

• Test Case

• Shared Steps

• Test Case

• Shared Steps

Code review and feedback

• Code Review Request

• Code Review Response

• Feedback Request

• Feedback Response

• Code Review Request

• Code Review Response

• Feedback Request

• Feedback Response

• Code Review Request

• Code Review Response

• Feedback Request

• Feedback Response

Audit trail Not supported Minimal Supported

Tasks SCRUM Agile CMMI

Monitor bug activity, reactivations, and

trends.

• Bug Status Report

• Bug Trends Report

• Reactivations Report

• Bug Status Report

• Bug Trends Report

• Reactivations Report

Monitor build activity, success, and trends. • Build Success Over Time

Report

• Build Summary Report

• Build Quality Indicators

Report

• Build Success Over Time

Report

• Build Summary Report

• Build Quality Indicators

Report

• Build Success Over Time

Report

• Build Summary Report

Track project health, team burn rate, and

task completion.

You can review this report daily or weekly

to monitor the progress of the team

during an iteration.

• Release Burndown (Scrum)

• Sprint Burndown (Scrum)

• Velocity (Scrum)

• Burndown and Burn Rate

Report (Agile)

• Remaining Work Report

• Status on All Iterations

Report

• Stories Overview Report

(Agile)

• Stories Progress Report

(Agile)

• Burndown and Burn Rate

Report (CMMI)

• Remaining Work Report

• Status on All Iterations

Report

• Requirements Progress

Report (CMMI)

• Requirements Overview

Report (CMMI)

Determine added work. (a.k.a. “Scope

Creep”)• Unplanned Work • Unplanned Work

Monitor testing activity. • Test Case Readiness Report

• Test Plan Progress Report

• Test Case Readiness Report

• Test Plan Progress Report

• Test Case Readiness Report

• Test Plan Progress Report

“Agile” Features in TFS 2012Planning Tools

Reporting

Supporting Features - Teams

“Agile” Planning Tools Work for Any

Process Template

Tools generated per Team

Drag and Drop for Quick Prioritization

and Assignment

Real-time Repor ting

Interactive Kanban Board

Interactive Task Board

Customizable

Ideal Trend = trend in which the

team burns down all remaining

effor t by the end of the sprint.

Remaining Work = hours

remaining for tasks that are

marked as “ To Do” in a sprint

Track how much effor t your team has

repor ted as complete for each sprint .

Est imate how much backlog effor t your

team can handle in future sprints.

Answers the fol lowing quest ions:

How much effor t has your team

completed in each sprint?

What is the maximum velocity of your

team?

What is the minimum velocity of your

team?

What is the average velocity of your

team?

Making it “real”

http://www.amazon.com/Visual-Studio-Team-Foundation-Server/dp/0321864875

http://www.amazon.com/Succeeding-Agile-Software-Development-Using/dp/0321579364

http://www.agilemanifesto.org/

http://msdn.microsoft.com/en-us/vstudio/ff459609

http://blogs.msdn.com/b/briankel/archive/2013/04/17/list-of-all-visual-studio-alm-virtual-machines.aspx

Recommended