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

Release management

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

Release management

Releases contain user stories, sometimes from multiple products or projects, that form the release backlog. A product owner creates the releases.

A release is bounded by start and end times and is used to organize the effort of the assigned groups working on user stories. A release can use multiple assignment groups.

Typically, the product owners select the prioritized stories from the backlog to be completed in a given release. The set of stories in a release are referred as release backlog.

Agile Development 2.0 allows the release backlog to be executed in two ways:
  • Project-based execution - Allows release backlog to be executed as one or more projects.
  • Non project-based execution - Allows release backlog to be executed by one or more assignment groups using their sprint schedules within a release.

Create a release

Create a release, and then select the prioritized stories to be completed in that release.

Before you begin

Role required: scrum_release_planner, scrum_admin

About this task

Before attempting to create a release, make sure that you have created the appropriate stories and scrum tasks and associated them with one or more products.


  1. Create a release using one of these methods:
    From a product record Select the Releases related list and click New.
    From the Releases list
    1. Navigate to Agile Development > Releases.
    2. Click New in the record list.
  2. Fill in the fields, as appropriate.
    Table 1. Release form fields
    Field Description
    Number A system generated number for the release.
    State Current state of the release. The default is Draft.
    Total committed points Displays the sum of all story points from the stories assigned to the release.
    Release capacity Sum of group capacity of all the assignment groups associated with the release.

    Group capacity of an assignment group for a release is calculated as: Group capacity * Number of sprints in the release for that group

    Release capacity is updated only when the Start sprint and End sprint are populated for the groups in the Groups related list in the release record.

    Planned start date The estimated date for the release to start.
    Planned end date The estimated date for the release to end.
    Assigned to The scrum user assigned to the release.

    It must be a scrum user, such as a release planner or product owner, whose role allows rights to create and edit releases.

    Short Description A brief description of the release.
    Description A detailed description of the release.
    Work notes Notes about the work being performed on the release.
  3. Click Submit.

What to do next

After a release record is created, perform release planning by selecting a product and moving stories from a product backlog to a release backlog. You can add products, stories, or groups using the following related lists.