Overview of Release with Delivery Insights

Digital.ai Release with Delivery Insights is a powerful tool that combines Agile and DevOps practices to improve software development. It enhances visibility and collaboration in software development by seamlessly connecting data at each release stage to related agile stories and features. This enables the entire organization to track progress end-to-end with a single, user-friendly tool.

Here's a simplified breakdown of its key features:

• Digital.ai Release: This is your release orchestrator. It focuses on managing the workflow and processes involved in software development.
• Delivery Insights: This component is all about tracking the actual content of your development process. It keeps an eye on work items, code commits, packages, versions, and their progress through the development pipeline.
• Integration: By linking these two together, Release can provide valuable insights into how your software is moving through the development pipeline. This integration enables you to see the bigger picture of your software development process.
• Release with Delivery Insights: This is the bundled solution that offers both Release and Delivery Insights. While Release is the user-friendly face of the product that your team interacts with, Delivery Insights operates in the background, doing the behind-the-scenes tracking and monitoring.

Digital.ai Release with Delivery Insights is a tool that combines the best of both worlds: process management with Release and content tracking with Delivery Insights. It helps your organization keep a close eye on the entire software development journey.

Progression and Progression Board

• Progression: A progression in Release with Delivery Insights is a structured path that package versions follow as they go through various stages before reaching the end users.
• Package Version: Each update is called a package version. It's like a package containing improvements and fixes for your software.
• Package Revision: Inside each package version, there can be multiple revisions. These revisions are individual updates of the version, and they are linked to specific work items (like stories or bug fixes) and the changes made (known as commits). The creation of revisions should be clearly and consistently defined in your workflow so that they always represent the same set of actions.
• Progression Board: A progression board helps you oversee all the package versions, their revisions, associated work items, and changes. You can use this board to move package revisions from one phase to another, ensuring they're on track for delivery to users.

How to Read the Progression Board?

• A progression board consists of software delivery phases and package version cards.

• Each phase in the progression board represents a discrete step in your software delivery process through which the work items are moved as your software gets closer to delivery.

• A card represents a version of a given application, and contains one or more revision. These cards also provide a visual representation of the work tied to the revisions. In the bottom right, you'll see a range of revisions, and in the top left you will see a range of Aliases.

• Aliases are defined by the user to quickly identify a revision.

• Work items in a package revision card are shown as color-coded dots to visually distinguish stories (Green), defects (Red), and work items with trailing commits (diametrical split).

• The progression board can track multiple applications at once.

• Each application has its own space on the board, with all of its cards in the same horizontal division.

  • Aliases: Range of minor version numbers included in this package revision.
  • Package Version Number: Package major version number.
  • Revision Range: Range of package revisions included in package revision.
  • Total Number of Workitems: Total number of stories and defects included in this package revision.

• Hovering over a dot shows the work item ID.

• Clicking a work item dot shows the Work Item Details pane.

• The following types of units are shown on the board:

  • A green dot represents a Story work item.

    

  • A Red dot represents a Defect work item.

    

  • The half-green dot represents a Undeliverable work item. This work item has some commits left behind in an earlier phase, not included in the current package revision. So, all the work done for this item isn't in the current card and can't be delivered right now.