Manage releases

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.