Implementing Scrum Using

Team Foundation Server

2012
David Starr

Chief Software Craftsman

Scrum.org

David Starr
david@scrum.org
@elegantcoder
Chief Craftsman, Scrum.org
ElegantCode.com Founder
Microsoft ALM MVP
Find Me Later At

DEV-TLC: Application Lifecycle Management

Our Backlog
Why Scrum?
Scrumdamentals
Visual Studio Scrum 2.0
The Product Backlog
The Sprint
Getting to Done

Module 1
Why Scrum?

You might care about Scrum if

These Things Are
Taking Longer

These Things Are

Declining

Changing our products

Quality

Planning new features

Value of work done

Implementing new features

Trust and Morale

Releasing our products

Customer relationships

Changing our minds

New Feature ROI

Planning

Analysis

Develop

Test

Integrate

Validate

Deploy

Time

Analysis

Develop

Develop

Develop

Develop

Develop

Test
Integrate
Validate

Test
Integrate
Validate

Test
Integrate
Validate

Test
Integrate
Validate

Deploy

Analysis
Deploy

Analysis
Deploy

Analysis
Deploy

Analysis

Test
Integrate
Validate

Deploy

Planning

Visibility

Business Value

Ability to Change

Risk

Talking to Management
Software in 30 Days
By Ken Schwaber and
Jeff Sutherland

ISBN 978-1-118-20666-9
Available now

Module 2
Scrumdamentals

Scrum is
A framework for Agile software
development
A set of rules
(defined in the Scrum Guide)
Easy to learn
Difficult to master

http://scrum.org

Elements of Scrum
Roles

Product
Owner
Developme
nt Team
Scrum
Master

Artifacts

Increment
Product
Backlog
Sprint
Backlog

Events

Sprint
Sprint
Planning
Daily Scrum
Sprint
Review
Retrospectiv
e

Scrum Master

Sprint Planning

Sprint Review

Product
Owner

Sprint
Retrospective

Dev Team
Sprint
Daily
Scrum

Product
Backlog
Sprint
Backlog

Increment

Module 3
Visual Studio
Scrum 2.0

Visual Studio Scrum 2.0

The TFS Process Template for Scrum
Collaboratively developed between Scrum.org and
Microsoft
Models the most common implementation model of
Scrum
Scrum continues to evolve as does TFS

Visual Studio Scrum 2.0

Work Item Types
Product Backlog Item

Queries

Product Backlog
Feedback Requests
Task
*
Code Review Request * Current Sprint
Code Review Response
Blocked Tasks
*
Open
Feedback Request *
Impediments
Feedback Response *
Sprint Backlog
Impediment
Test Cases
Test Case
Unfinished Work
Shared Steps
Work in Progress

Reports
Backlog Overview *
Release Burndown
Sprint Burndown
Velocity
Build Success Over
Time
Build Summary
Test Case Readiness
Test Plan Progress

Reports
Scrum reports
Backlog Overview
Release Burndown
Sprint Burndown
Velocity

Engineering reports
Builds Success Over Time
Build Summary
Test Case Readiness
Test Plan Progress

Team Web Access

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

Teams
A Team is a new concept in TFS 11
Rich metadata
Name
Description
Photo

Team Alerts
Vast improvement over individual
subscription
Alerts can be created
for groups or teams
Many templates to
choose from
Note: to use alerts TFS must
point to an SMTP server

Module 4
The Product
Backlog

Backlog Accuracy and Item Detail

Vague

Other
Backlog
Items

Understood Estimated PBIs

Next
Release

Next
Next
Sprint

Next
Sprint

Tasks

This
Sprint

Grooming the Product Backlog

Development Team helps the Product Owner
prepare the Product Backlog to be actionable
An ongoing activity
Emerging details of PBIs
Value
Effort estimates
Acceptance criteria
Order

Module 5
The Sprint

Sprint
Sprint
Plannin
g

Daily
Scrums

Sprint
Review

Sprint
Retro

Cone of Uncertainty
This is when projects are
typically funded.

Cone of Uncertainty in Scrum

Commitment vs. Forecast

A Common Expression of a Sprint

Backlog
Product Backlog
Sprint Backlog

Velocity
30

Top 3 Avg
23
Best Case

25
20

Middle 3 Avg 19
Likely Case

Feature Points 15

