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
  • Display PI Objectives
  • Update PI Objectives
  • Predictability measure
  • Map PI Objectives to Epics
  • Export
  1. Program Increment (PI) planning

PI Objectives

PreviousRaise risks and impedimentsNextCapacity

Last updated 10 months ago

Display PI Objectives

To display PI Objectives, click on View Options > Objectives

PI Program level objectives are shown on top of the page. PI Team level objectives are shown in each team plan section

Update PI Objectives

Click on the Update program objectives or Update team objectives links to open the edit objectives modal. Drag & drop objectives in the preferred order.

Use the update objectives form to add, update or delete PI objectives. Click on Submit to confirm the modifications.

Predictability measure

The Predictability Measure indicates how predictable (reliable) the planning is. This metric is computed as 'Total delivered value' divided by 'Committed planned value'. A figure between 80% and 100% typically means the planning is considered to be predictable.

The planned business value is an appreciation by the business owners on the business value of the objective. This figure is estimated during the PI planning session (so before any delivery is done). The figure is typically expressed between 1 (very low business value) and 10 (very high business value)

The delivered business value is an appreciation by the business owner on the effectively delivered business value. This figure is typically provided at the end of the last sprint of the PI, during the system demo.

The predictability measure is show when the planned value and delivered value are filled in.

Map PI Objectives to Epics

Enable PI objective mapping

Ativo Programs for Jira Admins can enable the epic (feature) mapping functionality by clicking on Update objectives > Settings > Map PI Objectives to epics (features) for this PI. This will enable the mapping for PI objectives at program and team level for this PI.

Map epics

Once enabled, use the Update program objectives or Update team objectives form to add or remove epics (features) per objective.

See progress

Progress of a PI Objective is computed based on the progress of the mapped epics and underlying stories. The metrics take all issues in on the program board (PI) into account (so from all teams, not only from the team owning the objective). Issues outside the program board (PI) are not considered.

See progress details

Click on the expand or expand all buttons to see the progress details per objective.

Export

This functionality is currently released as BETA functionality. Please report .

.

feedback to our support team
Export the PI objectives to Excel (CSV format)