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.
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.
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.
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.
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.
You can analyze the quality of your release by checking the latest test run results:
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.|
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.
Mark, a product manger, is responsible for the development of a basic mobile chat application. As his development team works, he needs to check and see that the development work is of a high enough quality to release.
Therefore, in the Dashboard module, he adds a number of widgets designed to show his release's quality:
Feature Quality Status
This enables him to see overall quality by comparing the total number of test runs and the status of each.
Open defects by severity
This enables him to see the outstanding problems in the application with the number of defects for the selected release.
Quality by application module
This graph enables his to see that each area of the application being developed is or is not of a certain level of quality.
In addition, there are numerous other charts and graphs available in the Quality section of the Widget Gallery, but these charts gave Mark the picture he needed.