Analyze release progress and quality

In the Backlog module, you can use the predefined charts and widgets to assess and analyze your release progress and overall quality.

Select an image to navigate directly to the topic about this phase and learn more.

Track release progress

ALM Octane uses phases to represent the status of an item. In the Settings area, workspace admins customize the workflow phases defined for each entity type. This workflow defines the order of phases each type of item must go through.

As items are designed and developed, you can advance their progress from phase to phase with a click of a button.

Track the development progress in a number of places:

  • At the top of the Backlog module, view the release timeline.

  • View the Phase column in the Backlog Grid view

  • View the Progress column in the epic, feature, and story Grid View. Hover over the progress bar to see more detail. The tooltip that opens lists the number of features, user stories, defects, story points, and or hours, as relevant.

    Note: Filtering the grid does not affect the progress bar.

    For epics and features, progress is measured in story points.

  • View the progress widget in the planning buckets.

  • Use chart and graph widgets in the Backlog Overview tab. Select a node in the backlog tree to filter the data. These widgets are context-sensitive and they display only data relevant to the selected node.

  • View widgets in the Dashboard module. Select from the predefined widgets offered by ALM Octane, or create your own. Configure the widgets to filter the data according to your needs. For details, see Use the ALM Octane Dashboard.

Back to top

Viewing progress columns

Progress is measured differently for epics and features vs. stories.

Epics and Features

Progress is measured in story points.

The green section of the graph indicates the amount of story points marked as Done. An item is considered Done if it is set to a phase that is included in the Done metaphase. The blue indicates remaining work. The amount of story points in items that are not Done.

Example:  

By default, the Rejected phase for defects is included in the Done metaphase. The In Testing phase for user stories in included in the In Testing metaphase.

In the progress bar, rejected defects are counted as Done, in-testing user stories are counted as remaining work.

  • The story points are collected from all of the user stories and defects defined under the epic or feature.

  • A feature's progress bar also displays the amount of work that was estimated for the feature itself. A gray bar indicates the number of story points defined in the feature, in comparison to the amount of story points aggregated from its stories.

Stories

Progress is measured in hours.

The hours are collected from all of the tasks defined in the story.

The green section displays the number of hours already invested. The blue section displays the number of hours remaining. The gray section displays the number of hours estimated for the story.

Back to top

Analyze release quality

You can analyze the quality of your release by checking the latest test run results:

Backlog module

When you view tests, a Last runs widget summarizes the last run status for each test. Hover over the widget to open the detailed run results. In the legend, click the View runs link to view a list of the last runs filtered by the results displayed in the tooltip.

Backlog module, Overview tab View test run results in chart and graph widgets . Select a node in the backlog tree to filter the data.
Dashboard module

Select from the predefined widgets offered by ALM Octane, or create your own. Configure the widgets to filter the data according to your needs. For details, see Use the ALM Octane Dashboard.

Back to top

Next steps: