Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Move stories from the release backlog to sprint backlog

Log in to subscribe to topics and get notified when content changes.

Move stories from the release backlog to sprint backlog

You can move stories from the release backlog to the sprint backlog through the planning board.

  1. Navigate to Agile Development > Planning > Planning Board.
  2. In the left pane context menu, select Release backlog to display the stories that still need to be worked on for this release.
  3. Open the same context menu again and select Backlog only to display only those stories not yet moved from the release backlog to a sprint. Deselect Backlog only to show all the stories in the release backlog, including those already moved to a sprint backlog.
  4. In the right pane context menu, select Sprint backlog and then select the sprint to add the stories to.
  5. Click the icon beside a story name in the release backlog (left pane) and drag the story to any location in the sprint backlog (right pane).
  6. Drag the story to any position in the list using the same icon.

    You can use this feature to rank stories in a backlog by importance.

  7. To move all the stories at once, click the Drag all icon at the bottom of the pane.
  8. To access the story progress board or the task progress board, select the appropriate option from a context menu opened from one of these locations:
    • Right-click a story in either pane.
    • Click the arrow in the backlog title of either pane.
  9. To edit the Release form, click the arrow in the Release Backlog title in the left pane and select Edit Release.
  10. To edit the Sprint form, click the arrow in the Sprint Backlog title in the right pane and select Edit Sprint.
  11. Use the gauge in the upper portion of the right pane to ensure that the total story points in the sprint do not exceed the capacity of the team.
    The gauge shows the percentage of the team's capacity that is committed and the number of points available against the total points of the release. When the team is working within its capacity, the gauge is blue, and the total committed percentage is less than 100%.
    Figure 1. Capacity Gauge 1
    When the total points of the sprint exceed the team's capacity, the gauge turns red and displays a total committed percentage in excess of 100%.
    Figure 2. Capacity Gauge 2
    When the team is working at exactly 100% of its capacity, the gauge turns green.
    Figure 3. Capacity Gauge 3

    What Do I Do Next?

    After the scrum master establishes the sprint backlog in the planning board and makes sure the team capacity is sufficient, the sprint is ready for work. The team members manage their stories and tasks within the individual records or from a progress board.