Plan the Iteration with Team Web Access
Our tutorial continues with Peter, the Scrum master on the Fabrikam team. For the next development iteration, the team meets to determine its capacity and discuss the product backlog items that it can implement and complete in that iteration. Peter runs the meeting, records any time off that team members plan to take, creates work items for the tasks that the team determines are required by each backlog item, and checks the team's capacity along the way by using the team project's backlog page in Team Web Access.
Requirements
-
Some features might not be available depending on your permissions or edition of Team Foundation Server. See Features Accessed Through Web Permissions.
In this topic
Before the meeting starts, Peter goes to the capacity pane of the backlog page for the current iteration (Sprint 1). He reminds the team that the iteration runs from Oct. 10 (today) through Oct. 28 and asks who is taking time off. Julia, a developer on the team, plans to take several days off. Peter enters Julia’s days off and sets the number of hours that each member of the team works per day.
-
On the capacity pane, type the number of hours of work in a typical workday for each team member.
-
For each team member that takes one or more days off, choose
, and enter the number of days off.
Tip
|
|---|
|
This team assigns work to individuals when it plans the iteration. If your team assigns tasks later, you can use the team capacity to make sure your team doesn't have more work than it can finish in the iteration. If each team member tends to do only one type of activity (develop or test, for example), you can set each team member’s activity on the capacity page and monitor the team's capacity by activity. |
Before the meeting, the team reviewed and prioritized the product backlog items based on their value, level of risk, and dependencies. See Create the Backlog with Team Web Access.
Now, Peter opens the prioritized product backlog and assigns the first item to the current iteration (Sprint 1). The team discusses each task required to complete the backlog item, and Peter creates a task work item for each task. The team estimates the number of hours of work required by each task. Peter adds the tasks to the backlog item, assigns them to the people who will perform them, and records the estimates.
After the team creates, estimates, and assigns the tasks for the first backlog item, Peter checks the team’s capacity, and the team continues this process for the next item in the product backlog until the team’s capacity is nearly reached.
-
On backlog, choose Product Backlog.
-
Drag a product backlog item from the contents pane to the backlog pane, and drop it on the iteration (Sprint 1).
-
On backlog, choose the iteration (Sprint 1).
-
On contents, choose
. -
Near the top of the work-item form, enter the task's title.
-
Open the Assigned To list, choose the person who will complete the task.
-
In Remaining Work, enter the estimated number of hours that the task takes to complete.
