Skip to main content
Version: 25.0

Programs

A program is a cross-hierarchical collection of projects used for filtering and reporting purposes. Programs allow you to group a set of projects that do not all roll up together within a single hierarchy. You can use them to represent:

  • Suite Releases that encompass updates for a number of products in a suite
  • A Program Increment across an Agile Release Train when using SAFe®
  • A newly-combined group of projects after a reorganization
  • Teams that support multiple products
  • Any other grouping that your hierarchy structure does not support directly

Users can filter the project selection by program to plan, track or report by these subsets.

When a Project (aka Planning Level) in the Program contains child Projects, those Projects are included in the Program. As an example, consider the following hierarchy

  • Application Suite
    • Product 1
      • Q1 Release
      • Q2 Release
    • Product 2
      • Q1 Release
    • Product 3
      • Q1 Release
      • Q2 Release

A Program that includes Product 1 and Product 2 will also include work from Q1 Release and Q2 Release from Product 1 and from Q1 Release from Product 2.

Accessing Programs

Programs display in the Project Tree and are visible by all system users, but any member who views a program's contents will only be able to see the included projects that they could otherwise access within the system. Note that a program does not increase anyone's access within the system.

  • To access the Project Tree, click on the Project Navigator button in the top left corner of the page. From there, you can select the programs you want to work with.

What is the "System (All Projects)" Project?
The "System (All Projects)" project sits at the top level of the project tree and was automatically created when Digital.ai Agility was set up. We recommend that you create all of your projects or child projects underneath it to retain the flexibility to scale the project tree in the future. To learn more, see Understanding System (All Projects).

Suite Release Example

A program called "Q1 Suite Release" can be created to encompass the work for the upcoming release of three products that make up a suite. Use a program to view the collective progress and status of all the work that is going into the Q1 Release of the Suite.

  • Application Suite
    • Product 1
      • Q1 Release
      • Q2 Release
    • Product 2
      • Q1 Release
    • Product 3
      • Q1 Release
      • Q2 Release

When a user selects the Application Suite and filters by Q1 Suite Release program, the system will include only the items scheduled in the Q1 Release under each of the projects. This is accomplished within the Tree & Filters panel of the Project Navigator. The tree control provides visual indication of exactly which projects will be included.

Reporting

View project or release and sprint metrics to measure your progress towards release.

Managing Budgets

Managing Projects or Releases

Selecting Data Using the Context Navigator

Allocate a Budget to Project Segments

Creating Budget

Deleting Budget

Editing Budget

Interpreting Budget Details and Indicators

Assigning Project Role

Adding or Assigning a Member to a Project

Understanding System (All Projects)

Portfolio Item Overview

Release Scheduling

Release Capacity Planning

Watching Backlog Goal or Objective

Adding Links

Attaching Files

Copying a Work Item

How to Print Story Cards

How do I create a friendly work item link

Working with Communities

Using Conversations

Working with Defects

Using Templates to Create Reusable Portfolio Items, Stories, Backlog Items, or Defects

Using Ideas

Tracking Impediments with Issues

Managing Member Accounts

Managing Projects or Releases

Using Requests to Capture User Feedback and Suggestions

Managing Sprints or Iterations

Sprint or Iteration Scheduling

Using the Portfolio Tree

Managing Stories Backlog Items

Using Tasks to Breakdown Stories Backlog Items

Using the Sidebar

Working with Community Topics