Backlog entities explained

There are a number of different items to use when building a Backlog.

Note: The backlog, releases, and teams are all structured within individual workspaces, and do not cross workspaces.

Epics

Epics are the product's high-level functional areas. These areas are top-level objectives around which your product development is focused.

Back to top

Features

Features are a useable part or action in an application. Each area of the application (epic) can contain multiple features. For example, you can have different features in a single epic area—buy a song, enter payment details, and so on.

ALM Octane supports two types of features: Business and Architectural:

  • Use a Business feature for customer facing changes.

  • Use an Architectural feature for changes required in your system to support a Business feature.

Back to top

User stories and quality stories

Within each feature, you add user stories and quality stories. These user stories describe a specific functionality (either customer-facing or internal) that the product offers:

  • A user story describes a customer-facing functionality or an action that a user can perform. A user story can be associated with a feature.

  • A quality story describes internal work that needs to be done by your developers or testing engineers, but does not directly affect the product's functionality. A quality story must be associated with a feature.

Note: The user stories, defects, and quality stories that are listed in the backlog are referred to collectively as Stories. When ALM Octane graphs report story data, they include the information for all user stories, quality stories, and defects.

Back to top

Defects

Defects are the faults or bugs detected in the product. Defects are included in the product backlog together with user stories. A defect can be linked to user stories, and can be associated with a feature and with application modules.

Note: The user stories, defects, and quality stories that are listed in the backlog are referred to collectively as Stories. When ALM Octane graphs report story data, they include the information for all user stories, quality stories, and defects.

Back to top

Tasks

Each user story and defect is broken down in to individual tasks. Tasks can be viewed in a tab when you select a user story or in the Team Backlog area in their own separate tab.

Use tasks to describe the steps necessary to implement the user story or defect.

When you create a new task, estimate the number of hours you think the task will require. As you complete the task, report your progress by updating the number of remaining hours in the Task Board. After you mark a task as completed, the task's remaining hours are automatically transferred to the invested hours.

The estimated hours for all tasks in a backlog item are aggregated into the number of planned hours for that item. The invested and remaining hours for all tasks are aggregated into the number of actual hours for that item.

Back to top

Tests

Each backlog item (epics, features, user stories, quality stories, and defects) can be associated with tests to check its quality.

The tests are displayed in the Tests tab of the Backlog module.

Back to top

See also: