Capture iterations
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 > Iterations. 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 iterationt's content area and define it in more detail there. Click to learn about how to use data workbenches.
-
Add a new program iteration. Click
> Create Iteration to open the edit panel and specify the basic data. -
Define the details of the iteration. Click the Navigate
button next to an iteration to open its content area. Specify the iteration's attributes as well as the relationships that it has to other assets in the repository.
Try to capture as much information as possible about the iteration because complete data considerably improves the results of business questions and other analytics.
Once an iteration is in the repository, you can define more details about it in the Iterations data workbench . Or specify and analyze the iteration in detail in its content area . In the data workbench, click the Navigate button for a iteration to open its content area > Overview page. All mandatory fields must be defined to create the iteration and save it.
Per default, the data workbench displays a limited set of basic attributes. You can add more columns via the Structure column to capture other attributes directly in the data workbench.
Define the iteration's basic data. All mandatory fields must be defined to create the iteration and save it.
- Name: (Mandatory) Enter a unique name for the iteration. The name should help others easily understand the iteration.
- Start Date and End Date: The planned start and end dates capture the period when the iteration is actively being executed in the company. This is the period from when the iteration 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 iteration from initiation to execution. Possible values are:
- In Design: The iteration is being scoped and defined.
- In Realization: The iteration is active.
- Done: The iteration is finished with its delivery.
- Authorized Access tab: The user who creates the iteration is the authorized user per default. This can be changed. Select one or more authorized user groups that shall have write permissions to the iteration. All users in the authorized user group can edit the iteration.
A role represents a functional responsibility that a user or organization has for the iteration. 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 iteration. A user assigned responsibility via a role has read-only permissions to the iteration. To change data about the iteration, they must also be specified as an authorized user or member of an authorized user group.
Roles can be assigned to an iteration in the Iterations data workbench or the iteration 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 iteration 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 iteration processes, removes impediments, and drives continuous delivery of value across teams.
- Stakeholder: Multiple persons and organizations who have an interest in the iteration and therefore requires read-only access permissions.
To specify responsibilities for the iteration:
- Click in the relevant role field to open the selector.
- Expand the ORGANIZATION or USER sections in the selector and select the person or organization fulfilling the role.
- Click OK to save the role definition and close the selector.
Go to the iteration's content area > Execution > Stories. Click the plus sign button > Add Story and select the story that shall be delivered by the program increment.
The assets that are impacted by an iteration make up its solution scope. You can specify any application, business capability, business process, component, information flow, or organization as an asset that is impacted by iteration.
- Go to the iteration's content area > Solution Scope > Affected Architecture.
- Click New > and select the relevant option to add the architecture impacted by the iteration.
Information flows specified for applications that have been added to the iteration's architecture scope will not be automatically added to the iteration. You must explicitly add the relevant information flows to the iteration in the Affected Architecture view.
- Select the relevant assets and click OK.
- To document the planned changes to one or more architecture elements assigned to the iteration's scope, click the
3-dots button > 
Edit. Provide a comment about the change and set the Change Category to describe the how the asset will be changed by the iteration: - New: The asset will be introduced in the scope of the iteration.
- Updating: The asset will be significantly updated in the scope of the iteration.
- Changing: The asset will be changed to some degree in the scope of the iteration.
- Retiring: The asset will be retired in the scope of the iteration.