Real World Scrum with TFS2013

Benjamin Day

Benjamin Day

• Brookline, MA• Consultant, Coach, & Trainer• Microsoft MVP for Visual Studio ALM• Team Foundation Server, Software Testing,

Scrum, Software Architecture• Scrum.org Classes

Professional Scrum Developer (PSD) Professional Scrum Foundations (PSF)

• www.benday.com, benday@benday.com, @benday

Online courses at Pluralsight.com

How many of you have heard ofScrum.org?

(Warning: Shameless plug.)

Professional Scrum Foundationsfor Teams training in Cambridge, MA on

February 24th & 25th. http://bit.ly/186qR4y

On with the show.

The Goal: Show you how to use TFS

to support Scrum.

Disclaimer:TFS isn’t going to lead you to

Agile/Scrum nirvana.

TFS will help...

…but TFS won’t just do it for you.

Software is a human endeavor.

There are actual people involved…

…and (fortunately / unfortunately)

you’re still going to need to talk to them.

You’ll use TFS tostreamline the human automation

and as the place of record.

The Goal: Show you how to use TFS

to support Scrum.

Scrum in a nutshell.

Scrum in a nutshell.

• Team agrees to deliver working software in 30 days or less

• Schedule a time to show that working software

• Team creates the software

• Team shows the software. Gathers feedback for next time.

Scrum in a larger nutshell

• There’s an idea for some software

• Gather a Team• Team agrees to deliver

working software in 30 days or less

• Craft a Product Backlog• Schedule a time to show

that working software• Team decides what they

think they can do in a Sprint.

• Team creates the software and assesses progress on a 24 hour interval

• Team shows the Done software. Gathers feedback for next time.

• Team conducts a Retrospective on how it went.

• Repeat

So how do you do that with Team Foundation Server 2013?

Scrum TFS2013 Demos

• There’s an idea for some software Create a Team Project in TFS

• Gather a Team Configure team(s)

• Team agrees to deliver working software in 30 days or less Configure Sprints

Scrum TFS2013 Demos

• Craft a Product Backlog Create a Product Backlog in TFS Organize the Product Backlog using Features

Does your team have a writtenDefinition of Done (DoD)?

My ‘quickie’ sketch of a DoD for a PBI.

• Checked in and merged/integrated with code for sprint

• Unit tested without a shared database

• Code Coverage of >75%• Compiles as part of an

automated build• Code Reviewed by

someone else

• Test plan(s) in TFS• Tested by someone else• No P1 or P2 bugs• Demo’d and accepted by

PO before Sprint Review• Database code & migration

scripts checked in• Deployment script for

feature• No undone work.

“What does QA do at the start of a Sprint?”

Scrum TFS2013 Demos

• Team decides what they think they can do in a Sprint Sprint Planning in TFS Capacity Planning (…and don't forget QA testing in the DoD)

Scrum TFS2013 Demos

• Team creates the software and assesses progress on a 24-hour interval. Run your Daily Scrum using the Scrum Board Maintain situational awareness using the Scrum Board Use the Burndown Chart to determine if you’re on target

Supporting your DoD Demos

• Automated builds• Test plans in MTM & Test Hub• Manual Testing• Coded UI Tests• Code Reviews• Gather Feedback with Feedback Manager• Lab management deployment builds

Helps support your testing efforts Helps prep for your Sprint Review meetings

Streamline “Situational Awareness”

• Use Team Rooms to help keep everyone aware of what’s going on.

“What about planning for the next sprint?”

“What are my BA’s doing?”

Answer:PowerPoint Storyboarding*

* = amongst other things

Supporting planning

• PowerPoint Storyboarding

Scrum in a larger nutshell

• There’s an idea for some software

• Gather a Team• Team agrees to deliver

working software in 30 days or less

• Craft a Product Backlog• Schedule a time to show

that working software• Team decides what they

think they can do in a Sprint.

• Team creates the software and assesses progress on a 24 hour interval

• Team shows the Done software. Gathers feedback for next time.

• Team conducts a Retrospective on how it went.

• Repeat

Any last questions?

Thank you.

www.benday.com | benday@benday.com