Managing releases

Managing releases#

In Allegra, the term “release” is used more broadly than usual. Releases allow projects to be structured over time and can themselves be subdivided further. In Allegra, releases denote

  • actual releases, that is, for example, versions of a product

  • sprints, which split a project or release into several iterations

  • backlogs, which serve as containers for items that have not yet been planned

Actual releases are optional in the Scrum workflow. In Allegra you can define releases that in turn contain sprints and a release backlog.

Adding releases#

To add releases, backlogs or sprints to a Scrum project, first select the desired project in the Scrum app. Then go to the main menu item “Releases”.

Now add an actual release, a backlog or sprints as needed. You can also create sprints and backlogs as sub-releases of actual releases, for example as a release backlog.

Shared releases#

By default, releases always belong to exactly one workspace. As a result, items (tasks, bugs, user stories and so on) also always belong to exactly one workspace. Sometimes, however, it is necessary to make an item accessible in several workspaces, for example to assign items from customer-specific sub-projects to an overarching product release.

You can enable this functionality by marking the releases of a higher-level workspace as “shared”.

Sprint auto-generator#

In Scrum, sprints are planned as iterations with a fixed duration. A sprint typically lasts one to two weeks. To simplify the creation of sprints, you can use the sprint auto-generator for each project and each release.

If the project has no active releases, the sprints are generated directly in the project. Otherwise, the sprint auto-generator creates the sprints within the active releases.

Attention

The creation of sprints by the auto-generator may occur with a delay of a few minutes, as it happens in the background.

Scrum settings#

The following can be configured for each project:

  • The attribute used for story points

  • The attribute used for the business value

  • The attribute used for the backlog priority

  • The sprint capacity in story points

Usually you define these settings once per project. If required, the sprint capacity can be overridden individually for each sprint.

Contents