Release life cycle

The release life cycle in Agile Manager can include the stages described below.

Select a box to jump to more details in the table below.

Note: Some steps can be carried out only by Administrator users.

Configuration (Administrators only)

Define workspace settings

Define the site users assigned to the workspace.
Configure general workspace parameters that apply to all releases.
List the applications being developed in your workspace.
Take advantage of the embedded ALI technology and monitor code development.

Define build servers and source code repositories to enable data synchronization with Agile Manager.

For more details, see Configure workspace settings and Configure ALI integrations.

Where: Configuration > Workspace

Release Planning

Structure the release and define teams (Administrators only)

Create a release, and define the teams and team members that will be active in the release.

For details, see Configure releases.

Where: Configuration > Release

Manage product and release backlog

Define your product themes and features.
Create a product backlog of user stories and associate them with features and themes.
From the product backlog, assign user stories and defects to a release.
When planning a release, pay attention to the release capacity.
The sum of story points you assign to a team should roughly match the release capacity.
The release buckets display the amount of story points assigned compared to the overall release capacity.

Where: Product Backlog

Sprint Planning

Plan user stories and defects

From the release backlog, assign user stories and defects to sprints.

Where: Release Management > Release Backlog / Planning Board

Assign items to teams

From the sprint backlog, assign items to teams.

Where: Release Management > Sprint Backlog

Manage team velocity

When planning a sprint, pay attention to the team velocity.

The sum of story points you assign to a team should roughly match the team's sprint velocity.

The team buckets display the amount of story points assigned compared to the overall team velocity.

Where: Release Management > Sprint Backlog

Sprint Execution

Allocate tasks to team members

For each item in the sprint backlog, define the tasks that are necessary to implement the user story or defect.

The tasks can be allocated to the same member as the backlog item, or to other members.

Where: Release Management > Sprint Backlog / Task Board

Track tasks and WIP

When the sprint begins, use the task board to track the progress of your tasks.

Where: Release Management > Task Board

If you using Kanban methodology, use the storyboard to manage the development life cycle of user stories and defects.

Where: Release Management > Storyboard

Implement and update

Develop your product as planned, and update item statuses as you move them towards completion.

Where: Release Management > Task Board / Storyboard

Log defects at any stage of the product development.

Defects are added to the release or sprint backlog in which you report them, and to the overall product backlog.

Where: Defect Management, Release Management > Release Backlog, Sprint Backlog

Retrospective and close the sprint

Write up a sprint retrospective and create action items.
Inspect the backlog items that were not completed in the sprint.
Carry over open backlog items to future sprints.

Where: Release Management > Sprint Closure

Visibility and Insight

Development analytics

Use ALI analytics to continuously monitor the progress of the release development, builds, and source code changes.

Analyze specific features or themes, or work completed by specific teams.

Where: Release Management > ALI Summary; Builds; Source Code

Kanban / Scrum reports and other customizable reports

Use predefined or customized dashboards to track applications, releases, sprints and defects.