Users with ‘Manage Programs’ permission can create a new Program from the Programs List screen.


To create a new Program:

  1. Name your Program

  2. Add Objectives & Roles (non mandatory): What are the main Program Objectives you want to communicate to your teams? Who are the main points of contact for the Program who can help to answer any questions? Are there any links to Confluence that would be helpful to include?

  3. Team Boards: From the Team Boards dropdown, search for the names of the teams you would like to include in your Program 

  4. Program Roadmap: Select which issue type/s you would like to schedule on your Program Roadmap and where the issues for your Program Roadmap live.

  5. Nominate the dependency link type you want to be visualised on your Program: Click ‘Show Advanced’ to display the Dependency Link Type field. By default, it is set to ‘blocks / is blocked by’, use the dropdown if you wish to visualise a different link type on your Program Board.


Editing your Program

Users with ‘Manage Programs’ permission can edit their Program from the Program Roadmap.

From this screen you can:

  • Edit the Program Name

  • Add or delete teams from the Program

  • Change the dependency link type visualised on the Program

Deleting your Program

Users with ‘Manage Programs’ permission can delete a Program from the Programs List screen.


FAQs

What board types can be added to my Program?

Scrum, Kanban, multi-project and Team-Managed (Cloud) boards can all be added to your Program.

Team-Managed boards can be added to a new or existing program although some of the functionality is limited depending on your Program’s configuration. 

Please read our documentation on team-managed boards for more information.

Can I add a team to multiple Programs?

Boards can only be added to one Program. If you’d like to be able to add a team’s board to multiple Programs please vote for the issue on our public roadmap.

Current workaround - Create a new board with the same board filter so you can visualise the work of a shared services team across multiple Programs.

What is the ‘Program Roadmap’ and which configuration option is best for my organisation?

The Program Roadmap visualises the features (Jira epics) that are planned within an Increment. Product Managers/Release Train Engineers can schedule issues onto the Increment Roadmap to communicate the focus for the Program Increment. 

Easy Agile Programs supports either sourcing features/Jira epics from the 'team' agile boards that have been added to the Program, or using a dedicated 'Roadmap' agile board.

There are three configuration options for the ‘Program Roadmap’:

A) I want to schedule epics from the selected Team agile boards onto my Program Roadmap

Select Option A if you only want to schedule Epics onto your Program Roadmap and the Epics you want to schedule live in the Team Boards you have included as part of your Program.

This option is best for teams that manage their own backlog of features.

B) I want to schedule epics from a dedicated agile board onto my Program Roadmap

Select Option B if you only want to schedule Epics onto your Program Roadmap and the Epics you want to schedule live in a dedicated board.

Use the 'Roadmap Board' dropdown to select the board where the Epics you want to schedule live.

This option is best for agile release trains that have a centrally managed backlog of features.

(info) When using this option, you will have the added benefit of Quick Filters on the Increment Roadmap and Team Planning Board.

C) I want to schedule other issue types from a dedicated agile board onto my Program Roadmap

Select Option C if you want to schedule ANY Issue Type onto your Program Roadmap and the Issues you want to schedule live in a dedicated board.   

From the 'Roadmap Board' dropdown, select the board where the issues you want to schedule live.

Select the Jira Issue Link Type from the dropdown to determine how the issues scheduled in Sprints by the teams are linked to the issues scheduled on the Program Roadmap.

This option is best for agile release trains that have a centrally managed backlog of features and have introduced a new level of hierarchy between the Jira Epic and the user story level i.e. ‘Feature’ to align with the SAFe framework.

(info) When using this option, you will have the added benefit of Quick Filters on the Increment Roadmap and Team Planning Board.

What is a ‘Team Agile Board’?

Programs is built around Agile Boards. Jira Software has both projects and agile boards. We decided to base Easy Agile Programs on agile boards as they provide a lot of flexibility around how they're configured.

An agile board determines which issues should be displayed based on the Jira saved filter, which can be as simple as all issues from a project, or a complex nested JQL query.

Search by the agile board name to location the team and add them to your Program.

Team Board Configuration

First up we'll need to create a Scrum board for each team. The filter used for the team boards will determine the issues that a given team will work with in their backlog. When creating a program in Easy Agile Programs using Epics you have two options:

Program only includes Epics from Team agile board

In this configuration each team will only see Epics from their own project in the Jira Backlog. The shared Project Epics will still be visible and linkable within Easy Agile Programs but won't be visible within the standard Jira Backlog.

This configuration is ideal when your shared Epic project has a large number of Epics that you may not want to include in every Team Backlog.

For this configuration the default board filter generated for a new Scrum Board is perfect. If you've created Scrum boards with your team projects there's nothing else to do here!

PROJECT = TEAMA ORDER BY RANK
CODE

Program includes Epics from the Team and Roadmap agile boards

In this configuration each Teams backlog will include their own Epics, and Epics from the shared SPACE project. 

For this configuration we need to set the board filter for each Team to include every issue from their Team Project and any Epics from the shared project

If you've created your Team Projects with the default Scrum boards you'll need to update each filter as follows substituting TEAMA for each Team.

PROJECT = TEAMA OR (PROJECT = SPACE AND TYPE = Epic) ORDER BY RANK
CODE

Roadmap Board Configuration

For the Roadmap board we're going to include Epics from all the Team boards (Team A, Team B and Team C) and Epics from the shared project (Space Exploration). We recommend a Kanban board for your Roadmap. You may also wish to review Understanding the cycle time of Epics in Jira. The board filter for your Program Roadmap Board should look like this:

PROJECT IN (TEAMA, TEAMB, TEAMC, SPACE) AND TYPE = Epic ORDER BY RANK
CODE

Alternatively you could assign each Project to a Project category to simplify the JQL. If every Project was included in a category called "Space Program" your Roadmap filter could be:

"Project Category" = "Space Program" AND TYPE = Epic ORDER BY RANK
CODE