Post on 07-Sep-2014
description
Agenda
− 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
“As a new customer I want to register online
so I can use the services offered”
“As a new customer I want to register online
so I can use the services offered”
Stories are listed on the backlog in priority order
Stories are listed on the backlog in priority order
New stories are added to the
product backlog
New stories are added to the
product backlog
The team estimates each story using story
points
The team estimates each story using story
points
55
88
33
55
88
11
Pri
ori
ty
Product Backlog
User Stories
Product Backlog
User Stories
Planning the Project
33
33
33
44
44
44
Sprint 3Sprint 3
The product owner re-prioritizes the
backlog
The product owner re-prioritizes the
backlog
Sprint 4Sprint 4
Stories are planned for
completion in upcoming sprints
Stories are planned for
completion in upcoming sprints
Pri
ori
ty
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 query
in Team Explorer
Product Backlog
New stories created by the Product Owner
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
The new story provides a guide to ensure the
story is written from the customer’s perspective
Product BacklogEach story is
ranked by priority and assigned a
story point value
Each story is ranked by priority
and assigned a story point value
Product Backlog
Product Backlog workbook for
planning future sprints
Product Backlog workbook for
planning future sprints
Product Backlog Workbook
Stories that are too large are left on the
backlog
Stories that are too large are left on the
backlogEach story is placed in an upcoming
sprint
Each story is placed in an upcoming
sprint
Product Backlog Workbook
Each sprint is added to Iteration
Planning worksheet…
Each sprint is added to Iteration
Planning worksheet…
… with start/end dates and the size
of the team
… with start/end dates and the size
of the team
The product owner can use the velocity of the team to help plan for upcoming
sprints
The product owner can use the velocity of the team to help plan for upcoming
sprints
Agenda
− 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
Product Backlog
User Stories
Planning a Sprint
User Stories Tasks (hours)
Iteration Backlog
CommiCommi
tt!!
CommiCommi
tt!!33
33
33
Can’t Can’t CommiCommi
tt!!
The team breaks down
each story into tasks
The team breaks down
each story into tasks
The team thinks this story
is more work than they can commit to…
The team thinks this story
is more work than they can commit to…
Based on estimates the team commits to each story
Based on estimates the team commits to each story
During the sprint planning meeting, the
product owner and the team add User Stories to the sprint
During the sprint planning meeting, the
product owner and the team add User Stories to the sprint
Product Backlog
User Stories User Stories Tasks (hours)
Iteration Backlog
Planning a Sprint
User Stories Tasks (hours)
33
33
33
33
CommiCommi
tt!!
The larger story is removed from the
sprint and the team considers a smaller story on
the backlog
The larger story is removed from the
sprint and the team considers a smaller story on
the backlog
CommiCommi
tt!!
CommiCommi
tt!!
The team can commit to this smaller story
The team can commit to this smaller story
The sprint is now planned and the team is ready to get
started!
The sprint is now planned and the team is ready to get
started!
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
Each sprint has an Excel workbook to assist the team in
making a commitment
Iteration Backlog Workbook
Dates for the sprint are added…
Dates for the sprint are added…
Iteration Backlog Workbook
... and any planned
interruptions
... and any planned
interruptions
Iteration Backlog Workbook
The team breaks down the first user story into
tasks
The team breaks down the first user story into
tasks
Iteration Backlog Workbook
Each task is estimated in
hours
Each task is estimated in
hours
Iteration Backlog Workbook
The team checks their capacity for the sprint
The team checks their capacity for the sprint
Iteration Backlog Workbook
The next story is broken down…
The next story is broken down…
Iteration Backlog Workbook
Iteration Backlog Workbook
… but one team
member has too much
work
… but one team
member has too much
work
The team has
capacity…
The team has
capacity…
Iteration Backlog Workbook
Iteration Backlog Workbook
The final story is broken
down
The final story is broken
down
Iteration Backlog Workbook
Based on capacity and estimates, the
team is overcommitted
Based on capacity and estimates, the
team is overcommitted
Iteration Backlog Workbook
The final story is removed…The final story is removed…
Iteration Backlog Workbook
And replaced with a smaller story from the
product backlog
And replaced with a smaller story from the
product backlog
Iteration Backlog Workbook
… but one team member still has too much work
… but one team member still has too much work
The team is comfortable
committing to this story…
The team is comfortable
committing to this story…
Iteration Backlog Workbook
Tasks are reassignedTasks are
reassigned
Iteration Backlog Workbook
Tasks are reassignedTasks are
reassigned
Iteration Backlog Workbook
Work is now load balanced
across the team
Work is now load balanced
across the team
Iteration Backlog Workbook
The final step is to publish
the data back to TFS
The final step is to publish
the data back to TFS
Sprint planning is complete!
Sprint planning is complete!
Agenda
− 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
Product Backlog
User Stories User Stories Tasks (hours)
Iteration Backlog
Running a Sprint
The team starts work on the
tasks…
The team starts work on the
tasks…
Running a Sprint
Completed work is
reported daily
Completed work is
reported daily
Product Backlog
User Stories User Stories Tasks (hours)
Iteration Backlog
Running a Sprint
Product Backlog
User Stories User Stories Tasks (hours)
Iteration Backlog
Running a Sprint
Each User Story has
been implemente
d
Each User Story has
been implemente
d
All work for the sprint is “done-
done”
All work for the sprint is “done-
done”
Product Backlog
User Stories User Stories Tasks (hours)
Iteration Backlog
Product Backlog
User Stories User Stories Tasks (hours)
Iteration Backlog
Running a Sprint
The team holds a demo to show the value they have
delivered
The team holds a demo to show the value they have
delivered
And the team has developed a “potentially shippable” increment
And the team has developed a “potentially shippable” increment
Running a Sprint
The latest increment is shipped to customers
The latest increment is shipped to customers
Product Backlog
User Stories User Stories Tasks (hours)
Iteration Backlog
Running a Sprint
The team holds a
retrospective…
The team holds a
retrospective…
Stories delivered in the last sprint are
closed
Stories delivered in the last sprint are
closed
Stories and tasks are cleared from the
backlog – the team delivered on its
commitment
Stories and tasks are cleared from the
backlog – the team delivered on its
commitment
Product Backlog
User Stories User Stories Tasks (hours)
Iteration Backlog
What worked? What didn’t work? What can the team
do to improve?
What worked? What didn’t work? What can the team
do to improve?
Running a Sprint
New Stories are added to the
Product Backlog
New Stories are added to the
Product Backlog
Product Backlog
User Stories User Stories Tasks (hours)
Iteration Backlog
Running a Sprint
The backlog is prioritized and
ready for the team to plan the next
sprint
The backlog is prioritized and
ready for the team to plan the next
sprint
Product Backlog
User Stories User Stories Tasks (hours)
Iteration Backlog
Running a Sprint
− Record completed work daily
− Track progress with reports and dashboards
− Retrospectives
Updating Tasks
Multiple interfaces for updating work
items
Multiple interfaces for updating work
items
Updating Tasks
Team ExplorerTeam Explorer
Updating Tasks
Iteration Backlog workbook
Iteration Backlog workbook
Updating Tasks
Team Project portal
Team Project portal
Updating Tasks
Updating Tasks
Updating Tasks
Team Web Access
Team Web Access
Tracking Progress
Burndown chart tracks remaining and completed
work
Burndown chart tracks remaining and completed
work
Tracking Progress
Tracking Progress
Tracking ProgressDetailed sprint
progress is tracked on the project portal
Detailed sprint progress is tracked
on the project portal
The burndown shows the team on track…
The burndown shows the team on track…
And almost half of the tasks remain
open
And almost half of the tasks remain
openBut the team hasn’t closed
any of the three stories…
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
The Scrummaster opens an issue to track the problem
the portal has identified
Tracking Progress
The issue is opened and
tracked in TFS
The issue is opened and
tracked in TFS
Tracking Progress
Test are passing…Test are
passing…
But bugs are climbing steadily
But bugs are climbing steadily
The portal brings data together so it can be analyzed to
ensure success on a sprint
The portal brings data together so it can be analyzed to
ensure success on a sprint
Tracking ProgressRich set of reports
track progressRich set of reports
track progress
Retrospective Capture retrospectives using
the Team wiki on the Project Portal
Capture retrospectives using
the Team wiki on the Project Portal
Sample documents are provided as a
guide
Sample documents are provided as a
guide
Agenda
− 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
Questions/Follow-Up
− Contact− Aaron Bjork
− abjork@microsoft.com− http://blogs.msdn.com/aaronbjork
− TFS Resources− http://blogs.msdn.com/bharry− http://social.msdn.microsoft.com/Forums/en-U
S/category/vsts− http://msdn.microsoft.com/en-us/teamsystem/
default.aspx
© 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.