![microsoft team foundation server 2010 requirements microsoft team foundation server 2010 requirements](https://i.ytimg.com/vi/o75ZeH46SRU/maxresdefault.jpg)
Running a SprintProduct BacklogIteration BacklogUser StoriesUser StoriesTasks (hours) Running a SprintProduct BacklogIteration BacklogUser StoriesUser StoriesTasks (hours)Completed work is reported daily Product BacklogIteration BacklogUser StoriesUser StoriesTasks (hours)Running a SprintThe team starts work on the tasks… How do you Run a Sprint?Track ProgressDaily Sprint MeetingWhat work has been completedWhat work remainsDeliver a “potentially shippable” incrementDemo the value deliveredRetrospective Iteration Backlog WorkbookThe final step is to publish the data back to TFSSprint planning is complete! Iteration Backlog WorkbookWork is now load balanced across the team Iteration Backlog WorkbookTasks are reassigned Iteration Backlog Workbook… but one team member still has too much workThe team is comfortable committing to this story… Iteration Backlog WorkbookAnd replaced with a smaller story from the product backlog Iteration Backlog WorkbookThe final story is removed… Iteration Backlog WorkbookBased on capacity and estimates, the team is overcommitted Iteration Backlog WorkbookThe final story is broken down Iteration Backlog WorkbookThe team has capacity…… but one team member has too much work Iteration Backlog WorkbookThe next story is broken down… Iteration Backlog WorkbookThe team checks their capacity for the sprint Iteration Backlog WorkbookEach task is estimated in hours Iteration Backlog WorkbookThe team breaks down the first user story into tasks Iteration Backlog WorkbookDates for the sprint are added… Iteration Backlog WorkbookEach sprint has an Excel workbook to assist the team in making a commitment Sprint PlanningBreak down user stories into tasksLoad balanceCommitTrack interruptionsTrack progress … let’s look at Sprint Planning in TFS 2010 Product BacklogIteration BacklogUser StoriesUser StoriesTasks (hours)Planning a SprintUser StoriesTasks (hours)Commit!333The larger story is removed from the sprint and the team considers a smaller story on the backlogCommit!?3The sprint is now planned and the team is ready to get started!The team can commit to this smaller stor圜ommit!
![microsoft team foundation server 2010 requirements microsoft team foundation server 2010 requirements](https://docs.microsoft.com/en-us/previous-versions/azure/devops/tfs-2015/reference/tfs-ps-sync/media/pstfs_provisioning.png)
Product BacklogUser StoriesPlanning a SprintIteration BacklogUser StoriesTasks (hours)Commit!Based on estimates the team commits to each stor圓3The team thinks this story is more work than they can commit to…During the sprint planning meeting, the product owner and the team add User Stories to the sprint3The team breaks down each story into tasksCommit!Can’t Commit! What is Sprint Planning?The product owner and the team add user stories to the sprintEach story is decomposed into tasksThe team makes a commitment to each user story Product Backlog WorkbookThe product owner can use the velocity of the team to help plan for upcoming sprints… with start/end dates and the size of the teamEach sprint is added to Iteration Planning worksheet… Product Backlog WorkbookStories that are too large are left on the backlogEach story is placed in an upcoming sprint Product BacklogProduct Backlog workbook for planning future sprints Product BacklogEach story is ranked by priority and assigned a story point value
![microsoft team foundation server 2010 requirements microsoft team foundation server 2010 requirements](https://i.ytimg.com/vi/hz_sGZNYbY0/maxresdefault.jpg)
Product BacklogThe new story provides a guide to ensure the story is written from the customer’s perspective Product BacklogNew stories created by the Product Owner Product BacklogProduct backlog query in Team Explorer Product Backlog in TFS 2010 Product Backlog quer圜reating new user storiesPrioritizingEstimating story pointsAdd user stories to upcoming sprints … let’s look at the Product Backlog in TFS 2010 Product BacklogUser StoriesPlanning the ProjectStories are planned for completion in upcoming sprintsSprint 3333Sprint 4The product owner re-prioritizes the backlogPriority444 Planning the ProjectProduct Backlog“As a new customer I want to register online so I can use the services offered”User Stories58Stories are listed on the backlog in priority orderThe team estimates each story using story points5Priorit圓New stories are added to the product backlog81 How do you Plan the Project?Product BacklogEvolving backlog of user stories (requirements)Describes what users need and valueOwned by the Product OwnerPrioritized by business valueEach story is written from the user’s perspective Scrum with Team Foundation Server 2010Aaron BjorkSenior Program ManagerMicrosoft CorporationĪgendaScrum with TFS 2010 using MSF for Agile 5.0Planning the ProjectHow do you plan the project?Project planning in TFS 2010Planning a SprintWhat is sprint planning?Sprint planning in TFS 2010Running a SprintHow do you run a sprint?Running a sprint in TFS 2010