Managing Releases#
In Allegra, the term “release” is used more comprehensively than usual. Releases allow for a temporal structuring of projects and can themselves be subdivided. In Allegra, releases refer to
real releases, i.e., versions of a product
Sprints, which divide a project or release into several iterations
Backlogs, which serve as containers for not yet planned items
Real releases are optional in the Scrum workflow. In Allegra, you can define releases, which in turn contain sprints and a release backlog.
Adding Releases#
To add releases, backlogs or sprints to a Scrum project, select the desired project in the Scrum app first. Then go to the main menu item “Releases”.
Now add a real release, a backlog or sprints as needed. You can also create sprints and backlogs as sub-releases of real releases, e.g., for a release backlog.
Sprint Auto-Generator#
Sprints are planned in Scrum as iterations with a fixed duration. The duration of a sprint is typically 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 will be generated directly in the project. Otherwise, the Sprint Auto-Generator will create the sprints within the active releases.
Attention
The creation of the sprints by the auto-generator may occur with a few minutes delay as it happens in the background.
Scrum Settings#
For each project, you can set
The attribute used for Story Points
The attribute used for Business Value
The attribute used for Backlog Priority
The Sprint Capacity in Story Points
Usually, these settings are defined once per project. If necessary, the sprint capacity can be overridden individually for each sprint.