Beta Team Planning page
Use the Team Planning page to pull work from the backlog and schedule work into iterations. Team Planning allows you to easily view the velocity of work items in a given iteration and whether the team is over capacity. This page is most effective if your team has already completed high-level planning on the Capacity Planning page. The Capacity Planning page enables your team to plan the features that customers need.
Once high-level planning has occurred, your team can begin to plan stories associated with the feature that are in the broader, high-level plan.
Team Planning includes:
- Page views
- Review the backlog
- Schedule work into iterations
You can switch between page views to view the following:
- An expanded view of the backlog.
- Drop-down menu with several options to filter the work you want to plan.
- Provides a way to move your work into a release or iteration.
- Drag-and-drop work items into iterations or releases.
- Indicators provide visual insight into missing work item estimates and velocity.
- Task popover to easily add and tasks associated to a work item.
- One-click deletion of work items in a release or iteration.
- Shows a more detailed view of your team's plan.
- View work in each iteration.
- Refine estimates or add missing estimates.
- Modify tasks as needed.
These page view options are located in the upper-right corner of the Team Planning page.
Review the backlog
As a team, you can review the backlog and designate work items to be added to each iteration. By default, the backlog displays the following:
- Feature ID and Name (if Group by Feature is enabled)
- Work item ID, Name, and Plan Estimate
Add a new work item
- Click the Add button at the top of the backlog.
- Type text into the name field to enable the Add button. Click Add to quickly add the work item, or click Add with Details to enter additional additional details for the work items before saving.
Search or scroll to select columns that you want to display on the backlog. Click Apply to confirm your selections.
View and edit details
You can inline edit many of the details on the backlog page by clicking once on the field. Type or select the new field value, then press Enter to save your changes. You can also click outside of the grid area to save. Press Esc to cancel any changes.
To edit additional fields, click the gear icon and select Edit. Make your changes on the editable detail page.
You can select a filter for your team's backlog that will allow you to easily view work that can be added to your team's plan. Multiple views are available.
Project-scoped work (user stories, defects, defect suites, test sets) with a Schedule State of less than In Progress and not scheduled into a release or an iteration.
Project-scoped work that had been scheduled into a release or iteration other than the release or iterations currently selected in the view and includes:
|Group by Feature (Unscheduled)||
Displays project-scoped leaf stories that have a Schedule State of less than Accepted and have neither a release nor an iteration. Leaf stories are grouped by their lowest-level portfolio item parent, regardless of the parent portfolio item's project. Visibility of the portfolio item is project-permission driven.
|Group by Feature (Unfinished)||
Displays project-scoped leaf stories that have a Schedule State less than Accepted, that are in a timebox prior to the selected release, and grouped by their lowest-level portfolio item parent, regardless of parent portfolio item's project. Only stories from previous timeboxes are displayed;stories scheduled for future timeboxes will not display. Visibility of the portfolio item is project-permission driven.
|Group by Feature in Release||
Displays project-scoped leaf stories that have a Schedule State less than Accepted, that are in the selected release and grouped by their lowest-level portfolio item parent, regardless of parent portfolio item's project. Visibility of the portfolio item is project-permission driven.
Project-scoped work that has been scheduled into the selected release but has yet to be scheduled in an iteration, and has a schedule state less than Accepted.
|Stories (unparented)||Shows project-scoped leaf stories with a Schedule State less than Accepted that are not scheduled in a release or iteration and do not have a lowest-level portfolio item type or story parent.|
Shows project-scoped leaf stories with a Schedule State less than Accepted that are not scheduled in a release or iteration.
Project-scoped defects that have a defect state other than Closed, and have not been scheduled into a release or iteration.
Project-scoped defect suites with a Schedule State less than Accepted that are not scheduled in a release or iteration.
Project-scoped test sets with a Schedule State less than Accepted that are not scheduled in a release or iteration.
Click the gear menu, located to the left of each work item in the backlog, and select Edit to view the details of the work item. You can also choose to rank the work item as highest or lowest in the backlog from the gear menu.
You can customize the number of work items shown in the backlog. By default, 25 work items display. To show more, click the drop-down menu and select the number of work items to display.
Schedule work into iterations
On the right side of the page, select the release you want to plan for from the drop-down list.
To modify iterations, click the gear menu and select Manage Iterations. This will direct you to the timeboxes iterations page.
Once your team has reviewed the backlog, it's time to start scheduling work into iterations for the next release. You can drag work items from the backlog and drop them into the iterations.
You can also drag-and-drop work items between iterations. For example, if you want to move a story from Iteration 1 to Iteration 2, you can do that by dragging the story from Iteration 1 and dropping it into Iteration 2.
Editable work item fields can be navigated with a mouse click or by using the tab key.
The bar next to each iteration displays the size of each work item relative to the velocity of the iteration. The percentage is an indicator of how much capacity the team has for the iteration. If the percentage is over 100%, the bar displays in red, indicating that work needs to be removed from the iteration in order to resolve the over-capacity issue.
The Issues column displays the icon if there are problems with the work item. Hover over the icon to view more details.
Examples of issues may include:
- A story does not have a plan estimate.
- An iteration's velocity is greater than 100%.
You can view the details of any work item in an iteration by clicking the gear menu, located to the left of each work item in an iteration, and selecting Edit. To remove a work item, click Remove from Plan from the gear menu.
You can view the whether a work item scheduled in an iteration has predecessors or successors. If there are predecessors or successors associated with the work item, the number of dependencies will display in the Dependencies column. Click the number to view those dependencies.
To view or update tasks for a work item in an iteration, click the iteration name under Iteration Allocations. Any tasks associated with the work item display next to that work item.
You can perform the following actions on the task popover:
- Add a new task by entering the name, selecting an owner and task estimate, then click Add or Add with Details.
- Inline edit fields.