Bottom 3 Avg 14
Worst Case

10
5
0

5
Sprint

Planning Ahead with Scrum

Product Backlog
Estimate: 2
Estimate : 20
Estimate : 20
Estimate : 3
Estimate : 5

Worst Case:
3 Sprints X 14 points = 42 points
Most Likely Case:
3 Sprints X 19 points = 57points

Estimate : 1

Best Case:
3 Sprints X 23 points = 69 points

Estimate : 8
Estimate : 13
Estimate : 3
Estimate : 100
Estimate : 13

Top 3 Avg - 23
Best Case

Middle 3 Avg 19
Likely Case

Bottom 3 Avg
-14
Worst Case

Module 6
Getting to "Done"

Done and Undone

Each Increment must be Done
Definition of Done (DoD)
A simple, auditable checklist owned by the team
It can be influenced by organizational standards
and specific requirements of the product or
release

Software Development Feedback Cycles

Operational Acceptance (Production)
User Acceptance Testing
System, Performance, Other -ility Testing
Integration Testing
Continuous Integration *
Check-In *
Developer Tests Pass
Compile and Link
IntelliSense

Cost
of
Error

Defining Done for the Plumber

Done and Undone

By Ken Schwaber and David Starr
On MSDN
http://bit.ly/NyUyOW

Thank You
David Starr
david@scrum.org
@elegantcoder
Scrum.org | Elegantcode.com
Find Me Later At

DEV-TLC: Application Lifecycle Management

Related Content
Breakout Sessions
FDN02

Application Lifecycle Management (ALM): Its a Team Sport

DEV321 Continuous Feedback in Agile Teams

DEV344 Developer Collaboration with Visual Studio 2012
DEV346 All Aboard the Team Foundation Server Express
DEV212 Implementing Scrum Using Team Foundation Server 2012
DEV316 Application Lifecycle Management Tools for C++ in Visual Studio 2012
AAP309 Making Agile Estimation Work
DEV263 Dev-Ops Best Practices On The Microsoft Stack
DEV214 Introducing the New Visual Studio 2012 Unit Testing Experience
DEV337 Software Testing with Microsoft Test Manager 2012 and Lab Management
DEV370 Automating Server-Based Build, QA and Test with Visual Studio 2012

Related Content
Breakout Sessions
DEV362 From Development to Production: Optimizing For Continuous Delivery
DEV310 Continuous Delivery of Windows Azure Cloud Apps
DEV318 Working on an Agile Team with Visual Studio 2012
DEV390 IntelliTrace, What Is It and How Can I Use It To My Benefits
DEV217 Deep Dive Into Team Foundation Server 2012 Agile Management Tools
DEV345 The Accidental Team Foundation Server Admin
AAP401 Real World Developer Testing with Visual Studio 2012
DEV340 Taking ALM to the Cloud with the Team Foundation Service
DEV317 Going Beyond F11: Debug Better and Faster with Visual Studio 2012
DEV312 Create Robust, Maintainable Coded UI Tests with Visual Studio 2012
DEV411 Testing Un-Testable Code with Fake in Visual Studio 2012

Related Content
Breakout Sessions
DEV324 A Modern Architecture Review: Using the New Code Review Tools
DEV412 Identify & Fix Performance Problems with Visual Studio 2012 Ultimate

Hands-on Labs (session codes and titles)

DEV11HOL
DEV12HOL
DEV13HOL
DEV16HOL
DEV17HOL
DEV19HOL

Agile Project Management in Team Foundation Server 2012

Build the Right Software and Collaborate Effectively Using Storyboarding and Feedback
Tools in Visual Studio 2012
Using IntelliTrace with Production Systems to Quickly Diagnose and Fix Issues
Learn How Microsoft Test Manager 2012 Will Embrace an Exploratory Testing Approach
Explore the New Unit Testing and Code Clone Capabilities of Visual Studio 2012
Discover How the New Features of Team Foundation Server 2012 Can Improve
Collaboration in Your Development Team

Resources
Learnin
g
Connect. Share. Discuss.

Microsoft Certification & Training Resources

http://europe.msteched.com

www.microsoft.com/learning

TechNe
t
Resources for IT Professionals

http://microsoft.com/technet

Resources for Developers

http://microsoft.com/msdn

Evaluations
Submit your evals
online
http://europe.msteched.com/sessions