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
  • Show capacity
  • Update Capacity
  • Update Load
  • Estimation models
  • Epic level estimations are excluded
  1. Program Increment (PI) planning

Capacity

PreviousPI ObjectivesNextTeam breakout

Last updated 11 months ago

Show capacity

To display capacity, click on View Options > Capacity

The current load (left) and capacity (right) figures are shown on top of each sprint.

Update Capacity

The capacity (right figure) represent the velocity of a team. Click on the capacity number (the right one) and enter a new value.

You can define a different capacity for each sprint. You ca&n hence account for longer sprints, ramp-up and ramp-downs, empty sprints (e.g. last sprint in a PI to prepare the next PI).

Update Load

The load is automatically computed based on the issues (stories) present in the sprint. To update the load, simply replan the stories or change the estimation (click on "expand" button on an issue and then update the estimation.)

Estimation models

The following estimation models are supported:

  • Story Points

  • Man Days

  • No estimations (simply count the number of tickets)

The estimation model can be changes per team: in Atiov Programs > Settings > Teams > Estimation.

When using Man Days, you can choose to use " original estimations" or "remaining work". Click on the load button to make a selection.

Epic level estimations are excluded

To avoid double counting, Ativo will ignore the estimations at epic level for the sprint capacity load.

Epic-level estimations are meant to be delivered over a longer term period, and are not attributed to a single sprint.

The sprint load represents the sum of story-level estimations in that sprint.