29 Jan 2011

Agile Project Management with

Team Foundation Server 2010

Sk. Md. Riyaz General Manager – DFDR Dept.

Agenda
− Collaboration In TFS 2010
− Scrum with TFS 2010 using MSF for Agile 5.0
− Planning the Project
− How do you plan the project?
− Project planning in TFS 2010
− Planning a Sprint
− What is sprint planning?
− Sprint planning in TFS 2010
− Running a Sprint
− How do you run a sprint?
− Running a sprint in TFS 2010
Visual Studio 2010
 How do you define a process?

4
What does a process template
look like?
− Behind the scenes it’s just a bunch of XML
What does a process template
look like?
What’s Included?
− Work Item Type
Definitions
− Work Item Links
− Queries
− Reports
− Portal Settings
− Source Control
Settings
What’s Included? (cont.)
− Work Item Type
Definitions
− Work Item Links
− Queries
− Reports
− Portal Settings
− Source Control
Settings
What’s Included? (cont.)
− Work Item Type
Definitions
− Work Item Links
− Queries
− Reports
− Portal Settings
− Source Control
Settings
What’s Included? (cont.)
− Work Item Type
Definitions
− Work Item Links
− Queries
− Reports
− Portal Settings
− Source Control
Settings
What’s Included? (cont.)
− Work Item Type
Definitions
− Work Item Links
− Queries
− Reports
− Portal Settings
− Source Control
Settings
What’s Included? (cont.)
− Work Item Type
Definitions
− Work Item Links
− Queries
− Reports
− Portal Settings
− Source Control
Settings
Templates in the Box
− MSF for Agile 5.0  MSF for CMMI 5.0
− Lightweight − Deeper hierarchy
− Relatively flat − Stretch to fit
− Stretch to fit − Teams interested in deep
− Teams implementing traceability & audit-ablity
Agile methods (Scrum,
XP, etc)
Other Templates
− EMC/Conchango – Scrum for Team System
− Cognizant – FDD
− Osellus – IRIS Process Author
− Object Group – Process Mentor
− Microsoft – MPT (Microsoft Process
Template)
− Others on CodePlex

− Or, create a custom template, starting from

the basic template
14
Traceability for MSF Agile 5.0

Story

Tests / Tested By

Related Parent / Child

Test Bug Task

Code Coverage Change Sets Change Sets

Code
Scrum for Team System Work
Item Hierarchy Example
Product Implemented By Sprint
Backlog Item Backlog Task

Tested By

Impeded By
Acceptance
Test
Impediment
Relationships are bi-directional

Product Implements Sprint

Backlog Item Backlog Task

Tests

Impedes

Acceptance
Test
Impediment
Adding a Linked Work Item
− You must select the correct Link Type and
Work Item Type when adding a linked item.
Which leads to…
Support for ATDD
Inferring Ready
Agenda
− Collaboration In TFS 2010
− Scrum with TFS 2010 using MSF for Agile 5.0
− Planning the Project
− How do you plan the project?
− Project planning in TFS 2010
− Planning a Sprint
− What is sprint planning?
− Sprint planning in TFS 2010
− Running a Sprint
− How do you run a sprint?
− Running a sprint in TFS 2010
How do you Plan the Project?
− Product Backlog
− Evolving backlog of user stories (requirements)
− Describes what users need and value
− Owned by the Product Owner
− Prioritized by business value
− Each story is written from the user’s perspective
 Planning the Project
Product Backlog
“As a new customer I want to
User Stories
register online so I can use
55 the services offered”
88

55
Stories are listed on the
Priority

The
backlog in team estimates
priority order each story
33 using story points
88
New stories are added to
11 the product backlog
 Planning the Project
Product Backlog
Stories are planned for
User Stories completion
Sprint 3 in upcoming
sprints
33

33

33
Priority

Sprint 4
The product owner re-
44
prioritizes the backlog
44

44
… let’s look at the Product Backlog in
TFS 2010
Product Backlog in TFS 2010
− Product Backlog query
− Creating new user stories
− Prioritizing
− Estimating story points
− Add user stories to
upcoming sprints
Product Backlog

Product backlog
query in Team
Explorer
Product Backlog

New stories created by

the Product Owner
Product Backlog

The new story provides a guide

to ensure the story is written
from the customer’s
perspective
Product Backlog
Each story is ranked by
priority and assigned a
story point value
Product Backlog

Product Backlog
workbook for planning
future sprints
Product Backlog Workbook

Stories that are too large are

left on the backlog
Each story is placed
in an upcoming
sprint
Product Backlog Workbook

The product owner can use

the velocity of the team to
help plan for upcoming
… with start/end dates and sprints
the size of the team
Each sprint is added to
Iteration Planning
worksheet…
Agenda
− Collaboration In TFS 2010
− Scrum with TFS 2010 using MSF for Agile 5.0
− Planning the Project
− How do you plan the project?
− Project planning in TFS 2010
− Planning a Sprint
− What is sprint planning?
− Sprint planning in TFS 2010
− Running a Sprint
− How do you run a sprint?
− Running a sprint in TFS 2010
What is Sprint Planning?
− The product owner and the team add user
stories to the sprint
− Each story is decomposed into tasks
− The team makes a commitment to each
user story
Planning a Sprint
Product Backlog Iteration Backlog
User Stories User Stories Tasks (hours)

