Capture agile release train data

Agile release trains have program increments that timebox the release and each program increment has iterations that describe the specific measurable steps that need to be taken to achieve the goals.Your enterprise can specify multiple agile release trains.

• An agile release train (ART) is a long-term team of agile teams, which, along with other stakeholders, incrementally develops and delivers one or more solutions that contribute to an operational value stream or developmental value stream.

  operational value stream

  An operational value stream describes the sequence of value stream steps that an organization performs to deliver a product or service that provides a continued flow of value to the company. Operational value streams allow 'value' in terms of the usefulness, advantage, or benefit of IT solutions to be articulated and measured in the business architecture.

  developmental value stream

  A developmental value stream describes the activities required to design, build, test, and deliver the systems or solutions that enable an organization’s operational value streams. It represents how teams create and evolve the capabilities the business relies on.

• 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.

  feature

  A feature is a tangible product or, solution functionality, or improvement that provides business value. Features contribute to the realization of an epic. Features can be further broken down into stories which are implemented, tested, and released incrementally. Features are structured to be delivered by a program increment (PI) in the context of an agile release train (ART).

• An iteration is a standard, fixed-duration timebox during which agile teams and ARTs individually and collectively deliver incremental customer value while working towards the objective of the program increment. Stories are delivered in the context of an iteration.

  story

  A story is a small, actionable requirement specified to realize a feature. Stories are implemented, tested, and released incrementally and are delivered in an iteration as part of an agile release train (ART). Stories may be of the type User Story, which provides value to the end user, and Enabler Story, which describes the necessary work of exploration, architecture, infrastructure, and compliance.

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 > Agile Release Trains.​ 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 an agile release train's content area and define it in more detail there. Click to learn about how to use data workbenches.

• Add a new agile release train. Click   > Create Agile Release Train to open the edit panel and specify the basic data.
• Define the details of the agile release train. Click the Navigate   button next to an agile release train to open its content area. Specify the agile release train's attributes as well as the relationships that it has to other assets in the repository.

Define the agile release train's basic data. All mandatory fields must be defined to create the agile release train and save it.

• Name: (Mandatory) Enter a unique name for the agile release train. The name should help others easily understand the purpose of the agile release train.
• Start Date and End Date: The planned start and end dates capture the period when the agile release train is actively being executed in the company. This is the period from when the agile release train 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 agile release train from initiation to execution. Possible values are:
  • In Design: The agile release train is being scoped and defined.
  • In Realization: The agile release train is active.
  • Done: The agile release train is finished with its delivery.
• Program Increments: The program increments (PI) that belong to the agile release train.

  program increment (PI)

  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.

• Authorized Access tab: The user who creates the agile release train is the authorized user per default. This can be changed. Select one or more authorized user groups that shall have write permissions to the agile release train. All users in the authorized user group can edit the agile release train.

  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 agile release train. 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 agile release train. A user assigned responsibility via a role has read-only permissions to the agile release train. To change data about the agile release train, they must also be specified as an authorized user or member of an authorized user group.

Roles can be assigned to an agile release train in the Agile Release Trains data workbench or the agile release train 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 agile release train 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 feature over the product market lifecycle.
• Release Train Engineer: A person who facilitates agile release train processes, removes impediments, and drives continuous delivery of value across teams.
• Stakeholder: Multiple persons and organizations who have an interest in the agile release train and therefore requires read-only access permissions.

To specify responsibilities for the agile release train:

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 Program Increment. Specify the program increment's basic attributes. All mandatory fields must be defined to create the program increment 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 program increment's attributes.