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
  • Plan features
  • Add details
  • Swimlanes
  1. Program Increment (PI) planning

Plan epics (features)

PreviousPlan issuesNextPlan dependencies

Last updated 2 months ago

Plan features

To plan a feature in a sprint:

  • Select the period in the period picker (top left)

  • Click on Feature Plan

  • Search on the name of the feature in the unassigned column.

  • Drag and drop the feature from unassigned to the desired sprint

Add details

The story points of a feature are defined by the number of story-points of the underlying stories (excluding dependency stories from other teams – those are kept separately). If needed, one can also directly define the story points at feature level. This can be useful in case underlying stories are not yet created in Jira, but we already want to highlight the story points at feature level.

The RAG (Red, Amber, Green) indicator visually represents the health status of the feature. The color codes typically mean the following:

  • Green means the issue is on track.

  • Amber means a serious risk or issue occurs but mitigation is still possible.

  • Red means a major risk or issue occurs and attention from management and peers is needed.

Issues and risks can be added the RAG comment field.

To add details to a feature:

  • Click on the details toggle in the top navigation bar

  • Update the field.

Swimlanes

Click View Options > Epic Swimlanes to view work items grouped by epic in a swimlane. Work items without parent epics or with parent epics outside of the PI are grouped in a separate β€œother” swimlane. The Epic Swimlanes view is available on both the Plan and Team Breakout pages.