Start your first SAFe train

This article will help you set up your first SAFe train, which consists of two teams: a front-end development team and a back-end development team.

• You will start by establishing the first "Front end" team using the Essential SAFe® - Scrum Team model.

• Then, you will launch the train that will become part of this team. You will have your train with an associated team.

• Afterwards, you will create your first "Program Increment" from your train. You will observe the impacts on your team.

• In a second step, you will form the second "Back end" team and attach it to your train. You'll learn how to add a team in the process of "Program Increment."

Creating Teams: "Essential SAFe® - Scrum Team"

The first step is to create a project for a team that can be integrated into a SAFe® train using the "Essential SAFe® - Scrum Team" template. This project corresponds to the workspace of a team that can then be attached to an SAFe® train.
The choice of this model ensures compatibility with train synchronization requirements, which are based on the configuration of the team's schedule trackers. Teams must comply with certain criteria for configuring Release and Sprint trackers to ensure their compatibility with the train (e.g. expected semantics, compatible status values, artifact links field, submission permissions, etc.).

Create the program: "Essential SAFe® - Train Agile" and add the first team to the program

Now you need to create a project with the "Essential SAFe® - Train Agile" template.
This project represents the SAFe® train: it is used to centralize the management of the program and to synchronize the schedules with the projects attached to it. This is, to put it simply, the program's workspace.

You can then add the team created in the previous step to this train.
Once attached, it will appear in the sidebar of the program workspace and can be synchronized with the train's schedules.

Prepare program schedules

It is now necessary to create the schedules. On a SAFe® model, schedules are represented by program increments, which are made up of iterations. It is in these schedules that the features of the program can then be planned.

Add a new team to the program

You may need to add a crew during a train. Tuleap allows you to meet this need by allowing you to add a team and resynchronize it with current schedules. To add a team, create a new one using the same process described in the Create Teams section: "Essential SAFe® - Scrum Team".

Practical information

You must be an administrator of the projects you want to consolidate.

Create and schedule a feature with the teams' user stories

This step allows you to move from a requirement defined at the program level to work distributed among several teams. In concrete terms, a feature is created in the program workspace, then scheduled by breaking it down into user stories that will be assigned to the different team workspaces (front-end, back-end, etc.).
The goal is to clearly distribute the work between the teams, take into account the dependencies between their user stories, and integrate them into a Program Increment (PI).

Key Steps:

1. Creation of the feature: a feature represents a major feature to be developed (e.g. "Integration of the online payment system").

   To do this, click on the

2. Breakdown into user stories by team: each team creates its user stories in relation to the feature.

   You must therefore go to the Trackers service of your Team and add artifacts to the User Stories tracker that you will link to the newly created feature.

3. Planning in the Program Increment (PI): User stories are planned in team iterations, which are themselves integrated into an Increment Program.

4. Dependency management: If one user story depends on another, these dependencies should be specified in order to facilitate coordination.

   

   Tuleap Program Management™ will then automatically create a link between the Feature and these User Stories.

   

5. Validation and follow-up: Check that the teams' user stories are linked to the feature and properly planned, in order to ensure the overall monitoring of progress.