33 Based on Commit!
33
estimates the team
The team thinks
commits to sprint
During the each planning
33
this story ismeeting,
morestoryTheproduct
the team breaks
owner
work than theyand
canthe down eachUser
team add story Commit!
commit to…Stories tointo tasks
the sprint

Can’t
Commit!
Planning a Sprint
Product Backlog Iteration Backlog
User Stories User Stories Tasks (hours)

33
Commit!
33

33

?33 The larger story is

Commit!
removed from the
sprint andThe
the sprint
team is now
considers aplanned
smaller
The
and the
team to
can
team is
story on the backlog ready
commit
get to this
started!
smaller story Commit!
Product Backlog and Sprint
Backlog Planning

Demo

39
How Sprint Planning will look for you
Sprint Planning
− Break down user stories
into tasks
− Load balance
− Commit
− Track interruptions
− Track progress
Iteration Backlog Workbook

Each sprint has an Excel

workbook to assist the
team in making a
commitment
Iteration Backlog Workbook

Dates for the sprint

are added…
Iteration Backlog Workbook

... and any planned

interruptions
Iteration Backlog Workbook

The team breaks

down the first user
story into tasks
Iteration Backlog Workbook

Each task is
estimated in hours
Iteration Backlog Workbook

The team checks

their capacity for
the sprint
Iteration Backlog Workbook

The next story is

broken down…
Iteration Backlog Workbook
Agenda
− Collaboration In TFS 2010
− Scrum with TFS 2010 using MSF for Agile 5.0
− Planning the Project
− How do you plan the project?
− Project planning in TFS 2010
− Planning a Sprint
− What is sprint planning?
− Sprint planning in TFS 2010
− Running a Sprint
− How do you run a sprint?
− Running a sprint in TFS 2010
How do you Run a Sprint?
− Track Progress
− Daily Sprint Meeting
− What work has been completed
− What work remains
− Deliver a “potentially shippable” increment
− Demo the value delivered
− Retrospective
Running a Sprint
Product Backlog Iteration Backlog
User Stories User Stories Tasks (hours)

The team starts work

on the tasks…
Running a Sprint
Product Backlog Iteration Backlog
User Stories User Stories Tasks (hours)

Completed work is Remaining Completed

reported daily 100
80
60
40
20
0
2/1 2/8
Running a Sprint
Product Backlog Iteration Backlog
User Stories User Stories Tasks (hours)

Remaining Completed
100
80
60
40
20
0
2/1 2/8 2/15
Running a Sprint
Product Backlog Iteration Backlog
User Stories User Stories Tasks (hours)
Each User Story
has been
implemented

Remaining Completed
100
80
60
40
20

All work for

0
2/1
the 2/8
sprint2/15 2/22 2/28
is “done-done”
Running a Sprint
Product Backlog Iteration Backlog
User Stories User Stories Tasks (hours)

And the team has The team holds a demo to

developed a “potentially show the value they have
shippable” increment delivered
Running a Sprint
Product Backlog Iteration Backlog
User Stories User Stories Tasks (hours)

The latest
increment is
shipped to
customers
Running a Sprint
Product Backlog Iteration Backlog
User Stories User Stories Tasks (hours)

Stories and tasks are cleared

from thedelivered
Stories backlog in
– the
the team
delivered
last sprint on its
are closed
commitment
What worked?
What didn’t work? What
The team holds a
can the team do to
retrospective…
improve?
Running a Sprint
Product Backlog Iteration Backlog
User Stories User Stories Tasks (hours)

New Stories are

added to the Product
Backlog
Running a Sprint
Product Backlog Iteration Backlog
User Stories User Stories Tasks (hours)

The backlog is
prioritized and ready for
the team to plan the
next sprint
Running a Sprint

Demo

72
How Running a Sprint Will Look for
You
Running a Sprint
− Record completed work
daily
− Track progress with
reports and dashboards
− Retrospectives
Updating Tasks

Multiple interfaces for

updating work items
Updating Tasks

Team Explorer
Updating Tasks

Iteration Backlog
workbook
Updating Tasks

Team Project portal

Updating Tasks
Updating Tasks
Updating Tasks

Team Web Access

Tracking Progress

Burndown chart tracks

remaining and
completed work
Tracking Progress
Tracking Progress
Tracking Progress
Detailed sprint progress is
tracked on the project portal

The burndown
shows the team And almost half of the
on track… tasks remain open
But the team hasn’t
closed any of the
three stories…
Tracking Progress

The Scrummaster opens

an issue to track the
problem the portal has
identified
Tracking Progress

The issue is opened and

tracked in TFS
Tracking Progress
The portal brings data
together so it can be
analyzed to ensure
success on a sprint

Test are
passing…

But bugs are climbing

steadily
Tracking Progress
Rich set of reports track
progress
Retrospective Capture retrospectives
using the Team wiki on
the Project Portal

Sample documents are

provided as a guide
Agenda
− Collaboration In TFS 2010
− Scrum with TFS 2010 using MSF for Agile 5.0
− Planning the Project
− How do you plan the project?
− Project planning in TFS 2010
− Planning a Sprint
− What is sprint planning?
− Sprint planning in TFS 2010
− Running a Sprint
− How do you run a sprint?
− Running a sprint in TFS 2010
© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market
conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation.
MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.