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. Preparing a Program Increment (PI)

Program cycle

PreviousProject and Jira (JQL) filtersNextFeature backlog

Last updated 2 years ago

Agile organizations value individuals and interactions over processes and tools. They prefer responding to change over following a plan. []

So instead of planning the full program ahead in details, we plan a program in cycles of different periods (called ā€œProgram Incrementsā€ in SAFeĀ® ).

Weā€™ll use lean visualization techniques to promote human interaction and to keep the plan thin and on point.

The main steps of the cycle are visualized in Ativo Agile Programs for Jira:

Select or create a program

When you open the application for the first time, you are invited to select an existing program or create a new program.

Select or create a period

Once youā€™ve created the teams and selected a program, you are invited to select a period or create a new period. A period contains a set of sprints.

Prepare and prioritize

Each program has a prioritized backlog of features. The business (Product Manager) defines the priority and selects a shortlist of features for the next period.

A feature is in Jira represented as an epic. The feature list is saved in a Jira project.

Plan and improve

As a next step, teams plan in the features and stories in the sprints of the period. Each feature is owned by a team ā€˜in the leadā€™. This ā€˜team in the leadā€™ coordinates the planning of the stories with other teams.

When a team has a story as part of a feature of another team, this story is a cross-team dependency between both teams.

More information:

Deliver and learn

Teams are responsible for the delivery of the stories and features. The progress is reviewed in the Sprint review and Scrum of scrum / art-sync meetings.

Ativo Agile Programs for Jira provides dashboards to show the issues, risks, dependencies, progress and metrics per team and per program.

More information:

A program is created by an Ativo Agile Programs for Jira Admin. Refer to the for more information on how to appoint an administrator. Refer to the and for more information on the configuration of teams and programs.

A period is created by an Ativo Agile Programs for Jira Admin. Refer to the for more information on the creation of a period.

security configuration documentation
team configuration
program configuration documentation
period configuration documentation
Plan stories
Plan features
Plan cross-team dependencies
Plan issues and risks
Team progress
Program progress
agile manifesto
Example of a program cycle visualization in Ativo Agile Program for Jira.