• Save
Agile planning and iterations with Scrum using Team Foundation Server 2013
Upcoming SlideShare
Loading in...5
×
 

Agile planning and iterations with Scrum using Team Foundation Server 2013

on

  • 2,819 views

 

Statistics

Views

Total Views
2,819
Views on SlideShare
2,748
Embed Views
71

Actions

Likes
5
Downloads
1
Comments
0

3 Embeds 71

http://www.scoop.it 63
https://www.facebook.com 7
https://hootsuite.scoop.it 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Agile planning and iterations with Scrum using Team Foundation Server 2013 Agile planning and iterations with Scrum using Team Foundation Server 2013 Presentation Transcript

  • Agile Planning and Iterations with Scrum using Team Foundation Server 2013 Allan Spartacus Mangune Taughtworks, Inc. facebook.com/mangune
  • Agenda • Creation and Estimating Product Backlog • Planning Iteration • Creation of Sprint Backlog • Completing Iteration
  • 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
  • Adding Product Backlog • Access the Team Web Access • Navigate to the home page • Click Product Backlog Item
  • Product Backlog Arrangement • Arrange in priority order • Open the Team Web Access • Navigate to the home page and choose View Backlog
  • 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
  • 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
  • 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
  • Committing Stories • Development Team’s capacity is known – Easy to decide on the number of Product backlog items to commit
  • Choosing Backlog Items for the Sprint • Move the product backlog items to Iteration
  • 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
  • Adding Tasks to a Product Backlog • On the Product Backlog page, access the Sprint • Right-click the Story and click Add:Task
  • Task Board • Center of activities in Sprint • Helps visualize the progress of work
  • 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”
  • Updating the Task Board
  • 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
  • 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
  • Impediments • Obstacles that preventing or slowing down work progress • Typically identifies during daily Scrum • Scrum Master helps removes these obstacles
  • Creating Impediment List • Access the Team Web Access • Navigate to the Impediment List • Add a new Impediment
  • Completing the Iteration • Development Team demonstrates the 100% completed and potentially shippable product increment • Any unfinished Stories are returned to the Product backlog
  • 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