Glossary of backlog entities

You use many types of items in the Backlog module.

Backlog root

The backlog root is the highest-level point of the backlog. It is not associated with a specific epic or feature, but serves as the container for all backlog items.

In the Backlog tree in the Backlog module, the root is the highest level in the hierarchy.

Back to top

Epics

Epics are the product's high-level functional areas. These areas are top-level objectives of your product development.

You define epics under the root of the backlog tree.

Epics are release-agnostic.

Back to top

Features

Features are a useable part of an application.

ALM Octane supports two types of features:

  • Business features for customer facing changes.

  • Architecture features for changes required in your system

Define features under an epic or under the root of the backlog tree.

You can assign features to releases.

Back to top

Backlog Items

Backlog Items is a collective term that includes User Stories, Quality Stories, and Defects.

Back to top

User stories and quality stories

In features, add user stories and quality stories. These user stories are a specific functionality (either customer-facing or internal).

  • A user story describes a customer-facing functionality or an action a user performs.

  • A quality story describes internal work for developers or testing engineers to do. These items do not affect the product's customer-facing functionality.

User stories and quality stories are always associated with a feature, even if you do not assign one.

Note: You view user stories and quality stories in the Backlog Items tab of the Backlog module.

However, user stories, defects, and quality stories are described collectively as Stories. When you configure ALM Octane dashboard graphs to show data from Stories, the graph includes details for user stories, quality stories, and defects.

Back to top

Defects

Defects are the faults or bugs detected in the product.

View defects in the Backlog Items tab of the Backlog module. If you prefer to view defects separately, use the Defects module.

Note: However, user stories, defects, and quality stories are described collectively as Stories. When you configure ALM Octane dashboard graphs to show data from Stories, the graph includes details for user stories, quality stories, and defects.

Back to top

Tasks

It is possible to divide a user story, quality story, into tasks. Use tasks to describe the steps necessary to complete the user story or defect.

View tasks in the Tasks tab of a user story or the Tasks tab of the Team Backlog module.

Back to top

Tests

Add tests to all types of backlog items check their quality.

ALM Octane lets you add manual or automated tests to any backlog item. ALM Octane aggregates test results to provide quality analysis of the associated backlog items.

View testsin the Tests tab of the Backlog module or the Tests tab of a selected item.

Back to top

See also: