Create a release in Agile Development 2.0

---
title: Create a release in Agile Development 2.0
description: Create a release to start associating the stories and scrum tasks of your product development to the release in Agile Development 2.0.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/it-business-management/agile-development/create-a-release.html
release: australia
product: Agile Development
classification: agile-development
topic_type: task
last_updated: "2026-11-06"
reading_time_minutes: 2
breadcrumb: [Managing your product development using Agile Development 2.0, Agile Development 2.0, Agile Development, Strategic Portfolio Management]
---

# Create a release in Agile Development 2.0

Create a release to start associating the stories and scrum tasks of your product development to the release in Agile Development 2.0.

## Before you begin

Role required: scrum\_release\_planner, scrum\_admin

## About this task

Use the Releases module to create a release record to start planning for your upcoming release.

A release has a start and end date during which several development iterations are completed. Releases are created by a product owner and contain user stories, sometimes from multiple products, and can also involve multiple teams. The stories associated to a release form its release backlog.

## Procedure

1.  Navigate to **All** > **Agile Development** > **Releases**.

2.  Select **New** in the record list.

    Alternatively, if you already created Product records in Agile Development 2.0, you can use the Releases related list to open the new release form.

3.  On the form, fill in the fields.

<table id="table_release_form"><thead><tr><th>

Field

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Number

</td><td>

System-generated unique number for the release.

</td></tr><tr><td>

State

</td><td>

Current state of the release. The default is **Draft**.

</td></tr><tr><td>

Total committed points

</td><td>

Sum of all story points from the stories associated with this release.

</td></tr><tr><td>

Release capacity

</td><td>

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** fields are populated for the groups in the **Groups** related list in the release record.

</td></tr><tr><td>

Planned start date

</td><td>

Estimated start date of the release.

</td></tr><tr><td>

Planned end date

</td><td>

Estimated end date for the release.

</td></tr><tr><td>

Assigned to

</td><td>

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

</td></tr><tr><td>

Short Description

</td><td>

Brief description of the release.

</td></tr><tr><td>

Description

</td><td>

Detailed description of the release.

</td></tr><tr><td>

Work notes

</td><td>

Updates about the work being performed on the release. This field is updated by the **Assigned to** user as the work progresses on the release.

</td></tr></tbody>
</table>4.  Select **Submit**.


## What to do next

Start planning your release by associating products, stories, and the assignment groups to this release record. Use the related lists available in the release record for these actions.

For information on the related lists of a release, see [Related lists for a Release in Agile Development 2.0](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-business-management/agile-development/related-links-lists-for-release-agile-development-2.md)

**Parent Topic:**[Managing your product development using Agile Development 2.0](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-business-management/agile-development/using-agile-development-2-0.md)