Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Backlog planning for a release or sprint

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

Backlog planning for a release or sprint

Use release planning list and sprint planning board to view and plan a backlog for a release or a sprint.

Based on the story ranking, you can plan to move stories from product backlog to release backlog, or from group backlog to sprint backlog.

Release Planning
During release planning, the product owners select the prioritized stories from the product backlog that should be completed in a given release. This set of stories that are completed in a release forms the Release Backlog.
Sprint Planning
During sprint planning, the scrum master and the group members define their sprint schedule. Then along with product owner, they select stories from the group backlog that should be completed in each sprint. The stories to be completed in a sprint is termed as Sprint Backlog.

The ability to plan a sprint effectively relies on a well-defined backlog that the team understands. The assignment group should ask questions to the product owner to clarify areas they do not understand. Only after team members understand a story can they make an accurate estimate of the effort require to complete it.

A group that is able to estimate story points accurately is more effective in sprint planning. For example, a group which knows that it can commit to 20 points in a sprint should add stories to the sprint backlog that total 20 points. The application does not restrict teams from over or undercommitting on story points. The sprint planning board provides a gauge that compares the capacity of the group to the total story points required for the sprint.