Prepare for a sprint
At the sprint planning meeting, create a backlog of user stories and defects you plan to handle in the sprint, and define tasks for the backlog items. Then assign backlog items and allocate tasks to team members.
- Open the Release Management > Sprint Backlog page.
- Make sure the correct sprint and team are selected.
What do you want to do?
Use the following pages to plan sprint backlogs:
Release Backlog: Plan sprint backlogs by dragging items from the release backlog into sprint buckets. For details, see Plan team sprints.
Planning Board: Use the Planning Board for a bird's eye view of the sprint plans for the entire release, and drag items from one sprint to another. For details, see Use the planning board.
You can also add unplanned user stories directly to the sprint backlog. Click Add Item.
When your Sprint plan is final, click to set the baseline for a Scope Change report. After the sprint ends, you can Export a Scope Change report to Excel from the Sprint Closure tab. Each time you set a sprint's baseline, the new baseline overwrites any previous ones.
If you do not set a baseline for a sprint, the Scope Change report uses the data from 2 days after the sprint's beginning as a baseline.
For more details, see Sprint Scope Change report.
The backlog items are ranked in the sprint backlog according to their ranks in the release backlog. Sort the sprint backlog by rank, and adjust the ranks as necessary.
For details, see Rank the backlog.
Backlog items are usually written from a user perspective. In order to create a development work plan, you need to break the user stories and defects into detailed tasks, written from a developer perspective. Tasks are displayed in the pane below the backlog grid.
Drag tasks up or down to organize them, such as in the order they should be performed.
- Right-click a backlog item, and select Add Task.
Fill in the following details for each task:
Task A description of the task. Assignee The user assigned to the task. By default, the owner of the backlog item is selected. You can assign the task to any member of the team. Estimation
Tasks are measured in hours, as opposed to backlog items that are estimated in story points.
Specify the number of hours you estimate it will take to complete the task.
Administrators define default task estimations on the Workspace > Settings configuration page.
Color Category Optionally, assign the task to a color category. For example, use color categories to identify development, QA, and documentation tasks.
Define the criteria that a user story must meet in order to be considered complete. Acceptance tests are displayed in the pane below the backlog grid.
According to your workspace settings, a user story may not to be set to Done until all its acceptance tests have passed.
Before you allocate tasks to team members, you should calculate each team member's capacity.
Then, assign backlog items and allocate tasks to team members by dragging them to user buckets in the planning pane on the right.
Compare assigned hours vs. capacity
The top of the planning pane indicates whether you are planned within your team capacity () or over-planned (), by displaying: the total assigned hours for the team sprint vs. the total capacity of all team members.
Total assigned hours includes both invested and remaining hours.
Each team member bucket indicates the amount of hours assigned vs. the total capacity defined for that team member.
Click the capacity link for each team member to modify that team member's capacity:
|Assign backlog item||To set the owner of a backlog item, select the item and drag it to the user's bucket. All the backlog item's tasks are added to the owner's workload. Later, you can reallocate specific tasks to other users.|
When defining tasks, you can assign them to a user. Later, you can reallocate tasks by dragging them to user buckets in the planning pane.
Note: If a backlog item was reassigned to another team, tasks may still be allocated to users in the original team.
Export a sprint backlog grid to an Excel or CSV file to use sprint data in other applications. Exported data includes any columns and filters displayed on the grid, and the Description and Comments fields.
Tip: If you are exporting to Excel, you can also include tasks and acceptance tests.
Define a filter for the items you want to export and arrange columns you want to include.
Click More Actions > Export Backlog to Excel or Export Backlog to CSV.
In the Export Backlog to Excel dialog box, select whether you want to include tasks and acceptance tests.
Tasks and acceptance tests are exported to separate Excel tabs.
- Task Board. Use the task board to track the progress on each of your tasks, and report the time invested in them. For details, see Use the Task Board.
- Storyboard. Use the storyboard to visualize and enforce your team processes on the development of backlog items. The storyboard can be used within the boundaries of a single sprint, or across multiple sprints. For details, see Kanban storyboard.