how to be a good tfs master

How to be a good TFS Master(using a sprinkle of Scrum of course)

Damian Brady

http://www.damianbrady.com.au

Twitter: @damovisa | #qalmug

Delivering Awesome Web Applications

Agenda

What is a TFS Master?

Why TFS?

More Pain for Better Results

Scrum with TFS

User Stories and the Backlog

What is a TFS Master?

?

Ensure your team gets the most out of TFS

http://brdy.in/sswtfsmaster

Why TFS?

?

TFS is much more than just source control

Why TFS?

0% 100%

Source control Lab Management

Backlog

Continuous Build

Continuous Deployment

TFS for Source Control

#1 reason to use TFS?

Annotate

http://brdy.in/sswannotate

More Pain for Better Results

This is good pain

TFS for Source Control

?

Check in regularlyhttp://brdy.in/sswcheckin

Only check in code that compiles and passes testshttp://brdy.in/sswcheckin2

TFS for Source Control

Shelvesets

Check-in Policies

Check-in Policies

http://brdy.in/sswcheckinpolicy

Automated Builds in TFS

?

Gate Gated Checkin Runs all unit tests

CI Triggered after a checkin Runs all unit tests and all coded UI tests

Nightly Triggered … nightly Run all unit tests, coded UI test, and load tests

http://brdy.in/sswbuilds

Scrum with TFS

?

?

TFS Scrum v2.0 will be the new default

User Stories in TFS

?

INVEST Independent Negotiable Valuable Estimable Small Testable

http://brdy.in/sswuserstory

Story Cards

http://brdy.in/sswstorycard

Adding Backlog Items

Excel

Project

TeamCompanion

Adding Backlog Items (in 2012)

Excel

Web Access

Project

TeamCompanion

Estimating Inestimable Tasks

?

Tasks should be estimable

Spikes can be used to estimate inestimable tasks

http://brdy.in/sswestimate

Acceptance Criteria

Positive Criteria

Negative Criteria

Gold Plating

http://brdy.in/sswacceptance

Definition of Done

?

We define: 7 levels of “Done” in software quality 3 levels of “Done” in communication

http://brdy.in/sswdone

Summary

TFS Master – get the most out of TFS

TFS is more than just source control

Tips

1. Annotate not History

2. Shelve unfinished work

3. Check-in Policies

4. Automated Builds

5. Story Cards

6. Spiking

7. Acceptance Criteria

8. Definition of Done

4 things…

DamianBrady@ssw.com.

au

http://

www.damianbrady.com.au

@damovisa

http://

www.dddbrisbane.com

Delivering Awesome Web Applications

Thank You!

Sydney | Melbourne | Brisbane | Adelaide

info@ssw.com.au

www.ssw.com.au

Find me on Slideshare!

http://www.slideshare.net/damovisa/