Skip to main content

Interpreting the Delivery at a Glance Board

This article explains how to interpret the Delivery at a Glance board in Agility.

Overview

Learn how to interpret the elements displayed on the Delivery at a Glance ( DAAG) board.

A valid Digital.ai Continuum instance is required in order to use Delivery at a Glance.

Elements

The board is comprised of the following elements:

ElementsDescription
Phase
A phase represents a particular location in your delivery pipeline. The heading displays the phase name ("Test" in this example) and the total number of unique work items contained in this phase. If the same workitem is contained in two separate packages in the same phase, this total will only count the work item once.
Package

A package is the container of workitems presented in each phase. It is comprised of workitems and commits. Its heading contains its name, last updated date & time, as well as total number of workitems.
Undeliverable Work Item
The light shaded square represents an "undeliverable" work item. This means that the workitem's status belongs to a "not started" or "in progress" reporting category.
Undeliverable Work Item with Trailing Commits
The light shaded square split with a diagonal line represents an "undeliverable" workitem which contains trailing commits. This means there are additional commits for this workitem in a package located in an earlier phase that are not contained in the package you are currently viewing. Effectively all the work that has been committed against this item is not in the current package and thus is not deliverable.
Deliverable Work Item
The dark shaded square represents a "deliverable" workitem. This means the workitem's status belongs to a "completed" reporting category and all the commits for the workitem are found in this phase or package. This means no newer commits are in any of the preceding phases and thus the workitem can be delivered.
Rogue Commits
The orange box located at the top right of a package represents the number of rogue commits contained in the package. These are commits that were not associated with any particular workitem and thus are rogue. This generally happens when a commit is not tagged with the workitem ID the work was intended for (for instance, S-12345) or because the story branch where the commit is located does not contain the correct workitem ID.