Ativo Programs for Jira 📖 Documentation
  • Getting started
    • Quickstart guide
    • Prerequisites
    • Installation
      • Updates
    • Cheat sheet
  • Configuration
    • Permissions
    • Team
    • Program (release train)
    • Period (program increment)
    • Project and Jira (JQL) filters
  • Preparing a Program Increment (PI)
    • Program cycle
    • Feature backlog
  • Program Increment (PI) planning
    • Plan issues
    • Plan epics (features)
    • Plan dependencies
    • Raise risks and impediments
    • PI Objectives
    • Capacity
    • Team breakout
  • Scrum of scrums / Art Sync
    • Scrum of scrums and art-sync preparation
    • Progress per team
    • Progress per program
  • Cross-pi
    • Cross-PI dependencies
  • Advanced
    • Export issues, PI objectives, milestones and capacity to Excel
    • Ativo Programs custom fields
      • Field sharing
      • Ativo Program fields use PI keys since April 2023
    • Fields added to screens
    • Issue types
    • Limit permissions of suppliers
    • Jira Service Management tickets on the program board
    • Server to cloud migration
  • REST API
    • Authentication
    • Version
    • Cloud REST API Rate Limiting
    • Cloud REST API
    • Data Center REST API
  • Training
    • User training
Powered by GitBook
On this page
  • What is a cross-team dependency?
  • See cross-team dependencies
  • Dependency cords colors
  • Add, update or remove (cross-team) dependencies
  • Hide or filter dependency cords
  1. Program Increment (PI) planning

Plan dependencies

PreviousPlan epics (features)NextRaise risks and impediments

Last updated 2 years ago

What is a cross-team dependency?

A cross-team dependency is a story in one team that is either:

  • part of a feature that is owned by another team

  • linked as “blocked by” or “blocking” with a story of another team in the program

See cross-team dependencies

The program plan (PI planning) view shows cross team dependencies with cords:

Dependency cords colors

Dependencies have three possible cord colors:

  • Purple : the dependency is planned "in order".

  • Amber : the dependency is planned between two issues in the same sprint. This could be a risk.

  • Red: the dependency is planned "out of order". This means the prerequisite is planned in a later sprint, or the prerequisite is stil in the backlog.

Add, update or remove (cross-team) dependencies

To plan or update a (cross-team) dependency :

  • Select the issue (story)

  • Click on the expand button

  • Click on Dependencies

  • Add / remove prerequisite dependencies (left side), or outgoing dependencies (right side).

Ativo Programs by default displays 'blocking/is blocked' and 'child/parent' dependencies on the board. jira admins can change the dependencies via Jira settings > Ativo Programs > Issue link.

Hide or filter dependency cords

Click on View options > Cords to select the cords you'd like to see. E.g. one can choose to hide all cords.

Select the Advanced view options to select the cords you'd like to see more precisely.