The features of TFS 2012 that support sprint planning, do allow the team to consider product backlog, priorities and capacity of the team, for the length of sprint.
Note: In a follow up article, I have explained how to Use TFS 2012 and SCRUM to Run the Sprint Sprint planning usually begins by the time the earlier sprint run is nearing the finish line.
Abstract: In this article, I will explain how the sprint planning is done by the SCRUM Team using Team Foundation Server 2012 a.k.a TFS 2012.
I will also show you how to consider capacity of the team while planning the sprint backlog.
This can happen because either those items were beyond the capacity of the team, or were having some related impediment or were just not completed in the earlier sprint.
As the first activity of the sprint planning, the team will set the dates for the next sprint.
Each team member may work on multiple projects and hence may devote different amount of time for each of them.
You can open the current sprint on the Work – Backlog page of the Web Access.
This total may work out to be more than the capacity of the team and that is where the sprint and member load balancing will be needed to be done.When the prompt for team project is shown, select your team project from the list and click Connect.We will now create a new input list by selecting the radio button for that option We can now see the basic structure of data that is needed to be entered for work items.In the case of TFS 2012, that can be done through the Web Access interface.If you are beginning from Team Explorer, then on the home page of the team project, you can select the link to settings In the settings, select the link for ‘Work Item Iterations’ Then you may either set dates or change them for Sprint 2 to suit your sprint length. Now the team will set the capacity of various team members for this week.