Download - Scrum With TFS 2010
Scrum withMicrosoft Visual Studio Team Foundation Server 2010Adrian Dunne | Microsoft Singapore
19th August 2011Microsoft Singapore ALM Event
Team Foundation Server 2010
An Open Platform
Source: Forrester Reasearch, Inc.
5
Why is Agile Catching On?
Business Needs Demand It
“Firms today experience a much higher velocity of business change. Market opportunities appear or dissolve in months or weeks instead of years. This increased business velocity demands much greater agility from business systems.”
Diego Lo Giudice and Dave West, ForresterFebruary 2011Transforming Application Delivery
Value Delivered Early and Often Working software continually delivered Regular discussions with stakeholders Maximize ROI
Agenda
Scrum with TFS 2010 Planning the Project Planning a Sprint Running a Sprint
Product Backlog
Sprint Backlog
Sprint
Daily
Potentially Shippable Increment
How do you Plan the Project?
Product Backlog Evolving backlog of Product Backlog
Items Describes what users need and value Owned by the Product Owner Prioritized by business value Each PBI is written from the user’s
perspective
Planning the Project
“As a new customer I want to register online
so I can use the services offered”
PBIs are listed on the backlog in priority
orderNew PBIs are added
to the product backlog
The team estimates the ‘effort’ for each PBI
5
8
3
5
8
1
Pri
ori
ty
Product Backlog
Product Backlog Item
Product Backlog in TFS 2010
Product Backlog query Creating new PBIs Prioritizing Estimating effort
DemoManaging the Product Backlog in TFS 2010
Agenda
Scrum with TFS 2010 Planning the Project Planning a Sprint Running a Sprint
Product Backlog
Sprint Backlog
Sprint
Daily
Potentially Shippable Increment
What is Sprint Planning?
The product owner and the team add Product Backlog Items to the sprint
Each PBI is decomposed into tasks The team makes a commitment to
each PBI
The team thinks this PBI is more work than they can commit to…
Product Backlog
PBIs
Planning a Sprint
PBIs Tasks (Points)
Iteration Backlog
Commi
t!
Commi
t!3
3
3
Can’t Commi
t!
The team breaks down
each story into tasks
Based on estimates the team commits
to each PBI
During the sprint planning meeting, the product owner and the team add PBIs to the
sprint
Product Backlog
PBIs Tasks (Points)
Iteration Backlog
Planning a Sprint
3
3
3
3
Commi
t!
The larger story is removed from the
sprint and the team considers a smaller story on
the backlog
? Commi
t!
Commi
t!
The team can commit to this smaller story
The sprint is now planned and the team is ready to get
started!
PBIs
Sprint Planning
Break down PBIs into tasks
Team members Sign up for tasks
Commit Track progress
DemoPlanning a Sprint in TFS 2010
Agenda
Scrum with TFS 2010 Planning the Project Planning a Sprint Running a Sprint
Product Backlog
Sprint Backlog
Sprint
Daily
Potentially Shippable Increment
How do you Run a Sprint?
Daily Scrum What was done What will be done Impediments Sprint Burn-down
Deliver a “potentially shippable” increment
Demo the value delivered Retrospective
Product Backlog
PBIs PBIs Tasks (Points)
Iteration Backlog
Running a Sprint
The team starts work on the
tasks…
Running a Sprint
2/1 2/4 2/72/1
02/1
32/1
62/1
92/2
22/2
52/2
8
0
20
40
60
80
100
Remaining CompletedCompleted work is reported daily
Product Backlog
PBIs PBIs Tasks (hours)
Iteration Backlog
Running a Sprint
2/1 2/4 2/72/1
02/1
32/1
62/1
92/2
22/2
52/2
8
0
20
40
60
80
100
Remaining Completed
Product Backlog
PBIs PBIs Tasks (hours)
Iteration Backlog
2/1 2/4 2/72/1
02/1
32/1
62/1
92/2
22/2
52/2
8
0
20
40
60
80
100
Remaining Completed
Running a Sprint
Each User PBI has been implemented
All work for the sprint is “done-
done”
Product Backlog
PBIs PBIs Tasks (hours)
Iteration Backlog
Product Backlog
PBIs PBIs Tasks (hours)
Iteration Backlog
Running a Sprint
The team holds a demo to show the value they have
delivered
And the team has developed a “potentially shippable” increment
Running a Sprint
The latest increment is shipped to customers
Product Backlog
User Stories User Stories Tasks (hours)
Iteration Backlog
PBIs delivered in the last sprint are closed
Running a Sprint
The team holds a retrospective…
PBIs and tasks are cleared from the
backlog – the team delivered on its
commitment
Product Backlog
PBIs PBIs Tasks (Points)
Iteration Backlog
What worked? What didn’t work? What can the team
do to improve?
Running a Sprint
New PBIs are added to the
Product Backlog
Product Backlog
PBIs PBIs Tasks (Points)
Iteration Backlog
Running a Sprint
The backlog is prioritized and
ready for the team to plan the next
sprint
Product Backlog
PBIs PBIs Tasks (Points)
Iteration Backlog
Running a Sprint
Record completed work daily
Track and Resolve Impediments
Track progress with reports and dashboards
Retrospectives
DemoRunning a Sprint in TFS 2010
Tracking Progress - Development
Burndown chart tracks remaining and completed
work
Tracking Progress - Development
Tracking Progress - Development
Tracking Progress - Development
Detailed sprint progress is tracked on
the project portal
The burndown shows the team on track…
And almost half of the tasks remain
openBut the team hasn’t closed any
of the three PBIs…
Tracking Progress - Development
The Scrum Master opens an issue to track the problem
the portal has identified
Tracking Progress - Development
The issue is opened and tracked in TFS
Tracking Progress – QA
Test are passing…
But bugs are climbing steadily
The portal brings data together so it can be analyzed to ensure success on a
sprint
Tracking Progress - QARich set of reports
track progress
Product Backlog
Sprint Backlog
Sprint
Daily
Potentially Shippable Increment
vNextA few agile driven features coming to TFS
Sprint Planning ToolCapacity & Sprint Burndown Burndown
progress
Team capacity at a glance
• The enhanced work item management tools in Team Web Access
• Tool pre-populates required data
• Streamlines the association and update process.
• Effectively allocate work balancing load with available capacity
• Real-time feedback on the updates to the plan
Task Board in Team Web Accessupdate the status of work items visually
Burndown progress
Easily move tasks around
Team NavigatorMy Work
• Allows the developer to easily context switch• Packages all the
open work• Save entire
environment settings
• Fix urgent bugs• Recall task, work is
instantly restored in context and error-free.
• Resume where the developer left off
© 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.