1. Agile Planning and Iterations with
Scrum using Team Foundation
Server 2013
Allan Spartacus Mangune
Taughtworks, Inc.
facebook.com/mangune

2. Agenda
• Creation and Estimating Product Backlog
• Planning Iteration
• Creation of Sprint Backlog
• Completing Iteration

3. Product Backlog
• Also referred to Story
• Capture features to be developed
– Product owner and development team
– Enter detailed information right away
– Enter basic information and enter details as the
work progresses
• Monitor progress
• Helps translates vision to product

4. Adding Product Backlog
• Access the Team Web Access
• Navigate to the home page
• Click Product Backlog Item

5. Product Backlog Arrangement
• Arrange in priority order
• Open the Team Web Access
• Navigate to the home page and choose View
Backlog

6. Sprint Planning
• Development Team builds the Sprint Backlog
on Day 1 of Sprint
• Product Owner ensures that Product Backlog
items contains enough information
• Team members needs to plan for their
availability
• Completed Sprint Backlog contains work to be
done for the current Sprint

7. Team Capacity
• Helpful for determining the amount of work to
plan for the current Sprint
• Account for work days, holidays, and other
events that affect the Development Team’s
capacity
• Specify the kind of work each member will do

8. Setting up Team’s Capacity
• Navigate to web access home page
• Choose View backlog
• Select a Sprint and set up the Development
Team’s capacity

9. Committing Stories
• Development Team’s capacity is known
– Easy to decide on the number of Product backlog
items to commit

10. Choosing Backlog Items for the Sprint
• Move the product backlog items to Iteration

11. Defining and Estimating Sprint Backlog
• Development Team identifies tasks on
committed Stories
• Tasks must be linked to appropriate Story
• Development team estimates the number of
hours needed to complete each Task

12. Adding Tasks to a Product Backlog
• On the Product Backlog page, access the
Sprint
• Right-click the Story and click Add:Task

13. Task Board
• Center of activities in Sprint
• Helps visualize the progress of work

14. Updating the Task Board
• Access the Team Web Access
• Choose View board
• For the task to be started, drag the Task from
“TO DO” to “IP PROGRESS”
• For the task that is completed, drag the Task
from “IP PROGRESS” to “DONE”

15. Updating the Task Board

16. Review Progress
• View the state of Tasks through the Task board
• View the burndown chart
– Task board or current Sprint of the Backlog
• Capacity bars

17. Viewing Burndown Chart
• Access Team Web Access
• Navigate to the Team’s home page
• Open the Burndown chart
– You can also access the chart from the Product
backlog page or Task board

18. Impediments
• Obstacles that preventing or slowing down
work progress
• Typically identifies during daily Scrum
• Scrum Master helps removes these obstacles

19. Creating Impediment List
• Access the Team Web Access
• Navigate to the Impediment List
• Add a new Impediment

20. Completing the Iteration
• Development Team demonstrates the 100%
completed and potentially shippable product
increment
• Any unfinished Stories are returned to the
Product backlog

21. Moving Incomplete Story to Product
Backlog
• Access the Team Web Access
• Navigate to the Product Backlog page
• Drag the Story from the Sprint or click the
arrow and move the Story to the Product
backlog