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
  1. Getting started

Prerequisites

Validate if the following prerequisites are met before installing and configuring Ativo Programs

  • Use Jira Cloud, Jira Server (> 7.8.0) or Jira Data Center (> 7.8.0).

  • Use a two layer deliverables structure composed of epics (called “features” in the application), and underlying tickets (stories, spikes, bugs, tasks …). Sub-tasks and sub-bugs can also be used by teams, but will not be visible on the program planning board.

  • When using the Jira Cloud platform: we only support ‘company-managed’ (‘Classic’) Jira projects. The ‘team-managed’ (‘next-gen’) are not supported, as they don’t support the necessary functionality to collaborate between teams. (more info)

  • Work iteratively in periods (called “Program Increments” or “PI” in SAFeÂŽ terminology) at program level. (more info)

  • Teams can work using a Scrum or Kanban methodology.

  • Teams can use Story Points or Man Days for their estimations, or use no estimations at all.

  • The application is displayed in English only (contact support for upcoming language support).

PreviousQuickstart guideNextInstallation

Last updated 2 years ago