Managing Releases and Sprints
Releases are represented by top level configuration items in Release type CMDB categories in Codebeamer. Sprints are simply child items of releases. Essentially, this hierarchy represents the one release is split into multiple sprints relationship.
You can create, update and delete releases and sprints as written in Release Management with Codebeamer
Managing and ranking backlogs
The term backlog was first introduced by Scrum, where it was described as a product backlog. In this enterprise model, product can be a pretty nebulous thing, because various teams may be working at various levels, so there are multiple types backlogs in the big picture. Therefore, the use of the term backlog is more generalized here.
The backlog is the one and only definitive source of work for the team. It holds all the work that needs to be done, like a todo list. It contains user stories, but also other issue types like a bug that needs to be fixed, a task or a change request that needs to be done, or a manual test that needs to be executed. The backlog is managed by the team.
There are three kinds of backlogs exist, each with a different scope:
1. Sprint backlog: The work to be done in a specific sprint.
2. Release backlog:: The work to be done in a specific release (which typically consist of multiple sprints).
3. Product backlog:: The work to be done on the product at some point, maintained and managed collaboratively by the team.
Backlogs are ordered by relative order in which the user stories should be done. The order is typically specified by many factors, like business value, the penalty for not doing that story, risk, cost and so. (These are not discussed here.)
Setting the relative order within a backlog is called ranking or prioritizing the backlog.
Learn more about the (somewhat limited-scope) product backlog in Wikipedia
Managing the product backlog
The product backlog is the list of issues that have no target release set. There is no special page in Codebeamer to manage this list, but you can add the issues to releases on the browse tracker pages. You can use Mass edit to change the release field of multiple issues at the same time.
Managing the release backlog
Release backlog is the prioritized list of issues in a specific release. You can access it by clicking on a release link in a release category.
By default, the issues in the backlog are ordered by priority descending (with the exception that closed and resolved issues are always at the end of the list) but you can change this order on the release planner
Managing the sprint backlog
The sprint backlog is the prioritized list of issues in a sprint. You can manage this list exactly like for any other release (described in the previous section).
To create a sprint click the New Sprint item in the menu of a release. In Codebeamer all releases that are not on the top level are sprints. To move issues to the sprint backlog you can use the issue editor page or mass edit (to move multiple issues at once).