Backlog management and release quality

The Backlog and Team Backlog modules enable you to manage the items you need for product development, prioritize these items, and plan development cycles.

What is the ALM Octane Backlog?

The backlog is a list of items to handle during product development. In ALM Octane, the backlog is managed in the Backlog module. The Backlog module contains all the product's epics, features, user stories, quality stories, and defects and their tests.

The Backlog module contains:

  • The tree containing the hierarchy of epics and features, regardless of release:

  • A grid containing separate tabs for epics, features, Backlog Items (user stories, quality stories, and defects), and tests. The items displayed in the grid are dependent on the item selected in the tree, and selected releases and sprints, or any additional filters:

The Backlog module enables you to:

  • Create epics and features, user stories, or quality stories

  • Open defects for problems encountered during development, testing, or application deployment

  • Rank items and plan development cycles

  • Add tests to epics, features, user and quality stories, or defects

  • Track release and sprint development progress

Back to top

The ALM Octane Backlog cycle

As you work in the Backlog in ALM Octane, follow these work phases:

Build the product backlog

Add epics, features, user stories, quality stories, defects, and tests - regardless of when you plan to develop or release them. After adding the list (a continual process), rank them.

Plan a release

Assign features, user stories, quality stories, and defects to specific releases. Then, assign them to a development cycle and a team.

Manage the team backlog

When items are assigned to teams, designate specific team members to perform the work. While the team works, track progress of the team.

Work on your stories

Once a story has been assigned to you, mark the progress of the stories and add tasks.

Create and run tests

After (or in parallel with) working on your stories, add tests to ensure that your improvements work properly in your application's build.

Analyze quality

In parallel with development work, view the progress and quality of your development by adding tests to epics, features, user stories, quality stories, and then using the graphs and widgets available in the Overview tab.

Assign items to application modules

Assign user stories, quality stories, and defects to application modules, enabling you to assess application quality regardless of release or sprint.

Back to top

See also: