Capture program increments (PIs)

A program increment (PI) is a timebox during which an agile release train (ART) delivers incremental value in the form of working, tested software and systems. Features are delivered in the context of a program increment.

In the navigation panel, go to Agile Architecture > Agile Release Trains and click the root node of the Agile Release Trains explorer. Go to Overview > Program Increments.​ Per default, the data workbench displays only a set of basic attributes. You can add more columns to capture other attributes directly in the data workbench or you can navigate to a program increment's content area and define it in more detail there. Click to learn about how to use data workbenches.

• Add a new program increment. Click   > Create Program Increment to open the edit panel and specify the basic data.
• Define the details of the program increment. Click the Navigate   button next to a program increment to open its content area. Specify the program increment's attributes as well as the relationships that it has to other assets in the repository.

Define the program increment's basic data. All mandatory fields must be defined to create the program increment and save it.

• Name: (Mandatory) Enter a unique name for the program increment. The name should help others easily understand the program increment.
• Start Date and End Date: The planned start and end dates capture the period when the program increment is actively being executed in the company. This is the period from when the program increment is first initiated to when it shall be completed. Click the calendar icon to select the date or enter the date in the date format Month/Day/Year. For example: 4/30/2023
• Status: This indicates the current status of the program increment from initiation to execution. Possible values are:
  • In Design: The program increment is being scoped and defined.
  • In Realization: The program increment is active.
  • Done: The program increment is finished with its delivery.
• Iterations: The iterations that belong to the program increment.
• Authorized Access tab: The user who creates the program increment is the authorized user per default. This can be changed. Select one or more authorized user groups that shall have write permissions to the program increment. All users in the authorized user group can edit the program increment.

  authorized user

  An authorized user has primary responsibility to maintain the data for an object. Typically this is the user that has created the object. The authorized user as well as members of authorized user groups have write permissions to objects they are responsible for.

  authorized user group

  An authorized user group is a set of users that have been granted write permissions to an object. More than one authorized user group may be specified for an object.

A role represents a functional responsibility that a user or organization has for the program increment. Assigning users and organizations to roles is critical to understanding responsibility for assets in the IT and is required to answer the business question Who is responsible for our assets?

Responsibilities are based on preconfigured role types. Your company may also configure custom role types via the Portfolio Admin user profile. Depending on the role type, a specified user and/or a specified organization may fulfill the responsibility for the program increment. A user assigned responsibility via a role has read-only permissions to the program increment. To change data about the program increment, they must also be specified as an authorized user or member of an authorized user group.

Roles can be assigned to a program increment in the Program Increments data workbench or the program increment content area via Overview > Responsibilities. A person can have one of the following roles or a custom role added by your company:

• Business Owner: One or more persons who own the program increment and are responsible for managing the functional requirements.
• System Architect: A person who designs and oversees the structure of complex IT systems ensuring they are scalable, secure, and aligned with business goals.
• Product Manager: A person who is the responsible for defining and supporting the building of the features over the product market lifecycle.
• Release Train Engineer: A person who facilitates program increment processes, removes impediments, and drives continuous delivery of value across teams.
• Stakeholder: Multiple persons and organizations who have an interest in the program increment and therefore requires read-only access permissions.

To specify responsibilities for the program increment:

1. Click in the relevant role field to open the selector.
2. Expand the ORGANIZATION or USER sections in the selector and select the person or organization fulfilling the role.
3. Click OK to save the role definition and close the selector.

Click the  plus sign button > Create Iteration. Specify the iteration's basic attributes. All mandatory fields must be defined to create the iteration and save it. In the Program Increments view, click the Navigate   button next to a program increment to open its content area and specify the iteration's attributes.